Save Eventbrite attendee updates to Airtable

Every time an attendee is updated in Eventbrite, FlowMattic adds a new record to your Airtable table, giving you a running log of attendee changes that you can sort, filter and share.

Eventbrite

Airtable

Download this workflow Browse more workflows

2 steps Setup ~5 min Used on 903 sites Free to import

The Save Eventbrite attendee updates to Airtable workflow on the FlowMattic canvas, with 2 steps across Eventbrite, Airtable — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

Attendee details change after registration: names get corrected, ticket holders are swapped, answers are edited. Eventbrite shows the current state, but not always a history you can work with. This workflow writes each change into Airtable as its own record, so you have a log to review before the event.

The Eventbrite Attendee Updated trigger fires when an attendee is updated, and passes the attendee's details, as Eventbrite sends them, on to Airtable.

The Airtable Create Record step then adds a new row to the base and table you choose. It ships unmapped: after import, connect Airtable, pick the table and map the attendee fields into your columns. Add a column for the time of the change, so the log reads in order.

Because the step always creates, a person who is updated three times appears in three records. That is what makes it a change log, not a single attendee list. Make a test edit on an attendee in Eventbrite and check Task History to see the fields that arrive and Airtable's response.

Audit trail for name changes

A conference team that prints badges checks the Airtable log the day before the event to catch every name correction made since registration.

Ticket transfers at a sold-out show

A venue sees in Airtable when an attendee record changes hands, so door staff know which name to expect on each ticket.

Reporting on attendee edits

An event agency groups the Airtable records by event to show a client how many attendee details changed after sales closed.

How this workflow runs

What happens at each step once the workflow is on, and what you need before you import it.

Step 1Trigger
Eventbrite Attendee Updated
Runs each time Eventbrite reports a change to one of your attendees. The attendee's current details, as Eventbrite sends them with the change, are passed to the Airtable step.
Step 2Action
Airtable Create Record
Adds a new Airtable record for each update. The step ships unmapped, so pick the base and table and map the Eventbrite attendee fields into the columns you want in the log.

What you need

FlowMatticCore
Eventbrite AccountAccount
Airtable AccountAccount

After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.

Make it yours

Changes worth making after you import it.

Add a created-time field in Airtable so every record shows when the update arrived, then sort the log by that field.
Map the attendee ID into its own column, so you can group all records for one person and follow their changes in order.
If you only care about one event, put a Filter on the event ID between the Eventbrite trigger and the Airtable step.

Questions about this workflow

Does this update an existing Airtable record for the attendee?

No. The step is Create Record, so each Eventbrite update adds a new record. To keep one row per attendee instead, you would use Airtable's Search Record and Update Record steps in place of Create Record.

Does a new Eventbrite registration also create a record?

This workflow listens for attendee updates. Whether a fresh registration also counts as an update depends on what Eventbrite sends, so make a test registration and look at Task History.

Which attendee fields can I save in Airtable?

Any that the Attendee Updated trigger sends. Edit a test attendee, then choose from the trigger data when you map each Airtable column.