Getting started with Airtable sync

You can either choose an existing grid view in a table or create a new grid view just for setting up the source for this sync. In most cases, we recommend creating a new view. You can duplicate a grid view that matches your needs if an existing one already exists.

In either case, remember that the source view may have filters, hidden fields, or field or table editing permissions. Each of these settings could impact the way that the sync can be configured in the destination base. Once you have created the new view or chosen an existing view you can move on to the next step.

1. After determining or creating a grid view to use as the sync source, find the Share and sync button and click it. We cover more about the view share menu in this article.

2. This will open a menu of options. Click Sync data to another base.

3. From here, you'll next toggle on the option to Allow data in this view to be synced to other bases.

4. This will cause additional configuration settings and sync options to appear. You can move on to the next step now.

You should now see a screen similar to the one shown below:

There are additional settings to consider:

• Allow data in this view to be synced outside of your org unit (Enterprise Scale/Business plans only) - By default, this option is toggled off. Additionally, this setting may be overridden by “Synced view restrictions” set in your organization’s admin panel settings.

• Allow edits from other bases (Enterprise Scale/Business plans only) - AKA enabling two-way sync. Learn more here.

• Sync linked records - This feature enables you to sync linked data across multiple bases while maintaining the links between records in different tables. Learn more about this feature below.

Depending upon who will be setting up the destination(s) for the sync you might take a few different actions here:

• You are ready to set up the destination sync in a base you have access to - Click Sync this view and choose the appropriate location to sync to. Then, move on to step 5 below.

• Another user will set up the sync in a base where you don't have access - Click Copy shared view link and send the other user that link so that they can use it for setup purposes. Alternatively, other users (with access to this base) can choose a specific view with syncing enabled to set up a sync destination in another base when creating a new table.

• You want to enable users across your organization to sync this data (Enterprise Scale/Business plans only) - Consult this support article about data sets for more information.

If you clicked Sync this view in the last step you can skip to the next step, otherwise, navigate to the base where you want to set up the sync and follow these steps:

1. Click + Add or import to begin creating a new table.

2. Under Add from other sources choose the Airtable base option.

3. This will open a configuration window where you can either select the Base, Table, and View to use as the source or enter the shared view link from the previous step. Click Next when you are ready to move on.
   

Whether you added the new destination sync from the source view or chose a source view from the sync destination base, you'll be brought to an additional configuration window. From here:

1. Choose to sync:

   • All fields in the source or

   • Specific fields in the source...
     

   • Note that the Advanced section includes the option to set a different primary field for the sync. This is covered in another section below.

2. Click Next. Additional options will appear that include:

   • Whether or not users can Edit source records. This option may not always be available, as two-way syncing will need to be enabled. We cover that option in more detail in this article.

   • Sync frequency - Can be set to automatically update the sync or only sync manually. More information about these options is listed in the dependencies section below.

   • Record deletion behavior - Can be set to delete when records are deleted in the source or to be kept in the base even when they are deleted in the source. Again, more considerations are available in the dependencies section.
     

Once you have configured the sync the way you'd like click Create table.

After clicking Create table, it may be a moment before the table appears, especially when syncing over larger sets of data. A few considerations now that the sync has been set up:

• The table's name in the destination will appear as the name of the synced view. In certain cases, you may want to change the table name to something else.

• If you'd like to go back and adjust a sync's settings later, then navigate to the Update sync configuration option from the destination table's drop-down menu.

• You may also want to set a table description so that other users know where the data is coming from and who to contact if the sync breaks.

¹ Automatic syncs will eventually stop on bases that don't have any recent activity. To keep automatic syncs active make sure that some kind of action (i.e. create a record, update a record, create a new view, etc.) is being performed in the base on a regular basis.

Note

Airtable Sync is unavailable on Free plan workspaces.

• Sync reads per source base - 400 reads per minute

  • Reaching this limit is uncommon in most use cases.

  • Essentially, this is a limit on how many times synced tables can read from a source base for the purpose of syncing from it.

• Maximum number of syncable source views per base - 100 share views with sync enabled per base

  • Each source view can have a large number of destinations (targets), however, a single base cannot exceed 100 views that have sync enabled on them.

• Record limit per integrated sync source - 10,000 records maximum

  • This limit only applies to integrated syncs. This limit does not apply to syncs that occur from one Airtable base to another Airtable base. In those cases, the limit would relate to the number of records that a base can have according to plan type.

Syncing is one-way process to get information from a source table in a base to a destination table in a base, unless the option to edit records has been enabled in both the source and the destination sync. For one-way syncs, this means that in the destination base you cannot:

• Add or delete records in the synced table

• Edit information in the fields that are synced

However, you can do many of the same things you can do with any regular table, including:

• Link existing tables to synced tables

• Create multiple views of the synced records

