--- title: "Eventbrite Integration" description: "Create and publish Eventbrite events, manage ticket classes and venues, and sync attendees and orders into your other systems through the Eventbrite API." url: https://flowrunner.ai/integrations/eventbrite date_modified: 2026-08-01T02:40:32-07:00 --- # Eventbrite [Scheduling](https://flowrunner.ai/integrations/category/project-management-productivity) Create and publish Eventbrite events, manage ticket classes and venues, and sync attendees and orders into your other systems through the Eventbrite API. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 20 actions · API key · available [Eventbrite website](https://eventbriteapi.com/) · [Platform Documentation](https://www.eventbrite.com/platform/api) · Capability data verified 2026-08-12 1. An upstream campaign approves a new event and fires the setup flow 2. Agent reads the event name, dates, timezone, and venue from the source 3. Agent creates the event as a draft with Create Event 4. Agent adds ticket classes and the venue the event needs to sell 5. Agent confirms the event has a valid time range and at least one ticket class 6. Agent posts the draft event and its details to the events channel 7. Publishing the event to the public waits for an owner to confirm it is ready ## What This Integration Enables FlowRunner agents use Eventbrite to run the event lifecycle without the manual setup. An agent can create an event as a draft, assemble the ticket classes and venue it needs, and keep attendees and orders synced into a CRM, spreadsheet, or marketing list. It can look up attendee check-in status and profile answers for on-site tooling and report on ticket sales across an organization. What it holds back is the public step. Making an event live reaches customers, so the agent assembles everything and then asks a person to confirm before it publishes. ### Without FlowRunner **Manual event setup**: Someone builds each event, ticket class, and venue by hand in the Eventbrite UI **Attendees exported by hand**: Registrant and order data is pulled into a spreadsheet manually after the fact **No review before go-live**: Events go live with whatever details the last editor happened to save ### With FlowRunner **Draft assembled automatically**: The event, ticket classes, and venue are built from the source record as a draft **Attendees and orders synced**: New attendees and orders flow into the CRM and reporting on a schedule **Human confirms go-live**: Publishing to the public waits for an owner to confirm the event is correct ## Use Case Scenarios ### Draft-to-Publish Event Setup A campaign approves a new event. The agent creates it as a draft with Create Event using the name, start, end, and timezone from the source record. It adds the ticket classes with Create Ticket Class and attaches a venue with Create Venue. It confirms the event has a valid time range and at least one ticket class, then posts the draft to the events channel for a final look. The event is fully built; only the public go-live waits on a person. ### Attendee and Order Sync On a schedule, the agent calls List Attendees and List Orders for an organization event. It enrolls each new attendee into a post-event follow-up audience and logs each order into a sales-tracking system. The reporting stays current without anyone exporting a CSV. ### On-Site Check-In Support During the event, on-site tooling reads attendee status. The agent calls Get Attendee to return check-in status, barcodes, and profile answers, so the check-in desk has what it needs to admit and route each guest without manual lookups. ## Human-in-Loop Highlight When an event is assembled and ready, the agent does not call Publish Event on its own. It pauses and routes to the event owner through their preferred channel: "The \[Event\] draft is built for \[date\] at \[Venue\] with \[N\] ticket classes. Review it here: \[link\]. Publish it to the public, or hold for changes?" The owner confirms, and only then does the agent make the event live. The step that customers see gets a human confirmation, so a wrong date or price never goes public unreviewed. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 20 actions ### Events 7 - **Cancel Event** Cancels a published event. Used when an event is called off and downstream systems must be notified. - **Create Event** Creates a new event as a draft, with start, end, timezone, and optional venue and category. Used to provision events programmatically from an upstream campaign. - **Get Event** Retrieves a single event. Used to read event details before publishing or updating. - **List Events** Lists an organization events. Used to find the event a workflow needs to act on. - **Publish Event** Makes a draft event live. Used once the event has at least one ticket class and is ready to sell. - **Unpublish Event** Takes a live event offline. Used to pause sales without cancelling. - **Update Event** Updates an existing event. Used to keep event details accurate. ### Attendees and Orders 4 - **Get Attendee** Retrieves a single attendee, including check-in status and profile answers. Used for on-site tooling. - **List Attendees** Lists an event attendees. Used to sync registrants into a CRM or follow-up audience. - **Get Order** Retrieves a single order. Used to inspect purchase details. - **List Orders** Lists orders for an organization. Used to log sales into a tracking system. ### Ticket Classes 4 - **Create Ticket Class** Creates a ticket class on an event, free or paid. Used to define what attendees can buy before publishing. - **Delete Ticket Class** Removes a ticket class. Used in event setup cleanup. - **List Ticket Classes** Lists an event ticket classes. Used to audit pricing and availability. - **Update Ticket Class** Updates an existing ticket class. Used to change price or capacity. ### Venues and Categories 4 - **Create Venue** Creates a venue. Used to provision a location an event can reference. - **Get Venue** Retrieves a single venue. Used to read venue details. - **List Venues** Lists an organization venues. Used to select a venue for an event. - **List Categories** Lists the available event categories. Used to resolve a category ID for an event. ### Account 1 - **Get User** Returns the connected account. Used as a connection check. ## Frequently Asked Questions ### What can FlowRunner do with Eventbrite? FlowRunner agents can run List Events, Get Event, and Create Event in Eventbrite, plus 17 more actions. ### Does connecting Eventbrite to FlowRunner require OAuth? No. Eventbrite connects to FlowRunner with an API key, no OAuth flow required. ### Can Eventbrite trigger a FlowRunner workflow automatically? Eventbrite doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Eventbrite?** This integration exposes Eventbrite to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/eventbrite. Site index: https://flowrunner.ai/llms.txt