Orgo icon

Orgo

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

Actions19

Overview

This node interacts with the Orgo API to manage event registrations (referred to as "eventAttend" resource). Specifically, the Get Many operation retrieves multiple event registrations for a specified event. It supports pagination and allows users to choose between simplified or raw output formats.

Typical use cases include:

  • Fetching all registrations for an event to monitor attendance.
  • Integrating event registration data into other workflows or reporting tools.
  • Paginating through large sets of registrations when events have many attendees.

For example, you might use this node to get a list of all users registered for a conference event, optionally retrieving only key fields like user ID, name, and status in a simplified format.

Properties

Name Meaning
Event ID The unique identifier of the event for which to retrieve registrations.
Output Format of the returned data:
- Simplified: Returns key fields only.
- Raw: Returns all available data from the API.
Page The page number of results to fetch (pagination), with each page containing up to 100 results.

Output

The node outputs an array of JSON objects representing event registrations.

  • In Simplified mode, each registration object includes:

    • id: Registration ID
    • userId: ID of the user registered
    • userName: User's full name or username
    • eventId: ID of the event
    • status: Attendance status (e.g., Registered, Attended)
    • createdAt: Timestamp when the registration was created

  • In Raw mode, the node returns the full registration objects exactly as received from the Orgo API, including nested user and event details.

No binary data is output by this operation.

Dependencies

  • Requires an API token credential for authenticating with the Orgo API.
  • The base URL for the Orgo API must be configured in the credentials.
  • The node uses HTTP GET requests to the /event_attends endpoint with query parameters for event ID and pagination.

Troubleshooting

  • Missing or invalid Event ID: The operation requires a valid event ID parameter. Ensure it is provided and correctly formatted.
  • API authentication errors: If the API token is missing, expired, or incorrect, the node will fail with authentication errors. Verify the API token credential configuration.
  • Pagination issues: Requesting pages beyond the available range may return empty results. Adjust the page number accordingly.
  • Unexpected response format: If the API changes its response structure, the simplified mapping may break. Switching to raw output can help diagnose such issues.
  • Network or connectivity problems: Ensure that the n8n instance has network access to the Orgo API endpoint.

Links and References

Discussion