Skip to content

Stacksync × Supabase Miami: AI-Native OperationsOct 13Reserve your spot

New

Stacksync MCP is here. Give Claude, Cursor, and any MCP client governed access to your syncs, workflows, and connections.

Set up MCP
Database · Two-way sync platform

Airtable connector for two-way sync.

Keep Airtable and your business systems aligned with Stacksync. Sync Attachments, Records and Formula fields within the connector’s object and field requirements, with two-way sync for eligible records.

Set this up from Claude or ChatGPT
  • Configure field mappings and sync direction
  • Inspect and resolve record errors in one dashboard
Setup guide: how Stacksync connects to Airtable

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Record types

Airtable objects and coverage.

Start with the records your workflow needs. Object-specific permissions and operation limits are shown alongside the available coverage.

Records
Check object and field eligibility in the setup guide.
Attachments
Check object and field eligibility in the setup guide.
Formula fields
Check object and field eligibility in the setup guide.

Read the Airtable object and setup guide

Connection setup

Airtable connection requirements.

Check the account access and change-detection requirements for your environment. Your system administrator can help confirm permissions before the first sync.

Connection method
REST API (per-base Web API plus metadata and webhooks endpoints)
Account access
OAuth (Airtable OAuth grant to specific bases or all resources); the authorizing user must have a creator role, since only creator roles can create webhooks
How changes are detected
The connector uses incremental updates. Formula fields do not emit ordinary change notifications and are refreshed hourly.

Sync directions

  • Read data Documented
  • Write data Documented
AirtableStacksync setup guide
Setup prerequisites for your administrator
  • Authorize access to the intended bases through OAuth with an Airtable creator role, which is required to create webhooks.
  • Check formula and attachment fields separately from ordinary editable fields.

Documentation checked September 15, 2026.

Setup guides and technical references

Integration design

Match records and fields for your Airtable integration.

Define the row/document key, external application identity, required types, and relationship model. Decide how nested values, nulls, schema changes, and deleted parents appear in the other system.

Use your account’s actual field names when applying these matching and dependency checks.

Explore record matching and field-mapping checks
AirtableSource record IDKeep the account and record type
Record matchingSource ID ↔ destination IDLink the same record across systems
Selected destinationDestination record IDPreserve its local key and rules
Conceptual identity model. Keep source and destination IDs linked so an update reaches the right record. Confirm the supported sync direction separately.
Match the same record in both systems
Retain the source record identifier together with its base and table context. A display name or formula result is a poor matching key because it can change without identifying a new record.
Load related records in the right order
Resolve linked-record references separately from attachment content. Decide which destination fields store an attachment reference and which process, if any, needs the file itself.

Mapping checks by record type

Attachments

See connector requirements

Identity
Keep file/object ID, container, and version. A path can change and a filename can repeat.
Fields to consider
Source file ID · Container reference · Version · Metadata · Access classification
Related records to resolve first
Resolve folder/container and parent-record references before attaching metadata.
Test before going live
Test a renamed file, a new version, a moved folder, and an access-restricted document.

Download the field-mapping workbook (CSV) to capture the actual API fields, matching keys, owners, and test results. Use it as you build with your team or a Stacksync engineer.

Setup and validation

Validate the Airtable integration in four steps.

Repeated delivery reaches one intended record; related data remains addressable and incompatible values produce an observable failure.

View the four setup tests and expected results

  1. Confirm the intended Airtable account and grant

    Use the documented setup with the intended account and environment. Check that the authorizing user can grant access to the selected objects; test reauthorization without changing the mapped record identity.

    Expected result: The connection reaches the intended account, and the integration owner can renew or revoke the grant through the agreed procedure.

  2. Measure formula freshness separately

    Update an ordinary field and an input to a formula, then record when each destination value changes. The connector documentation specifies hourly formula refreshes.

    Expected result: The acceptance target distinguishes ordinary record updates from the documented formula refresh cycle.

  3. Test writes in the directions you need

    Select one eligible Airtable object and writable field. Test the required create/update direction, an invalid value, and a repeated delivery. Check object-specific restrictions before enabling the return path.

    Expected result: The selected operation is confirmed, addresses the intended record, and exposes rejected values for repair.

  4. Test recovery and name the support owner

    Interrupt a non-production transfer, restore the connection, and reconcile the selected Airtable records. When using Stacksync’s Retry to sync action, check the latest source value: the retry re-reads current source state rather than replaying an immutable historical event.

    Expected result: The records have the expected current values, repeated delivery creates no duplicate business record, and your team knows who handles unresolved errors.

Use the production-readiness checklist to record test results, assign support owners, and agree on when to go live.

Troubleshooting

Troubleshoot your Airtable integration.

