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 event by its ID. It is useful for workflows that need to fetch event details such as name, description, dates, venue, and other metadata from Eventbrite. Typical use cases include syncing event data into CRMs, generating reports, or triggering actions based on event attributes.
For example, you can use this node to:
- Get full details of an event before sending notifications.
- Retrieve event info to display in a dashboard.
- Use event data as input for further automation steps like ticketing or marketing campaigns.
Properties
| Name | Meaning |
|---|---|
| Event ID | The unique identifier of the event to retrieve. |
| Additional Fields | Optional extra parameters: |
| - Max Results: Maximum number of results to return (1-50) — relevant if listing multiple items. | |
| - AI Agent Mode: Whether to optimize output format for AI agents (simplified and structured). | |
| - Include Summary: When AI Agent Mode is enabled, whether to include a human-readable summary. |
Output
The node outputs JSON data representing the event details retrieved from Eventbrite. The structure includes fields such as:
id: Event IDname: Event name (text or HTML)description: Event description (text or HTML)url: Public URL of the eventstart/end: Start and end date/time objects with timezone infocreated,changed: Timestamps for creation and last modificationcapacity: Maximum capacity of the eventstatus: Current status (e.g., live, draft)currency: Currency code used for the eventonline_event: Boolean indicating if the event is onlineorganization_id,organizer_id,venue_id: Related entity IDscategory_id,subcategory_id,format_id: Classification identifiersis_free: Boolean indicating if the event is freelocale: Locale stringprivacy_setting: Privacy level of the eventvenue: If available, nested object with venue details including name, address, latitude, and longitude- Other metadata fields related to event series, inventory, sharing, and appearance
If AI Agent Mode is enabled, the output may also include a simplified summary text designed for AI consumption, along with a count of total results and a timestamp.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Eventbrite API.
- Uses HTTPS requests to the Eventbrite v3 REST API endpoint (
https://www.eventbriteapi.com/v3). - The node expects the API key to be provided via n8n credentials configuration.
- No additional external dependencies beyond standard HTTP client libraries bundled with n8n.
Troubleshooting
Common issues:
- Invalid or missing Event ID will cause the API call to fail.
- Expired or incorrect API authentication token will result in authorization errors.
- Network connectivity problems can cause request timeouts or failures.
- Requesting events that do not exist or are inaccessible due to permissions will return errors.
Error messages:
"Failed to fetch events from organization ..."indicates issues retrieving events when searching by organization."No data found"means the requested event ID did not return any data.- Authorization errors typically mention invalid token or permission denied.
Resolutions:
- Verify the Event ID is correct and exists in your Eventbrite account.
- Ensure the API key credential is valid and has necessary scopes.
- Check network connectivity and retry.
- Confirm the authenticated user has access rights to the event.