Short answer: Drop the "Eventbrite → List Eventbrite Events" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Organization ID organizationId | string | Required | Organization ID |
Status status | options | Optional | Status. Options: All, Draft, Live, Started, Ended |
{"organizationId": "{{trigger.organizationId}}","status": "{{trigger.status}}"}
{"events": [{"id": "evt123","end": {"utc": "2026-06-15T17:00:00Z"},"url": "https://www.eventbrite.com/e/tech-conference-tickets-123","name": {"text": "Tech Conference 2026"},"start": {"utc": "2026-06-15T09:00:00Z"},"status": "live"}]}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.