Airtable integration

What it does

The Airtable integration lets your agency operate on a client's bases without leaving TaskJuice. Connect a client's Airtable account once and your workflows can list and search records, fetch a single row by ID, create new records, patch existing ones, delete records, and react whenever rows are added or updated in a watched table.

Connect an Airtable account

1. Open your workspace in TaskJuice and navigate to Connections.
2. Choose Airtable and click Connect.
3. Sign in with the Airtable account that owns or has been invited to the bases you want to automate.
4. Grant the requested scopes: data.records:read, data.records:write, and schema.bases:read.
5. Pick which bases this connection can access on the Airtable consent screen, then return to TaskJuice with the connection ready to use.

To revoke access at any time, visit Airtable integrations and remove the TaskJuice entry.

Triggers

• airtable/new-record polls a selected table and fires for every record whose Last Modified Time field advanced past the prior poll, including newly inserted rows. One activation per poll cycle carries every record observed in an items array; drop a Loop node downstream to process each record individually.
• airtable/updated-record shares the same polling shape but is intended for workflows that must react to every edit on an existing record, not just creations.

Actions

• airtable/list-records returns records from a selected base and table with optional view, formula filter, page size, and continuation token.
• airtable/get-record returns a single record by its Airtable record ID.
• airtable/create-record inserts a new record with a field map and an optional typecast flag.
• airtable/update-record patches the supplied fields on an existing record without touching the rest.
• airtable/delete-record removes a record from a table.

Known limitations

• Each Airtable record list response returns at most 100 rows. Use the offset continuation token returned with the response to fetch the next page.
• Airtable rate-limits each base to 5 requests per second per access token. When a 429 is returned, TaskJuice surfaces it as a retryable rate-limit error and respects the recommended backoff.
• Polling triggers depend on a Last Modified Time field on the watched table. Add one through the Airtable column picker before activating the trigger; without it the watermark cannot advance reliably.
• Airtable's Web API webhooks ship a thin notification ping that requires a second call to fetch the diff. TaskJuice does not use these today; polling List Records works uniformly on every base without extra setup.