Skip to main content
Connect Airtable in Workspace settings → AI → Connections. You need permission to manage integrations in Conversion and Creator access to the Airtable bases you select during authorization. One Airtable account connects to each Conversion workspace. Its permissions and the bases you authorize determine what Conversion can access. Use a dedicated account: Airtable attributes writes to the connecting user, and API edits from that account are ignored to prevent agents from waking themselves.

​
Choose what starts the agent

On a custom agent’s Configuration tab, add an Airtable trigger. Choose your Base, Table, and Event. For example, choose Record updated and add Status is Ready. Add Type is Email or Newsletter to narrow the requests. Every field condition must match; a field can accept multiple values. Text matches exactly, including capitalization. You can filter text, number, checkbox, and single- or multiple-select fields. Use Record created when complete records arrive from a form or API. To respond to both creation and updates, add a trigger for each event with the same conditions. Conditions are configured in Conversion. Airtable views remain useful for organizing records, but changing a view’s filters does not change your agent’s conditions. Different agents can use different conditions on the same base. They share one webhook subscription. Existing matching records do not start sessions when you save the trigger. A matching event of the selected type can start one. Initial subscription setup usually takes about a minute; changes before activation are not backfilled. Fields and select options are saved by ID, so renaming them preserves conditions. Remove or replace conditions if you delete their fields or options. Older view-based triggers must be edited to use conditions before they can start new sessions; existing linked conversations continue.

​
Continue in comments

The first matching record event starts one session per agent and record. Later record changes return to that session, even when the record no longer matches the starting conditions. New comments on that record also reach its linked agents, even when the agent is paused or its original trigger has been deleted, as with Linear conversations. Delete the agent or disconnect Airtable to stop those conversations. Record changes use webhooks. Airtable does not send comment notifications through its Webhooks API, so Conversion checks comments periodically on a separate maintenance schedule. Comment checks continue while the record has a session link and Airtable remains connected. Comments can continue an existing conversation; they do not start one by themselves. The agent can read the record and its recent comments, update editable fields, and post a comment or reply. Comments are prefixed with the agent’s name. These tools use the record linked to the session, so the agent cannot choose another record to modify. Configure Requires approval, Automatic, or Disabled on the agent’s Tools tab as needed.

​
Attachments

The agent can inspect attachment fields and download individual files into its sandbox, up to 25 MB per file. It resolves the attachment against the current record when downloading because Airtable’s download links expire. It can upload a sandbox file into an attachment field, up to Airtable’s 5 MB direct-upload limit. For larger outputs, it can share a download link in a comment. See Files and sandbox.

​
Connection health

In AI settings, open Airtable’s menu and select Connection details to see subscription errors and events waiting to be retried. Contact support if the pending count does not clear. Reconnect if access was revoked or the connected account lost permission. A subscription that expired or lost payload history needs an explicit Restart subscription. Restart watches future changes; it cannot reconstruct events Airtable has already discarded. Review affected records and update any missed work that matches your starting conditions. Conversion renews active subscriptions while retrieving their payloads. Airtable keeps payload history for seven days, so an extended outage can leave a gap even after reconnecting.