<!-- BusyBot node reference — https://busybot.net/tools/eventbrite-trigger/ -->

> Node: Eventbrite Trigger (`eventbrite_trigger`) · Webhook trigger · v1
> Category: Marketing · Credentials: Eventbrite (`eventbriteApi`)
> Updated: 2026-08-16

# Eventbrite Trigger

> Triggers on Eventbrite events such as orders, check-ins, and event updates

## Overview

Receives webhook notifications from Eventbrite when event-related actions occur, such as order placements, attendee check-ins, event updates, and ticket changes. The incoming payload contains an api_url pointing to the full resource; when Resolve Data is enabled, the trigger fetches the complete object from that URL. Supports filtering by organization and specific event. Validates that incoming api_url values belong to the Eventbrite API domain to prevent SSRF. Useful for automating ticket fulfillment, attendee tracking, event analytics, and notification workflows triggered by Eventbrite activity.

**Category:** Marketing  
**Tool Name:** `eventbrite_trigger`  
**Version:** 1

**Appearance:** Icon: `lucide-CalendarCheck` | Color: `#f05537`

## Node Type

**Trigger** — webhook (receives incoming HTTP callbacks)

## Input / Output

| Direction | Port(s) |
|-----------|--------|
| Input | None (trigger node) |
| Output | `Output` |

## Credentials

This tool requires **Eventbrite** credentials.
See the [Credentials Guide](https://busybot.net/credentials/eventbrite-api/) for setup instructions.

### Parameters

| Parameter | Type | Required | Default | Description |
|-----------|------|----------|---------|-------------|
| Authentication | `options` | No | `privateKey` | Authentication method to use for Eventbrite API calls. |
| | | | | Options: `privateKey` (Private Key), `oAuth2` (OAuth2) |
| Organization | `string` | Yes | — | The Eventbrite Organization ID to listen for events on. Retrieve from your Eventbrite account settings. |
| Event | `string` | Yes | `all` | Limit the triggers to a specific Eventbrite event. Use "all" for all events, or enter a specific event ID. |
| Actions | `multiOptions` | Yes | `[]` | Which Eventbrite actions to subscribe to. Select one or more webhook event types. |
| | | | | Options: `attendee.checked_in`, `attendee.checked_out`, `attendee.updated`, `event.created`, `event.published`, `event.unpublished`, `event.updated`, `order.placed`, `order.refunded`, `order.updated`, `organizer.updated`, `ticket_class.created`, `ticket_class.deleted`, `ticket_class.updated`, `venue.updated` |
| Resolve Data | `boolean` | No | `true` | By default the webhook payload only contains an api_url reference to the object. When enabled, the trigger automatically fetches the full object data from the Eventbrite API. |

## Output Data

Each delivery from Eventbrite produces one output item, built from the webhook payload plus three added fields:

- `_trigger` — always `eventbrite_webhook`
- `_timestamp` — ISO 8601 timestamp of when the request arrived
- `_webhookEvent` — the action Eventbrite reported, taken from `config.action`

The Eventbrite payload itself carries:

- `api_url` — the Eventbrite API address of the object that changed, e.g. an order or an attendee
- `config` — the delivery's own metadata, with `action`, `endpoint_url`, and `webhook_id`

Deliveries whose `api_url` is not on the Eventbrite API domain are rejected. Eventbrite's own test delivery produces a single item carrying `_webhookEvent: "test"` and a `placeholder` message instead of real data — perform the action in Eventbrite to see a real payload.

Reference the payload downstream by expression, e.g. `{{ $json.api_url }}` or `{{ $json.config.action }}`.

## Usage Examples

- Start a workflow when a new ticket order is placed on Eventbrite
- Trigger a notification when an attendee checks in at an event
- Automate follow-ups when an Eventbrite event is published
- Sync order data to a CRM when an Eventbrite order is updated

## Example Configuration

Fire on every order placed or refunded across the organization:

```json
{
  "type": "eventbrite_trigger",
  "parameters": {
    "authentication": "privateKey",
    "organization": "123456789",
    "event": "all",
    "actions": ["order.placed", "order.refunded"],
    "resolveData": true
  }
}
```

Watch attendee check-ins for one specific event:

```json
{
  "type": "eventbrite_trigger",
  "parameters": {
    "authentication": "privateKey",
    "organization": "123456789",
    "event": "987654321098",
    "actions": ["attendee.checked_in", "attendee.checked_out"],
    "resolveData": true
  }
}
```

Track event lifecycle changes:

```json
{
  "type": "eventbrite_trigger",
  "parameters": {
    "authentication": "privateKey",
    "organization": "123456789",
    "event": "all",
    "actions": ["event.created", "event.published", "event.unpublished", "event.updated"],
    "resolveData": false
  }
}
```

### Trigger Behavior

- **Activation:** When the workflow is activated, a webhook endpoint is registered with the service.
- **Deactivation:** The webhook is automatically unregistered when the workflow is deactivated.
- **Payload:** The incoming webhook payload is parsed and output as workflow items.
- **Verification:** Supports signature verification where applicable.

## Tips

Entry point that fires when Eventbrite sends a webhook for subscribed actions (orders, attendees, events, etc.). Configure the organization, optionally scope to a specific event, and select which actions to listen for. When Resolve Data is enabled, the trigger fetches the full object from the Eventbrite API instead of returning just the api_url reference.