Airtable triggers start a run from what happens in a table. All three are instant — Airtable tells Bizomate the moment it happens:

  • Airtable · New record — When a record is added to a table.
  • Airtable · Record updated — When a record's fields change.
  • Airtable · Record matches a view — When a record enters a view.

Publishing adds a webhook to the base for you, and nothing needs pasting — see How instant triggers work.

Who can do this

Workspace Admins and Editors, on every plan. Viewers see the trigger and its status but cannot change it.

In Airtable, the person whose token the connection uses needs Creator access to the base, because adding a webhook needs it.

Before you start

An Airtable connection whose token has the webhook:manage scope and includes the base — see Connect Airtable.

Steps

  1. Open the workflow in the designer and open the trigger picker — Browse all triggers on an empty workflow, or select the trigger and Change how it starts.
  2. Under Airtable, select the event. It reads Airtable · instant. Or type Airtable in Search triggers.
  3. In Connection, choose your Airtable connection.
  4. In Base, choose the base — Bases the token was given. For example Consulace CRM.
  5. In Table, choose the table — Clients. For New record: Each record added starts one run. Instant triggers need the token's webhook:manage scope.
  6. For Record updated: optional, in Fields to watch, a field — Stage, say. Only a change to this field starts a run — to watch several, use a value with their names separated with commas. Empty: any field.
  7. For Record matches a view: in View, choose the view — for example Ready to invoice. A record starts a run when it comes to match the view's filters — added, or changed so that it does.
  8. The panel reads Publishing sets this up in Airtable, and every publish sets it up again. It stays while the workflow is published — switched off, what arrives is ignored — and is taken away when the workflow is deleted or starts another way.
  9. Add the steps, then Publish. Bizomate adds a webhook to the base. The panel reads Waiting for the first event — Make one happen; it appears here within seconds.

Test with a real event:

  1. Make the event happen in Airtable — add a record, or change Stage.
  2. Within seconds the panel reads Listening — instant — Last event 10:45 · Record updated · Northwind Logistics.
  3. On Output, select Use the last event, then Test run.

What the trigger gives

The record, read back from Airtable as the Airtable steps read it — id, url, createdAt and each field by its name, {{ trigger.Company }}, {{ trigger.Stage }} — and:

Field What it is
baseId, tableId, tableName Where the record is — appX1y2Z3, tblQ4r5S6, Clients.
user Who made the change in Airtable, by name or email.
changedFields Record updated only: the names of the fields that changed — ["Stage"].
missedWindow Only on the first run after Bizomate had to make the webhook again (below): from and to, the times between which changes may not have reached Bizomate.

What happens next

  • Each record starts one run of the live version, in Production, named after its primary field — New record · Northwind Logistics. A record changed twice in quick succession, inside one delivery, starts one run.
  • Each workflow has its own webhook on the base. Every publish sets it up again; changing to another trigger, base or table and publishing, or deleting the workflow, removes it.
  • Airtable ends a webhook after 7 days unless it is renewed. Bizomate renews each one daily, so you do nothing.
  • A webhook that lapsed anyway — deleted in Airtable, or not renewed in time — is made again at the next daily renewal. The first run after that carries missedWindow, so a workflow can catch up — with Find records, say — on what changed between from and to.

How Bizomate knows an event is Airtable's

When it makes the webhook, Airtable gives Bizomate a secret for it, kept encrypted. Airtable signs every call with it (the X-Airtable-Content-MAC header). A call whose signature does not match is answered 401 — The signature does not match. — and starts nothing. The call only says something changed; Bizomate then fetches the changes from Airtable itself.

Good to know

  • Record matches a view starts a run when a record comes into the view — added, or changed so that it now passes the view's filters — not for records already in it. A filtered view works best.
  • A record edited by hand, field by field, can start a Record updated run for each change. Watch only the fields that matter.
  • A record deleted before Bizomate reads it still starts its run, with the values Airtable sent.
  • Airtable allows 10 webhooks per base. Each published workflow with an Airtable trigger on that base uses one.

If something goes wrong

What you see Why What to do
Not listening — Airtable would not take Bizomate's address: Airtable would not make a webhook on the base: the token needs the webhook:manage scope. Edit the token in Airtable, then publish again. Fix it, then publish again. The token lacks webhook:manage. Add the scope to the token in Airtable, then publish again.
Not listening — Airtable would not take Bizomate's address: Airtable refused: … Fix it, then publish again. The account is not a Creator of the base, or the base already has 10 webhooks. Fix the access, or remove a webhook, then publish again.
Not listening — … View is empty. Choose the view records enter. … or … Clients has no view “…”. Choose the view again. … No view is chosen, or it was renamed or deleted. Choose the view, then publish again.
Not listening — … Clients has no field named “Stage”. Refresh the fields and choose again. … A field to watch was renamed or deleted. Choose the field again, then publish again.
Waiting for the first event stays Nothing has happened yet, the changed field is not the one you watch, or the record did not enter the view. Make the event happen.
Nothing has arrived yet — make one happen in Airtable, then try again. on Output No event has reached the trigger yet. Make one happen, wait for Listening — instant, then Use the last event.
A run did not start for an event the panel shows The workflow is switched off, or its workspace is archived. Switch it on — see Switch a workflow on or off. The missed event does not run later.