Orgo icon

Orgo

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

Actions19

Overview

The node interacts with the Orgo API, a multi-tenant SaaS platform for managing organizational data. Specifically, the "Event" resource with the "Get Many" operation retrieves multiple event records from the Orgo system.

This operation is useful when you want to fetch a list of events, for example:

  • Displaying upcoming or past events in a dashboard.
  • Synchronizing event data with another system.
  • Generating reports based on event metadata.

You can control how many events to retrieve and whether to get simplified key information or the full raw event data.

Properties

Name Meaning
Output Choose between:
- Simplified: Returns only key fields (id, uuid, title, startDate, endDate, location, status).
- Raw: Returns all available event data as provided by the API.
Limit Maximum number of event records to return. Must be at least 1. Default is 50.

Output

The output is an array of JSON objects representing events.

  • If Output is set to Simplified, each event object includes these key fields:

    • id: Internal event identifier
    • uuid: Unique universal identifier of the event
    • title: Event title/name
    • startDate: Start date/time of the event
    • endDate: End date/time of the event
    • location: Location of the event
    • status: Status of the event (e.g., active, cancelled)

  • If Output is set to Raw, the entire event object as returned by the Orgo API is included without filtering.

The node does not output binary data.

Dependencies

  • Requires an API token credential for authenticating with the Orgo API.
  • The base URL of the Orgo API must be configured in the credentials.
  • The node uses HTTP GET requests to fetch event data from the /events endpoint.

Troubleshooting

  • Common issues:

    • Invalid or missing API token will cause authentication errors.
    • Exceeding the API rate limits may result in request failures.
    • Providing a limit less than 1 will likely cause validation errors.
    • Network connectivity problems can prevent successful API calls.

  • Error messages:

    • Authentication errors typically indicate invalid or expired API tokens; verify and update credentials.
    • Validation errors about parameters usually mean required inputs are missing or out of range; check the "Limit" property.
    • HTTP errors from the API (4xx or 5xx) should be inspected for details; ensure the Orgo API service is operational.

Links and References

Discussion