Eventbrite
Read events, orders, attendees and ticket classes from Eventbrite.
About
Eventbrite ships in the w6w first-party pack. It declares 10 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.eventbrite- Version
- 0.2.5
- Author
- w6w
- Licence
- MIT
- Categories
- Commerce & Payments · Calendar & Scheduling
Overview
Eventbrite reads events, orders and attendees directly into a workflow — listing and fetching events, pulling the orders and attendees tied to them, and reading ticket classes to see what was actually offered for sale.
Organizations and organizers are available too: an account’s organizations can be listed, and organizers can be listed or fetched individually, which matters for anyone managing events across more than one Eventbrite organizer profile.
A fit for keeping attendee and order data in sync with a CRM or spreadsheet, triggering follow-up actions once an event’s attendee list is known, or reporting on ticket sales without logging into Eventbrite’s own dashboard. This app reads Eventbrite data; it does not create or modify events, orders or tickets.
Build with Eventbrite
Three routes to the same 10 actions. The Workflow tab is generated from Eventbrite's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
List Events
list-events List events for an organization. Walks one page; pass back `continuation` to get the next.
List Organizers
list-organizers List organizers belonging to an organization. Organizers are the public-facing event hosts (logo, bio, social links) — distinct from Organizations.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Eventbrite's real ids.
{
"manifestVersion": "2",
"name": "eventbrite-example",
"steps": [
{
"id": "get-attendee",
"uses": {
"app": "io.w6w.eventbrite",
"action": "get-attendee",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"eventId": "<eventId>",
"attendeeId": "<attendeeId>"
}
}
]
}Here are some of the things you can do
-
Get Attendee
readget-attendee -
Get Event
readget-event -
Get Order
readget-order -
Get Organizer
readget-organizer -
List Attendees
readlist-attendees
+5 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Eventbrite, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Eventbrite. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "list-events",
payload: {
organizationId: "<value>",
// status: "<value>",
// nameFilter: "<value>",
// timeFilter: "<value>",
// showSeriesParent: "<value>",
// pageSize: "<value>",
// continuation: "<value>",
// expand: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action list-events --payload '{"organizationId":"<value>"}'Give an AI agent Eventbrite — without giving it Eventbrite's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.eventbrite#get-attendee",
"input": {
"eventId": "<eventId>",
"attendeeId": "<attendeeId>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Eventbrite connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Eventbrite's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Eventbrite itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Eventbrite declares its own checks, so its health is a property of the app rather than something the host guesses at.
Eventbrite platform status
API rate-limit headroom
Hourly allowance remaining on this token, read off the `X-Rate-Limit-*` headers.