Actions19
Overview
This node integrates with the Orgo API to manage event registrations, specifically allowing users to register for events. The "Create" operation under the "Event Registration" resource enables creating a new registration record linking a user to an event with an optional attendance status.
Typical use cases include:
- Automatically registering users for events in an organizational system.
- Managing attendance statuses such as Registered, Attended, Invited, or Not Attending.
- Integrating event registration workflows into broader automation pipelines.
For example, you could use this node to register a user for a conference event by providing the event's UUID and the user's ID, optionally setting their attendance status.
Properties
| Name | Meaning |
|---|---|
| Event UUID | The unique identifier (UUID) of the event to register the user for. |
| User ID | The identifier of the user who is registering for the event. |
| Additional Fields | Optional fields to specify additional details about the registration. Currently supports: - Status: Attendance status with options: Registered, Attended, Not Attending, Invited. Default is Registered. |
Output
The output JSON contains the newly created event registration object returned from the Orgo API. It includes at least the following fields:
event: A reference URL to the event resource.user: A reference URL to the user resource.status: Numeric code representing the attendance status (e.g., 1 for Registered).isInvited: Boolean flag set if the status is "Invited".- Other metadata fields as provided by the API response.
The node outputs one item per execution containing the full JSON response of the created registration.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Orgo API via an API token credential.
- The node expects the base URL and API token to be configured in the credentials.
- HTTP requests are made to the
/event_attendsendpoint of the Orgo API.
Troubleshooting
- Missing Required Parameters: Ensure that both "Event UUID" and "User ID" are provided; otherwise, the API call will fail.
- Invalid Status Value: The status must be one of the predefined options (Registered, Attended, Not Attending, Invited). Using unsupported values may cause errors.
- API Authentication Errors: Verify that the API token credential is valid and has sufficient permissions.
- Network Issues: Check connectivity to the Orgo API base URL.
- Error Responses from API: The node returns error messages from the API in the output JSON if the request fails. Review these messages for specific issues like invalid IDs or permission problems.
Links and References
- Orgo API Documentation (Replace with actual URL if available)
- n8n Documentation on Creating Custom Nodes