Event

trigger.eventbrite_event

TriggerBusiness appsconnection requiredruns in-engine

Registers a webhook subscription in the tenant's Eventbrite organization on publish and starts one run per delivered action. Emits {action, api_url, resource_id, payload}.

Start a run when Eventbrite reports a change (order, attendee, event).

Ask about Eventbrite All Eventbrite nodes Provider API docs ↗

Connection

Required: Yes — the node will not save without one
Auth type: OAuth 2.0
Providers: Eventbrite
Secret shape: the Eventbrite private token, or {client_id, client_secret, refresh_token}
Config it needs: organization_id
Resolved by: config.connection_id, else node.connection_id
Note: The token must be able to administer the organization's webhooks; a token for a different organization registers nothing useful. Publishing also needs MANTLE_APP_PUBLIC_BASE_URL set to a URL Eventbrite can reach.

Configuration

3 fields, none required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

Field	Type	Required	Default	Constraints	Example
actions Which Eventbrite actions to subscribe to. One subscription carries all of them, and it is deleted again when the workflow is unpublished or disabled.	array	No	["order.placed"]	1–15 characters; array of string	—
organization_id Subscribe on behalf of this organization instead of the one on the connection. Run eventbrite.list_organizations to find the id.	string	No	—	matches ^\d{1,32}$	—
event_id Only deliver actions about this one Eventbrite event. Leave blank to receive them for every event in the organization.	string	No	—	matches ^\d{1,32}$	—

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "actions": [
    "order.placed"
  ]
}

Output

One shape.

eventbrite event

A flat envelope over Eventbrite's pointer payload. Eventbrite never sends the object itself — fetch `api_url` for that.

Extra keys beyond the ones listed can appear.

Field	Type	Example
action The Eventbrite action that fired, e.g. order.placed. Branch on this when the subscription names more than one.	string	order.placed
api_url The API address of the thing that changed. Eventbrite sends a pointer and never the object, so fetch this to get the order, attendee or event itself.	string	https://www.eventbriteapi.com/v3/orders/1234567890/
resource_type The collection api_url points into — orders, attendees, events, venues, ticket_classes — lifted out so a workflow need not parse a URL.	string	orders
resource_id The id of the thing that changed, as a string so a long numeric id survives anything downstream that treats numbers as floats.	string	1234567890
webhook_id Eventbrite's id for the subscription that delivered this event.	string	9876543
user_id The Eventbrite user the subscription was created by — the account behind the connection, not the buyer.	string	4321098765
delivery_id Eventbrite's delivery id (X-Eventbrite-Delivery). Also the idempotency key: a retry carries the same id, so it joins the run it already started instead of starting a second one.	string	963154
payload The envelope exactly as Eventbrite sent it, for anything the fields above do not lift out.	object	—

{
  "action": "order.placed",
  "api_url": "https://www.eventbriteapi.com/v3/orders/1234567890/",
  "delivery_id": "963154",
  "payload": {
    "api_url": "https://www.eventbriteapi.com/v3/orders/1234567890/",
    "config": {
      "action": "order.placed",
      "endpoint_url": "https://mantle.example.com/api/v1/hooks/p/acme/8f3c…",
      "user_id": "4321098765",
      "webhook_id": "9876543"
    }
  },
  "resource_id": "1234567890",
  "resource_type": "orders",
  "user_id": "4321098765",
  "webhook_id": "9876543"
}

Notes

Publishing creates the subscription at Eventbrite; unpublishing, disabling or archiving deletes it. A workflow that is off is off at Eventbrite too.
Eventbrite does NOT sign its deliveries — there is no signature to check, and the callback URL's unguessable id is what keeps the endpoint private. Treat the body as a hint and fetch api_url for the authoritative object.
The payload is a pointer, never the object: an order.placed delivery carries the order's api_url, not the order.
One run per delivery, idempotent on X-Eventbrite-Delivery — Eventbrite retries a failed delivery every 10 minutes, up to 10 times.

Related Eventbrite nodes

See Event run in a workflow.

In a technical demo we add the Eventbrite connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.

Book a technical demo Talk to sales