Orgo icon

Orgo

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

Actions19

Overview

This node interacts with the Orgo API, a multi-tenant SaaS platform for managing organizational data. Specifically, the "Event" resource with the "Get" operation allows users to retrieve detailed information about a single event by its UUID.

Typical use cases include:

  • Fetching event details such as title, dates, location, and status for display or processing in workflows.
  • Integrating event data into other systems or automations that require up-to-date event information.
  • Using event metadata to trigger conditional logic or notifications based on event attributes.

For example, you might use this node to get an event's start and end dates to schedule reminders or to verify event status before registering attendees.

Properties

Name Meaning
UUID The unique identifier (UUID) of the event to retrieve. This is required to specify which event's details to fetch.

Output

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

  • id: Internal event ID
  • uuid: Event UUID
  • title: Title of the event
  • startDate: Event start date/time
  • endDate: Event end date/time
  • location: Location of the event
  • status: Current status of the event

The node returns this data as a single JSON object inside an array, e.g.:

[
  {
    "json": {
      "id": "123",
      "uuid": "abc-def-ghi",
      "title": "Annual Conference",
      "startDate": "2024-09-01T09:00:00Z",
      "endDate": "2024-09-03T17:00:00Z",
      "location": "Conference Center",
      "status": "scheduled"
    }
  }
]

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Orgo API.
  • The node expects the base URL and API token to be configured in the credentials.
  • HTTP requests are made to the Orgo API endpoints using these credentials.

Troubleshooting

  • Missing or invalid UUID: If the UUID parameter is empty or incorrect, the API will likely return an error indicating the event was not found. Ensure the UUID is correctly provided.
  • Authentication errors: If the API token is missing, expired, or invalid, the request will fail with authentication errors. Verify the API token in the credentials.
  • Network issues: Connectivity problems can cause request failures. Check network access to the Orgo API endpoint.
  • API rate limits or server errors: The Orgo API may return errors if rate limits are exceeded or internal errors occur. Review error messages and retry as appropriate.

If the node is set to continue on failure, errors will be returned in the output JSON under an error field.

Links and References

Discussion