dev@sessioncanvas.local
Airtable stays the organizers' source of truth; Session Canvas mirrors every submission out and reads decisions back in.
Authorised by dev@sessioncanvas.local on 10 Aug 2026, 19:53.
Granted scopes
Rows created directly in Airtable are counted but not imported — creating submissions from Airtable is out of scope. Applying a status change from Airtable never emails anyone, including an acceptance.
The last sync was over 15 minutes ago, so a fresh one was started in the background. Refresh in a moment to see it.
You will sign in at airtable.com and choose which bases this app may see. We never see your Airtable password, the grant is limited to the bases you tick, and you can revoke it from Airtable at any time. Come back here to pick the base and table the sync should use.
Creating the table needs an Airtable token with the schema.bases:read and schema.bases:write scopes — separate from the record scopes the sync itself uses. This connection has both.
Field names are the contract your Airtable automations are built on, so they are spelled the way a person would label a column. Extra columns of your own are left untouched.
| Field | Airtable type | Contents |
|---|---|---|
| Title | Single line text | Proposal title. |
| Status | Single select | The one column we read back. Options: Submitted, Maybe, Accepted, Declined. |
| Speaker Name | Single line text | Primary speaker. |
| Speaker Email | Primary speaker's address. | |
| Company | Single line text | Speaker's company. |
| Track(s) | Single line text | Comma-joined track names. |
| Format | Single line text | Session format name. |
| Submitted At | Date (with time) | ISO 8601 timestamp. |
| App URL | URL | Deep link back to the submission in Session Canvas. |
| Description | Long text | Abstract, truncated to 2,000 characters. |
| Started | Direction | Result | Counts |
|---|---|---|---|
| 10 Aug 2026, 21:18took 2.7s | Two-way | Success | 30 pushed · 0 pulled |
| 10 Aug 2026, 21:11took 2.7s | Two-way | Failed | 0 pushed · 1 pulled · 30 failedSpeakers: creating rows failed — Airtable responded 403: Invalid permissions, or the requested model was not found. Check that both your user and your token have the required permissions, and that the model names and/or ids are correct. · Sessions: creating rows failed — Airtable responded 403: Invalid permissions, or the requested model was not found. Check that both your user and your token have the required permissions, and that the model names and/or ids are correct. |
| 10 Aug 2026, 20:03took 3.6s | Two-way | Success | 22 pushed · 0 pulled |
| 10 Aug 2026, 19:56took 955ms | Two-way | Failed | 0 pushed · 0 pulled · 22 failedUpdating rows failed: Airtable responded 422: Record ID recrsxxxxxxxxxxxx does not exist in this table |
| 10 Aug 2026, 19:55took 1.1s | Two-way | Failed | 0 pushed · 0 pulled · 22 failedUpdating rows failed: Airtable responded 403: Invalid permissions, or the requested model was not found. Check that both your user and your token have the required permissions, and that the model names and/or ids are correct. · Airtable responded 403: Invalid permissions, or the requested model was not found. Check that both your user and your token have the required permissions, and that the model names and/or ids are correct. |