Connecting Airtable to Automate.io

There are two methods to connect Airtable to Automate.io.

Method 1:
Go to APPS in your dashboard. Click the blue ‘+’ button on the top-right. You will see a ‘Add a new app’ pop-up.

Search for Airtable in the search box. Select Airtable. You will see a window that prompts you to validate the app.

Enter your API key and then click Validate to give Automate.io access to your Airtable account. To get your API key, click 'Account Settings' above.

Then hit Save. You now have successfully connected your Airtable account to Automate.io.

Method 2:
While creating a Bot, you can directly connect Airtable either as a Trigger or an Action app. Refer to 'Connecting the Trigger app' or 'Connecting the Action app' in How to create a Bot.

Using Airtable with Automate.io

Now that the connection is successful, it’s time for the real fun—creating bots to automate your tasks. You will need to set up a trigger and action(s) to do that. To learn what these terms mean, check out our Automate.io terminology page.

You can integrate Airtable with so many of your favorite apps—support, collaboration, payments, forms, etc.

Things to remember:

Before you connect an Airtable base to Automate.io, make sure that its first two rows are filled with some data. If the rows are empty, enter some dummy data.

Limitations

  1. While setting up your triggers, we only support fields that are of 'View' type. These are: grid, form, calendar, gallery, and kanban.
  2. We currently support 50 columns in a table.
  3. In the 'Search Records' action, 'Search by Field' will not be applicable on ‘multipleSelects’, ‘singleCollaborator’, ‘multipleCollaborators’, ‘multipleRecordLinks’, ‘multipleAttachments’, ‘formula’, ‘rollup’, and ‘lookup’ fields.

Common issues and solutions

I get this error: INVALID_MULTIPLE_CHOICE_OPTIONS Insufficient permissions to create new select option ""In Progress"".

Workaround: This error occurs when you pass a value to a field in your Bot that doesn't exist in your Airtable base or table. As a workaround, make sure that the value you are passing to the field exists in your Airtable base.

Did this answer your question?