• Add additional fields to the synced records to enrich them

• Add a last modified field to see when the record was last synced

• Add a button field to open the original record to edit it

• Refer to the synced records from other tables using linked records and lookups

• Use a view of the synced table to trigger automations

• Field types that will sync in the same format - Attachment, date, long text (Rich text), multi select, number, single line text, single select, and user ¹

  • ¹ User field types in syncs created before March 14th, 2023 will sync as text fields. To have user fields sync in the same format, a user with creator permissions would need to recreate the sync in a new table. Note that this may not always be a feasible workaround in every scenario and it's important to think of the potential downstream effects of breaking the original sync.

• Computed field type - Formulas, rollups, and other computed field types that produce text, numbers, or dates will sync as their result type

• Field types that sync as text - Linked record (unless configured properly), lookup, buttons with the Open URL action, and created by

• Field types that will not sync - Authenticated attachments

• Adding a record (new rows may be added to the end of the view on the destination table)

• Editing a record

• Deleting a record

• Adding a field (“sync all fields” must be turned on)

• Changing a field’s configuration (supported fields)

• Deleting or restoring a field

• Changing the view’s filters or hidden fields

Reordering, grouping, or sorting records.

In the sync configuration process, there is an option to sync manually or automatically (Workspaces on the free plan will not see an option to sync automatically).

• Turning on automatic syncing will cause the synced table to update in real-time. You can still manually sync a table, even if you have turned on automatic syncing. There are a few exceptions to real-time sync behavior:

  • Time-based formula fields (and all dependent fields) will not be instant – instead, they will periodically update.

  • Table syncs with Field Type Customized Linked Records will not be instant – instead, they will periodically update.

Note

Automatic syncs will eventually stop on bases that don't have any recent activity. To keep automatic syncs active make sure that some kind of action is being performed in the base on a regular basis. This can be accomplished via Airtable Automations or API. The idea is that by having either of these options periodically make an update to a base you will be able to trigger the automatic sync to run.

• Manual sync can be accomplished on any plan at any time you choose. To manually sync your table click on the synced table's dropdown menu and click "Sync now". After you click the table will begin to update and save any changes. This process may take more time depending on the amount of information being synced. You will see an "All changes saved" message when the sync has finished successfully.

From the sync configuration window, you can choose to sync all fields from the view or just some:

• If you choose to sync all fields, then new fields added in the sync source will show up in the synced table when the next sync occurs.

• If you choose to sync just some fields, then any new fields added in the source table will not sync until you have toggled them on as visible from the sync configuration window.

Note

If you do not see a table that you are expecting as an option, then you may need to check (or have a collaborator check) the settings in the source table/view.

You can also choose how to handle records that are deleted or hidden in the source view. You can either delete or keep them in the destination table.

Note

If you choose the Delete the records in this table option, and records are deleted in the source table or filtered out of the synced view at any point in time, any additional information added to the synced destination table (e.g. linked records or other data in fields) will be removed.

Should you choose to Leave the records in this table you will be able to manually delete specific records that have been deleted in the sync source by clicking the Delete unavailable records... option.

Note

We recommend carefully considering your primary field choice to ensure it meets your needs from the start. Once a primary field is selected for your destination table, it cannot be changed after the sync is created. To modify the primary field, a new destination table will need to be created.

While you are configuring a sync you'll arrive at the Advanced drop-down option on the Select fields to sync section. This option allows you to choose a specific field that will act as the primary field in Airtable. Primary fields should contain unique information in each cell to act as the primary key. Additionally, only certain field types are allowed to be used in the primary field.

Warning

If the field type in the sync source for this field is hidden or changed to an unsupported field type, then it will cause the sync to fail in the destination table. Consider locking the view being used as the sync source to prevent this from occurring.

After you've configured and created a synced table, you can customize each of the fields. To do this, click the drop-down next to the field's name, click Customize field type, and choose the field type that you want to change the field to.

There are some important things to note about this feature:

• If a field has had its type changed in the target base, that will take precedence over the field type from the source base.

• Multi-source syncs will have different options than single-source syncs. These are covered in a separate article on multi-source syncing.

1. Navigate to the base where an existing sync source view has been configured or follow the steps covered here to create a new sync.

2. Click on the Share and sync button.

3. Click the Sync data to another base option.

4. Click the Sync linked tables option. You’ll see the number of tables connected to the table/view via one or more linked record fields that you are configuring as a source sync. Additionally, there is a preview of how many of those tables contain an existing syncable share link that you can choose from in the next step.

   

