- Connecting Airtable with Mesa
- Unsupported field types
- Potential Use Cases
Connecting Airtable with Mesa
When you're setting up your first workflow with Airtable, you'll need to add your Airtable account API key so that Airtable is a connected app within Mesa.
You can find the API key on your Airable account page. Paste the API key into the Airtable Step and click on Add Credential. Then, you are all set!
Locating your Base & Table
Airtable Triggers and Actions both require a Base and Table to be configured.
To find your Base*, make sure that you are logged into Airtable and then go to airtable.com/api. Click on your Base from the list. On the next page, your id will be listed in green with the label The ID of this base. Example:
The Table* will be the label from your Airtable interface, for example: "Restaurants", "Orders", or "City Districts".
Afterwards, your App Configuration should look something like this:
Locating your Record ID
In specific Airtable actions, you may be required to enter a Record ID. To locate your Record ID, click here to learn more.
Updating Tokens in Mesa
If you have an Airtable Record Updated or Airtable Record Created trigger added in your workflow, you will see an Update Available Tokens button:
Once you have added the Base and Table, you will be able to click on this button to update the available Tokens in Mesa that you can use in later steps in the same workflow.
To locate your available Tokens, you can click open Fields within the Token Selector.
Retrieving fields from your Airtable Table
Note: Your fields will display in the order that they were defined when you set up your Airtable Table. If you are viewing your table's data in an Airtable View, the order of the columns may be different.
In specific Airtable actions, we can automatically detect the fields in your Airtable Base and add them to Mesa through the Retrieve Table Fields button:
If no fields appear or if the fields are missing, make sure you have at least one record in your Airtable table with a value in each column.
Sending data with different field types
Airtable provides a variety of field types that lets you store data in each record. For more information about field types, please view Airtable's documentation here..
When using Mesa's Token feature, you will want to make sure that the data (that represents each token) matches Airtable's expected format. When the data does not match Airtable's expectations, your automation will fail. Here is an example of a failed automation due to some formatting issues.
If you find that your automation is failing due to your Base's field types, you can reach out to our team at email@example.com and our team would be happy to take a look.
Unsupported field types
Currently the following field types are unsupported in Mesa and will not be added to the Mesa interface:
- Multiple Select
- Links to other Tables if "Allow linking to multiple records" is enabled
If you need support for either of these fields, please let us know! Our team adds features based on popularity.
The Record Updated and Record Created Triggers run on a polling system. Mesa makes a request to Airtable every hour to look for created or updated records and triggers the necessary Workflows. During testing, Mesa will look for created and updated records every time the workflow is saved.