Airtable sync

Mirror your event into an Airtable base so the automations your team already built keep firing.

Go to Settings → Integrations and press “Connect Airtable”.
Paste a personal access token from airtable.com/create/tokens and your base ID.
The token needs four scopes: data.records:read, data.records:write, schema.bases:read, schema.bases:write. The base ID is the app… part of the base URL.
Connecting creates three tables in your base — Submissions, Speakers, Sessions — and fills them.
If those tables already exist, Trackstage adopts them instead of making duplicates. Rows are matched on a Trackstage ID column, so re-syncing never doubles anything up.
From then on it keeps itself up to date: within seconds of a change, plus a sweep every five minutes.
The card shows when it last synced and how many rows are in each table. “Sync now” forces a run.

One way by default. Trackstage writes to Airtable and doesn’t read back, so edits you make in Airtable are overwritten on the next sync.

Experimental: sync Status changes back. Switch it on under the Airtable card and a submission’s Status column becomes two-way — triage in Airtable, and the decisions land in Trackstage on the next sync. Only that one column comes back. Draft and Withdrawn can never be set from Airtable, a row has to be mirrored once before it’s eligible, and if the same submission changed in both places, Trackstage wins — the overruled Airtable edit is written to Settings → Activity so you can see what was ignored.

If a sync fails you get a “Last sync didn’t finish” message on the card with Airtable’s own error. Disconnecting only forgets the token; your Airtable rows stay.