An Airtable connection lets workflows create, update, find and delete records, and upload attachments — and start a run the moment a record is added, changed or enters a view. It connects with a personal access token that you make in Airtable, limited to the bases you choose.

Who can do this

  • In Bizomate: workspace Admins and Editors, on every plan — Airtable is not a premium connection. Viewers see the connection but cannot add or change it.
  • In Airtable: anyone can make a token for their own account. It reaches only the bases you add to it, and only what your account may do in them. Triggers need Creator access to the base, because they add a webhook to it.

Scopes the token needs

Scope What it is for
data.records:read Every step and trigger reads records with it
data.records:write Create, update, upsert and delete records, and upload attachments
schema.bases:read The Base and Table lists, and each table's fields and views
webhook:manage Every Airtable trigger — they are instant
user.email:read (optional) Lets the test show your email; without it, it shows your Airtable user id (usr…)

Without any of the first three, the connection is not saved. Without only webhook:manage, it is saved and every step works, but a trigger cannot be published.

Steps

In Airtable, make the token:

  1. Sign in to Airtable and go to airtable.com/create/tokens — or select your account icon, then Builder hub, then Personal access tokens.
  2. Select Create new token.
  3. In Name, type Bizomate.
  4. Under Scopes, select + Add a scope and add each of the four scopes above.
  5. Under Access, select + Add a base and choose each base your workflows use — for example Consulace CRM. Or choose all current and future bases in a workspace.
  6. Select Create token. Copy it — it starts pat. Airtable shows it only once.

In Bizomate, add the connection:

  1. Select Connections in the bar at the top, then + Add connection.
  2. Under Productivity, select Airtable. It reads "Stored credential".
  3. The window notes: Scopes to tick — data.records:read, data.records:write, schema.bases:read, and webhook:manage for instant triggers. Optional: user.email:read, so the test can show your email. The test says which are missing.
  4. In Connection name, type a name — for example Consulace Airtable.
  5. Paste the token in Personal access token — placeholder pat…. Airtable › Builder hub › Personal access tokens › Create token. Give it the four scopes below, and the bases its workflows use.
  6. Leave Test the connection before saving ticked. Bizomate asks Airtable whose token it is and which scopes it has before keeping it.
  7. Select Save connection. The button reads Testing while Airtable is asked.

The toast "Connection added" says what Airtable answered — for example "“Consulace Airtable” is ready. Reached rohan@consulace.com · 4 of 4 scopes."

What happens next

  • The connection appears under Productivity. Its panel shows Replace token, Test and Revoke — never the token. Stored encrypted. Secret fields are never shown again after you save.
  • Test answers with the account's email (or, without user.email:read, its user id) and how many of the four scopes the token has — Reached rohan@consulace.com · 4 of 4 scopes, or Reached rohan@consulace.com · 3 of 4 scopes — instant triggers need webhook:manage.
  • Airtable steps and triggers list it under Connection. Their Base list shows the bases you added to the token, each with your access — Consulace CRM · Creator, · Can edit, · Can comment or · Read only.

Good to know

  • The token is tried before it is saved. A token Airtable refuses, or one missing a record or schema scope, is never kept.
  • A base missing from the list has not been added to the token. Edit the token in Airtable, add the base, then select Refresh on the list. The token itself stays the same.
  • Adding a scope later keeps the same token too — edit it in Airtable, and nothing changes in Bizomate.
  • To replace the token — after you regenerate it in Airtable, say — open the connection's panel and select Replace token, paste the new token and select Replace token. The old one is used until then. The toast "Token replaced" says "Workflows that use “Consulace Airtable” use the new key from their next run."
  • Signing in with Airtable instead of a token is not offered yet; the token is the only way to connect.

If something goes wrong

What you see Why What to do
Airtable refused it — "Airtable refused: … Check the connection's details on Connections. Nothing was saved." The token was mistyped, regenerated or deleted. Copy the token again, or make a new one.
Airtable refused it — "Reached rohan@consulace.com, but the token lacks data.records:write and webhook:manage. Edit the token in Airtable and add them. Nothing was saved." The token was made without a scope the steps need. Edit the token in Airtable, add the scopes it names, and save the connection again.
"Fill in Personal access token." The box is empty. Paste the token.
Nothing to pick — "The token reaches no base. Edit it in Airtable, add the bases its workflows use, then Refresh." No base was added to the token. Add the bases in Airtable, then Refresh.
"Could not reach Airtable: …" or "Airtable did not answer within 30 seconds." Airtable could not be reached. Try again in a few minutes.