5. The next step will depend on whether you are:

   • Choosing a syncable view already configured - Use this option when you already know of a view that contains the settings appropriate to your use case for syncing.

     1. Next to the “Default view” section click the Select a default view drop down. If you are updating a previously configured source sync, then you might see the name of the current default view to click.

     2. Choose which syncable view you would like to set as the default view. The number of syncable views will be determined by how many have already been set up in the linked table that you are connecting with.

     3. Click the arrow symbol ↗ to open a new tab in your browser if you need to make any modifications to the syncable share view that you’ve selected.

        

   • Creating a new syncable view - Use this option when you need to create a new syncable share view in the other table.

     1. Click the + Create new syncable view option.

        

     2. A view creation window will appear. Give the new view a name and toggle on the option to “Allow other bases to edit data in this created view” in order to allow two-way syncing.

        

     3. Click Create view

     4. The sync configuration window should update the “Default view” section with the view you created.

        

6. You can now share the view link with your colleagues to utilize are continue building by moving on to configure the sync in one or more destination bases.

When setting up syncs containing linked tables there will be an additional step to choose whether or not to include the additional tables required to allow for linked records to be preserved within the base where you are setting up the destination sync.

Note

You will need Editor permissions or higher in the sync source base in order to see and configure the steps outlined below.

For those without editor+ permission on the source base, you could obtain additional shared view links from another collaborator who does have access to the additional linked data that you want to add. Once the additional synced tables are present in target, you can link them via the synced linked records upconversion flow outlined in the “Upconverting previously synced linked record fields” section below.

1. Follow step 4 in the “Configuring a basic sync” section.

2. When you reach the “Sync linked tables” window during the configuration process all available linked tables will be chosen by default.

   • Feel free to adjust this by clicking the check icon next to each linked table that you do not want to include in the sync.

   • Remember that not choosing to include a linked table will result in linked record fields that appear as single link text rather than linked record field types.

   Once you’ve configured the sync linked tables, click Next.

3. Configure the sync settings covered in step 5 of the “Configuring a basic sync” section. Then, click Create tables. This will create the main source table as well as any additional linked tables selected in the previous step.

Prior to August 2024, linked record columns were synced as plain text. In order to use the newer synced linked records functionality, you will need to convert any of these older linked record fields. Converting these fields also involves syncing the additional tables necessary to use this feature.

To convert a linked record field:

1. First, you’ll need follow the steps listed in the “Configuring a basic sync” section. The goal here is to sync in any extra source tables that contain linked record relationships not currently represented in the destination base. In some cases, you may be able to click the option Go to linked table in order to configure a new syncable shared view link.

   

2. Once you’ve synced in the additional necessary source tables, navigate to the destination table where a linked record field needs to be converted.

3. Click the dropdown next to the linked record field’s name.

4. Select the option Convert to linked records. If the option is not clickable, then the necessary synced table is still not synced into the destination base.

   

5. Finally, a confirmation modal with appear. Click Connect to finish the conversion process. Keep in mind that it may take a moment for Airtable to process the conversion on the backend before the linked records will appear in the synced linked record field.

   

• Multi-source syncing is not supported.

• Self-linked records are not supported—only linked record fields that are creating a relationship between two tables are supported.

• Dynamic filtering is not inherited from the source base.

• If a linked record is not shown in the source view for the sync due to filtering conditions, then we will not be able to reference all of the information contained within that record. In these cases, we will only reveal a partial set of information about the linked record that is filtered out of the source view, but still present in the table where the source view resides.

When you configure a table sync, you can choose to manually or automatically sync changes to your base.

• Automatic syncing between Airtable bases occurs in real-time¹

• Automatic syncing between a sync integration and an Airtable base will occur as often as 5 minutes, but may take longer at times.

• Automatic syncs will eventually stop on bases that don't have any recent activity. To keep automatic syncs active make sure that some kind of action (i.e. create a record, update a record, create a new view, etc.) is being performed in the base on a regular basis by automations, humans, or a combination of the two.

• Automatic syncing is only available on paid Airtable plans.

¹ Time-based formula fields (and all dependent columns) will not be instant – instead, they will periodically update. Table syncs with Field Type Customized Linked Records will not be instant – instead, they will periodically update.

Airtable only supports syncing from grid views. It is not possible to set up a sync from calendar, gallery, kanban, timeline, list, or Gantt view types. However, those view types can be recreated in the destination table after the sync has been configured from the initial grid view.

Sync integrations can be managed from the workspace settings page as outlined in this support article.

In the Sync Activity log, if you have access to the destination base, you'll see the name of the base and the user who configured the sync. If instead, you see "an anonymous base" or "unknown user", this is due to one of the reasons below:

• You do not have access to the base

• The destination base has been deleted

If you're concerned about who might have access to the shared view link to set up a synced table, you can:

• Regenerate your shared view link - When you do so, the sync will pause on all destination bases until it is re-authenticated. The users on the destination bases will see an error icon, along with the time the table last synced. To re-authenticate, they'll need the new syncable view share link. To use that link, click the dropdown next to the destination table, click Update sync configuration, and insert the new link.

