Actions11
- Event Actions
- Order Actions
- Organization Actions
- User Actions
- Venue Actions
Overview
This node integrates with the Eventbrite API to list orders associated with a specific event. It is useful for event organizers or managers who want to retrieve order details such as ticket purchases, attendee information, and payment status for their events.
Typical use cases include:
- Fetching all orders for an event to analyze sales.
- Exporting order data for reporting or CRM integration.
- Monitoring ticket sales in real-time during an event promotion.
For example, you can use this node to get a list of all ticket orders placed for a conference event by providing the event's ID.
Properties
| Name | Meaning |
|---|---|
| Event ID | The unique identifier of the event for which to list orders. |
| Additional Fields | Optional parameters to customize the output: |
| - Max Results | Maximum number of orders to return (between 1 and 50). |
| - AI Agent Mode | Whether to format the output optimized for AI agents (simplified and structured). |
| - Include Summary | When AI Agent Mode is enabled, whether to include a human-readable summary of the results. |
Output
The node outputs an array of JSON objects, each representing an order related to the specified event. Each order object contains detailed information about the order as returned by the Eventbrite API, including but not limited to:
- Order identifiers
- Ticket types and quantities
- Buyer information
- Payment status
- Order creation and update timestamps
If AI Agent Mode is enabled, the output may also include a simplified summary string designed for easier consumption by AI systems, along with metadata such as total results count and timestamp.
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
https://www.eventbriteapi.com/v3. - Proper configuration of the API key credential within n8n is necessary.
Troubleshooting
Common issues:
- Invalid or missing Event ID will cause the API request to fail.
- Exceeding the maximum allowed results (more than 50) will be rejected; ensure Max Results is between 1 and 50.
- Network or authentication errors if the API key is invalid or expired.
Error messages:
- Errors from the Eventbrite API are propagated and may include messages like "Unauthorized" or "Not Found".
- If the node fails to fetch orders, it throws an error indicating the failure reason.
- To handle intermittent failures, enable "Continue On Fail" in the node settings to process remaining items.