Actions11
- Event Actions
- Order Actions
- Organization Actions
- User Actions
- Venue Actions
Overview
This node integrates with the Eventbrite API to retrieve detailed information about a specific order. It is designed to fetch order data by its unique Order ID, which can be useful for event organizers or administrators who need to access purchase details, attendee information, or payment status related to an order.
Common scenarios include:
- Retrieving order details to verify ticket purchases.
- Accessing attendee information linked to an order.
- Integrating order data into other workflows such as CRM or email marketing.
- Automating reporting on sales and orders for events.
Example: Given an Order ID, the node fetches all relevant details about that order from Eventbrite, enabling further processing or analysis within an automation workflow.
Properties
| Name | Meaning |
|---|---|
| Order ID | The unique identifier of the order to retrieve. This is required. |
| Additional Fields | Optional parameters to customize the request: |
| - Max Results | Maximum number of results to return (1-50). Relevant if listing multiple orders. |
| - AI Agent Mode | Whether to optimize the output format for AI agents by simplifying and structuring it. |
| - Include Summary | When AI Agent Mode is enabled, whether to include a human-readable summary in the output. |
Output
The node outputs JSON data representing the details of the requested order. The structure corresponds directly to the Eventbrite API's order object, including fields such as:
id: The order's unique identifier.status: Current status of the order.created,changed: Timestamps for creation and last modification.event_id: The associated event's ID.attendees: Information about attendees included in the order.amount_paid: Total amount paid for the order.- Other metadata related to payment, tickets, and customer info.
If the "AI Agent Mode" is enabled, the output may also include a simplified summary designed for easier consumption by AI systems, optionally with a human-readable summary text.
No binary data is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Eventbrite API.
- The node makes HTTP requests to the Eventbrite API endpoint at
https://www.eventbriteapi.com/v3. - Proper configuration of the API key credential within n8n is necessary for successful operation.
Troubleshooting
- Invalid or missing Order ID: Ensure the Order ID is correctly provided and exists in Eventbrite.
- Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- API rate limits: Eventbrite enforces rate limits; excessive requests may result in temporary blocking.
- Network issues: Check connectivity to the Eventbrite API endpoint.
- Error messages from API: The node surfaces error messages returned by Eventbrite; review these for clues (e.g., "Order not found").
- If the node is set to continue on failure, errors will be included in the output JSON for each failed item.