Unsupported-source pipeline
A system that isn't on Airtable's official Sync list gets pulled into a base on a real refresh schedule anyway, built directly against that system's own API instead of waiting for Airtable to add official support.
Airtable Sync is Airtable's native feature for pulling live, read-only data from a supported outside source, think Jira, Salesforce, or Google Calendar, directly into a table inside your base, refreshed on a schedule instead of pasted in by hand. It's a specific, narrower feature than linking tables inside the same base, and it only moves data in one direction.
Once you connect a supported source, Sync creates a table that refreshes on an interval you choose, pulling fresh records from that source automatically. The resulting table is read-only inside Airtable: you can view and reference that data elsewhere in your base, but you can't edit the synced records directly, since the source system stays the system of record.
Airtable maintains the list of sources Sync supports, and it's a fixed, specific list, not every tool a business runs shows up on it.
Two gaps show up constantly. The first is simple: the system you actually need isn't on Airtable's supported source list at all. The second is structural: even for a supported source, Sync only pulls data in. A status change made directly in Airtable never pushes back out to update the original system, because that's not what the feature was built to do.
Both gaps are exactly the custom integration work we build, usually directly against each system's own API. When a source doesn't expose what's needed through an API at all, we build the connection through browser-based automation instead of treating it as a dead end.
A system that isn't on Airtable's official Sync list gets pulled into a base on a real refresh schedule anyway, built directly against that system's own API instead of waiting for Airtable to add official support.
A status change made directly in Airtable pushes back out to the original source system automatically, something native Sync's one-directional design doesn't do at all.
If a system you depend on isn't on Airtable's official Sync list, or you need data to flow the other way too, tell us which one and we'll scope the build.
Tell us which system, and whether you need data flowing one direction or both. We'll scope what it takes to build that connection directly. Airtable Sync doesn't have to be where your business is actually stuck for this to be worth a conversation.
Let's talk →Airtable maintains an official list that includes tools like Jira, Salesforce, and Google Calendar, among others. The exact list changes over time, so check Airtable's current documentation for what's supported today.
No, synced tables are read-only inside Airtable. The connected source stays the actual system of record.
No, it only pulls data into Airtable. Pushing a change made in Airtable back out to the source system isn't something native Sync does.
That's where custom automation picks up, built against that system's own API, or through browser-based automation if it doesn't expose an API at all.
Availability and the number of synced sources you can run depend on your plan, so airtable.com/pricing has the current breakdown.