Diagnose record matching, delayed changes, and rejected operations
A formula appears older than the record beside it
Check the formula refresh window before treating it as a failed ordinary update. For missing record changes, verify that the authorizing user has the creator role needed for webhooks.
The first load looks correct but later results differ
The connector uses incremental updates. Formula fields do not emit ordinary change notifications and are refreshed hourly. Measure the original source change, its capture, and the destination observation separately. Confirm whether the affected object is incremental, historical-only, or subject to a special refresh cycle.
One operation succeeds while another is rejected
Check the specific Airtable object, field permissions, required references, and allowed operation. A successful read does not establish that a create, update, deletion, or business action is available.

Review retry, replay, and recovery behavior before repeating an operation that may already have succeeded.

Review your Airtable workflow with an engineer

Airtable integration guides

FAQ

Airtable connector FAQ

How should I plan an integration with Airtable?

Ordinary records, formula values, and attachments need separate acceptance checks. Stacksync supports two-way sync for eligible objects. Start with one workflow, agree on which fields each system owns, then test initial data, later changes, and recovery before expanding.

Can the Airtable connector write changes back?

Stacksync supports reads and writes for eligible Airtable objects. Check the selected fields, account permissions, and the other system’s connector. Update an ordinary field and an input to a formula, then record when each destination value changes. The connector documentation specifies hourly formula refreshes.

Which identifiers should I preserve for Airtable data?

Retain the source record identifier together with its base and table context. A display name or formula result is a poor matching key because it can change without identifying a new record.

Which related records should I load first for Airtable?

Resolve linked-record references separately from attachment content. Decide which destination fields store an attachment reference and which process, if any, needs the file itself.

What should I check if Airtable data is missing or delayed?

Check the formula refresh window before treating it as a failed ordinary update. For missing record changes, verify that the authorizing user has the creator role needed for webhooks.

What will we cover in a Airtable integration demo?

Start with one workflow and a sample record from Attachments. We can review how to identify the record, connect related data, set the update direction, and test recovery. Include the person who owns the source system and anyone who will maintain the integration; you do not need a finished requirements document.

AI assistant

Set up Airtable from Claude or ChatGPT

Connect the Stacksync MCP server to your AI assistant, then ask for the sync in plain language. You only sign in; there is no code to write and no API key to paste.

1. Add the Stacksync MCP server

Server URL

https://mcp.stacksync.com/mcp

In Claude

  1. Open Customize → Connectors, select + Add, then Add custom connector.
  2. Name it Stacksync and enter https://mcp.stacksync.com/mcp.
  3. Select Connect, sign in to Stacksync and choose your workspace.

In ChatGPT

  1. Open Settings → Apps → Advanced settings and turn on Developer mode.
  2. Select Create app, name it Stacksync, enter https://mcp.stacksync.com/mcp and choose OAuth.
  3. Sign in to Stacksync, then enable Stacksync from the tools menu in a chat.
Set up Codex or Claude Code

Codex

codex mcp add stacksync --url https://mcp.stacksync.com/mcp
codex mcp login stacksync

Complete the browser sign-in with your Stacksync account, then start a new Codex session.

Claude Code

claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp

Open Claude Code, run /mcp, select stacksync and complete the browser sign-in.

Then ask: “List my Stacksync workspaces.” Sign-in connects your assistant; it does not create a sync yet.

Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI and other assistants: setup steps in the docs.

2. Ask your assistant

Create a sync between my Airtable and another app or database.

Also from the same chat

You can also ask for workflows and AI agents (Genies) that use Airtable. The assistant checks what each app supports, for example:

  • “Build a workflow that messages our team in Slack when a Airtable record changes.”
  • “Create a Genie that answers questions about our Airtable data in Slack.”

What happens next

  • Signs you in with your Stacksync login (OAuth). No API key is pasted into the chat.
  • Gives you a secure sign-in link for each app it connects; you open it and sign in to that app.
  • Builds the sync with your permissions in Stacksync, nothing more. Turn on Ask before every change in the MCP settings to approve each change first.

New to Stacksync? Create an account first, then sign in from your assistant.

AI assistant setup

Use Airtable through Stacksync MCP.

Explore capabilities and setup →

Explore Airtable connections

Choose the other system in your workflow. Each guide explains the connection options, available operations, field mapping, and setup checks for that pair.

289 integration guides

CRM · 45

ERP · 39

Database · 49

Data warehouse · 29

Business productivity · 41

Accounting and finance · 17

AI · 5

Analytics · 7

Communications · 5

Developer tools · 11

E-commerce · 8

Human resources · 14

Marketing · 9

Security and identity · 6

Storage · 4

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2SSH TunnellingSSL certificatesIP WhitelistingVPN gatewayVPC peeringand more
Coworkers laughing in front of a laptop in a casual office setting

Connect the systems your business runs on.
Build your next workflow with Stacksync.

Book a demo Get started