Eventbrite integration

What it does

The Eventbrite integration lets your agency act the moment a client's event sells a ticket and manage their full Eventbrite footprint without leaving TaskJuice. Connect an Eventbrite account once and your workflows can list organizations the account belongs to, list and read events under any of those organizations, create draft events and publish them, list attendees and orders for a live event, cancel an event, and list team members and venues. The integration also listens in real time as new events are created, existing events update or publish, attendees change, orders are placed, and venues are edited.

Connect an Eventbrite account

1. Open your workspace in TaskJuice and navigate to Connections.
2. Choose Eventbrite and click Connect.
3. Sign in to the Eventbrite account that owns the organization you want to wire up and approve the requested access.
4. TaskJuice returns you to the workspace with the connection ready to use in any workflow.

To revoke access, open your Eventbrite account, navigate to Account Settings and then App Management, and remove the TaskJuice authorization. See the Eventbrite platform docs for the full OAuth grant flow.

Triggers

• eventbrite/order-placed fires when an attendee places an order against an event (order.placed). The activation payload carries the resource api_url and the webhook configuration, so a follow-up eventbrite/list-event-orders call can hydrate the full order.
• eventbrite/event-created fires when a new event is created under an organization (event.created). Use it to mirror new events into your client's CRM, marketing automation, or website.
• eventbrite/event-updated fires when an existing event is updated (event.updated). Use it to keep schedule, capacity, and ticketing changes in sync downstream.
• eventbrite/event-published fires when a draft event is published and goes live (event.published). Useful for kicking off promotion sequences the moment a client lists a new event.
• eventbrite/attendee-updated fires when an attendee record changes (attendee.updated), including check-in status, name changes, and refund updates.
• eventbrite/venue-updated fires when a venue tied to one of the connected organizations is updated (venue.updated). Useful for keeping cached venue metadata in sync across downstream systems.

Every inbound POST is authenticated by matching the value Eventbrite sends in the Authorization request header against the shared secret you configured on the webhook. Activations whose header is missing or does not match are rejected before they reach your workflow.

Actions

• eventbrite/get-current-user returns the currently authenticated Eventbrite user, including the user id and primary organization required by other endpoints.
• eventbrite/list-organizations lists the organizations the authenticated user belongs to, paginated by the continuation token.
• eventbrite/get-organization retrieves a single organization by id.
• eventbrite/list-owned-events lists events owned by the authenticated user with optional status and ordering filters, paginated by the continuation token.
• eventbrite/list-organization-events lists events under a specific organization with optional status, ordering, and page-size filters, paginated by the continuation token.
• eventbrite/get-event retrieves a single event by id.
• eventbrite/create-event creates a draft event under an organization with a name, timezone, start and end timestamps, and currency.
• eventbrite/publish-event publishes a draft event, transitioning it from draft to live. The event must have at least one ticket class before publishing.
• eventbrite/list-event-attendees lists attendees for an event with optional status and changed_since filters, paginated by the continuation token.
• eventbrite/list-event-orders lists orders placed against an event with optional status and changed_since filters, paginated by the continuation token.
• eventbrite/cancel-event cancels a live event. Refunds and attendee notifications follow the organizer's configured cancellation policy.
• eventbrite/list-organization-members lists team members for an organization, including each member's role.
• eventbrite/list-organization-venues lists venues an organization has used or created.

Known limitations

• Eventbrite enforces a per-token rate limit. When a 429 status is returned, TaskJuice surfaces it as a retryable error so the workflow can back off and retry.
• Publishing requires the event to have at least one ticket class. Create a ticket class via the Eventbrite UI or platform API before calling publish-event.
• Webhooks are scoped to a single organization at creation time. To listen on multiple organizations, create one webhook (and one connection) per organization.
• Webhook POSTs deliver only a reference (api_url) and the action metadata. Your workflow follows up with a lookup action (list-event-orders, list-event-attendees, get-event) to hydrate the full payload.
• The TaskJuice integration targets the Eventbrite v3 REST API. Fields surfaced only on private or beta endpoints are not exposed.