Orgo icon

Orgo

Interact with Orgo API - Multi-tenant SaaS platform for organizations

Actions19

Overview

This node integrates with the Orgo API, a multi-tenant SaaS platform for managing organizations. Specifically, the Event Registration - Get operation retrieves detailed information about a single event registration by its unique ID.

Typical use cases include:

  • Fetching the status and details of a user's registration for an event.
  • Verifying attendance or registration data before processing further workflows.
  • Integrating event registration data into other systems or reports.

For example, you might use this node to get the registration record of a user attending a conference, then trigger follow-up emails or update CRM records based on the retrieved data.

Properties

Name Meaning
ID The unique identifier of the event registration to retrieve. This is required to specify which registration record to fetch.

Output

The output is a JSON object representing the event registration resource as returned by the Orgo API. It typically includes fields such as:

  • id: The registration's unique ID.
  • userId or nested user object: Identifies the user who registered.
  • eventId or nested event object: Identifies the event.
  • status: The attendance status (e.g., Registered, Attended, Not Attending, Invited).
  • createdAt: Timestamp when the registration was created.

If the node receives multiple items, it returns an array of such JSON objects, each corresponding to one registration.

The node does not output binary data.

Dependencies

  • Requires an API key credential for authenticating with the Orgo API.
  • Needs the base URL of the Orgo API instance configured in credentials.
  • Uses HTTP GET requests to fetch data from the /event_attends/{id} endpoint.

Troubleshooting

  • Missing or invalid ID: If the "ID" property is empty or incorrect, the API call will fail. Ensure the ID is provided and valid.
  • Authentication errors: If the API token or base URL is misconfigured, the request will be unauthorized or fail to connect.
  • Network issues: Connectivity problems to the Orgo API endpoint can cause timeouts or errors.
  • API changes: If the Orgo API changes its schema or endpoints, the node may return unexpected results or errors.

To resolve errors:

  • Verify the "ID" input is correct.
  • Check that the API token and URL are properly set in credentials.
  • Confirm network access to the Orgo API.
  • Review error messages returned in the node output for clues.

Links and References

Discussion