• Enable a password and/or email domain restrictions on the shared view link - If the view share link is restricted to example.com, an example.com Airtable account will be required to sync that view to any base. You can learn more about sync permissions here. Note that these restrictions can break existing syncs or published data sets that depend upon this shared view link.

We respect password and email domain restrictions. For example, if the view share link is restricted to dundermifflin.com, a dundermifflin.com Airtable account will be required to sync that view to any base. Learn more about sync permissions here.

The sync will pause until it is re-authenticated. You’ll see an error icon ⚠️, along with the time the table last synced.

To re-authenticate, you’ll need a new syncable view share link. Then, click the dropdown next to the destination table, select Update sync configuration, and provide the new link.

It’s likely the case that someone is adjusting the filtering conditions (or hiding records) in the source view. If a record is filtered out of the source view, then, depending on your particular sync's settings, that record will in turn be removed from the destination table. If a record is removed from the destination table, that record will unlink from any linked record fields to that table.

You can address this issue is by locking the source view 🔐 (paid plans only), to prevent other collaborators from inadvertently changing the filtering conditions. You can also consider renaming the source view to warn people to not change the view’s filtering conditions

If the shared view is domain-restricted and the user that set up the sync loses access to the source base, the sync will pause. It may be worthwhile for an admin user to set up important syncs so that they are not interrupted.

By design, changing field names in a sync destination is meant to be difficult to change since formula fields, scripting, API calls, automations, and more may depend upon the current name of a field in the destination. For that reason, field names in the source and destination may not match if the name has been updated in the source. Use caution when using the workaround described and consider using the field manager to understand the dependencies in your base.

To update a destination table to match the name of the field in the sync source, first, navigate to the synced destination table and click the dropdown next to its name. Then, click Update sync configuration. This will open the sync configuration window. From here, click on the three-dot icon next to the source you would like the field's name to match and select Edit synced fields. If the Specific fields in the source option has not already been selected, choose that option. Then, toggle off the field that you'd like the name to match and hit Save. Next, you'll follow the same steps, this time toggling the option to sync that same field back on and then click Save once more. Optionally, you can repeat the process one more time by choosing the All fields in the source and fields added in the future option to return the sync configuration back to that functionality as well.

You can add a button field with the ‘Open Source Record’ action. If the button is grayed out, the record has been deleted or hidden in the source view.

Yes. For example, if you sync a view with 1,000 records from a source base (where the records originate from), the destination base (where you want to sync the records) will count the 1,000 synced records towards that base's total record limit.

Yes. Similar to record limits, attachments in a synced table will count against the attachment limit in that synced table's base.

Yes. However, daisy-chained syncs will not be reflected in sync sources/destinations enabled for two-way syncing.

Yes. If you choose to keep records in the destination base when they are deleted in the source base, then you can add a sync source record button field. If the button is not clickable, then the record was deleted, hidden, or filtered out of view in the source base.

No. Record comments are scoped only to the base where the record resides. The records that reside in the destination table have a different record ID than the records in the source table, which means that even though there is a connection via the sync that you've set up, the records in each table are technically unique.

While we don't support linking to individual records across multiple bases, you can add related tables into the same base. This case study demonstrates how a Airtable user interlinks dozens of tables into a single base.

There are several options to consider when turning off a sync:

• Turning off a sync from the source view - In some instances, you may want to disable a sync source. Keep in mind that this will break any connection to existing sync destinations, so they will be unable to continue to sync the data moving forward.

  • To disable a source view navigate to the base → table → view where you want to stop allowing syncs. Click the Share and sync button. Then, click the Sync data to another base option. Next, toggle off the “Allow data in this view to be synced to other bases” option.

• Turning off a sync from a destination table - In other instances, you may want to disable a sync in a destination table. This is a good option to use when you want to “freeze” the data according to it’s most recent sync. The table will remain and the sync could be re-established in the future if needed. Keep in mind that you could also change the sync frequency to be “Only sync changes when requested” if you currently are automatically syncing the data.

  • To disable a destination sync, navigate to the base → destination table. Click the dropdown next to the name of the table. Click the Update sync configuration option. Next, you can either:

    • Change the sync interval to be unsynced by clicking the Change button under the “Settings” section next to the current interval setting. Then, choose the “Stop syncing changes and convert to unsynced table” option on the next page. A confirmation modal will appear where you will need to click Remove to break the sync.

    • Remove an individual source, which can be helpful in multi-source syncs. To accomplish this, click the … icon next to the source you want to remove. Then, click Remove source.

• Deleting a source or destination table - This option should be used with caution, but there are time when you may need to delete a source or destination table. Keep in mind that deleting sync source tables can affect the data in downstream destination syncs depending on the destination sync’s settings. Reference this article if you want to learn more about deleting a table.