MetaLocator can import location data directly from an Airtable base. This allows you to use an Airtable table as the source for your MetaLocator location records.
This article explains how to create an Airtable Personal Access Token and configure the Airtable import connection in MetaLocator.
Before You Begin
You will need:
Access to the Airtable account that owns or can access the base you want to import
Permission in Airtable to create a Personal Access Token
Access to the MetaLocator account where you want to import data
An Airtable table containing the data you want to import
Create an Airtable Personal Access Token
MetaLocator connects to Airtable using an Airtable Personal Access Token.
Log in to Airtable.
Open the Airtable Builder Hub.
Go to Personal access tokens.
Click Create token.
Give the token a clear name, such as MetaLocator Import.
Add the following scopes:
data.records:readschema.bases:read
Under token access, add the Airtable base or bases that MetaLocator should be allowed to access.
Click Create token.
Copy the token and store it somewhere secure.
The token is only shown when it is created. If you lose it, you will need to create a new token or regenerate the existing one.
Recommended Airtable Token Permissions
For MetaLocator imports, the token only needs read-only access:
Scope | Purpose |
| Allows MetaLocator to read records from the selected Airtable table |
| Allows MetaLocator to list available bases, tables, and views |
You should only grant access to the Airtable base or bases that you want to use with MetaLocator.
Configure the Airtable Import in MetaLocator
Log in to MetaLocator.
Click Locations (or Data)
Click Import
Choose Airtable as the import source.
The Airtable connection screen will open.
Paste your Airtable Personal Access Token into the Personal Access Token field.
Click Test Connection.
If the connection is successful, MetaLocator will display a success message and load the Airtable bases available to your token.
Select the Airtable Base, Table, and View
After testing the connection:
Choose the Airtable Base you want to import from.
Choose the Airtable Table that contains your location records.
Optionally choose a View.
If you select a view, MetaLocator imports the records available in that Airtable view. This is useful when you want to import only a filtered set of records.
If you leave the view blank, MetaLocator imports all records from the selected table.
Continue to Field Mapping
After selecting the base, table, and optional view:
Click Next.
MetaLocator will retrieve the Airtable data.
Continue through the normal import process.
Map the Airtable fields to the appropriate MetaLocator fields.
Review and complete the import.
Airtable fields are converted into a CSV-style import file behind the scenes, so the remaining steps work like other MetaLocator data imports.
Keeping Airtable Data in Sync
Some MetaLocator accounts may see an option labeled Keep Airtable Data In Sync?
When enabled, MetaLocator creates the Airtable import as a background sync job. This allows MetaLocator to refresh the imported data automatically on a recurring basis.
Be sure to publish and schedule the new background job if you checked the Keep Airtable Data In Sync? option by clicking Background Jobs as shown below. Then enable the Published and Scheduled toggles for your new Airtable Job.
If you do not see this option, your account may not include background import support.
How Airtable Field Values Are Imported
MetaLocator reads the fields from Airtable records and prepares them for import.
Common field types are handled as follows:
Airtable value type | How MetaLocator imports it |
Text, numbers, dates, and other simple values | Imported as the field value |
Checkbox values | Imported as |
Multiple select or linked record arrays | Imported as comma-separated values |
Attachment fields | Imported as comma-separated attachment URLs |
Complex nested values | Imported as JSON text |
Troubleshooting
“Personal Access Token is required”
Enter your Airtable Personal Access Token and try again.
“Unable to connect to Airtable”
Check the following:
The token was copied correctly.
The token has not expired or been revoked.
The token includes the required scopes.
The token has access to the Airtable base you want to import.
No bases are listed after testing the connection
The token is valid, but it may not have access to any bases. Edit the token in Airtable and add the correct base to the token’s access list.
No tables are listed after selecting a base
Confirm that the selected base contains tables and that the token has access to the selected base.
The wrong records are importing
Check whether you selected a specific Airtable view. If a view is selected, MetaLocator imports records available in that view. To import all records from the table, leave the view blank.
The import fails after clicking Next
Verify that:
The Airtable token is valid.
The selected base, table, or view has not been deleted or renamed.
The selected table contains records.
The Airtable API is available.
The token still has access to the selected base.
Security Notes
Treat your Airtable Personal Access Token like a password.
Do not share the token publicly.
Do not send the token over unsecured channels.
Grant only the scopes required for the import.
Limit token access to only the bases MetaLocator needs.
Revoke the token in Airtable if it is no longer needed.