The Airtable Plugin can be used to pull data from Airtable into Bubble, as well as update Airtable records from Bubble workflows. The ideal use case for this plugin is to supplement your Bubble application with Airtable data, or vice versa. We don’t recommend using Airtable as your sole database because using your Bubble database will generally be more performant, since it won’t require API calls.
Add new records to your Table. To use this action, check the box to “Create & Modify” this Table in the Plugins tab.
Enter the type of record to create. This will match the name of the Table where you want to add the record.
Remove existing records from your Table. To use this action, check the box to “Delete” from this Table in the Plugins tab.
Enter the type of record to delete. This will match the name of the Table where you want to remove the record.
The existing record to delete. For example, if you are displaying a list of records from Airtable in a repeating group, this could be the current cell’s thing.
Enter the type of record to modify. This will match the name of the Table where the record exists.
The existing record to modify. For example, if you are displaying a list of records from Airtable in a repeating group, this could be the current cell’s thing.
Install the Airtable Plugin in the Plugins tab of the editor. Click “Add another Account” and fill out your Account Label and API Key.
The Account Label can be a label of your choosing. To find your API key, log into your Airtable account and navigate to https://airtable.com/account. Your API Key is here:
Start adding your Tables! Click “Add another Table”, then configure your Table information by first selecting a Base, then selecting a Table from the dropdowns. You can also optionally specify a View - this will impact the order in which your data returns from Airtable. For example, if you wish to see your records in the same order as they appear in your Table’s Grid view, specify this when you save your Table.
After you’ve saved your Table, you’ll see a popup where you can see your schema, make necessary changes, and specify which Tables your linked records refer to.
Once set up, the app will be able to read and write to the connected Airtable base(s). For example, in a dynamic statement, you can use "Get data from an external API" to select the Airtable base as the API provider. Upon doing so, you can even add search constraints.
You will also be able to write changes back to Airtable, via workflow actions that will show up in the "Plugins" section of the action selector.
The field type dropdowns in the initialization popup have four special data types unique to Airtable: Attachment, Collaborator, Barcode, and Link to Record(s). This is for ease of use, to make it easier for you to map your Airtable columns to Bubble types. In practice, Attachment fields can be used like a list of images or files. Barcodes can be used like text. Since Collaborators and Links are native to Airtable, these fields must be pulled directly from Airtable when using a Table as data or creating/modifying records.
The filtering mechanism is done in the request we send to Airtable, so we have done as much as we can using the current API.
Some fields in Airtable are generated by other fields, such as Rollups or Counts. Therefore, these cannot be altered or created via API calls.
Make sure your permissions are set accordingly. To use a Table in the Create and Modify actions, you must give it Create & Modify permissions. The same stands for the Delete action.
You can use files or images in Bubble to create or modify Attachment fields in Airtable, and you can use text to create or modify barcodes. For linked records and collaborators, you must pull this directly from Airtable. For example, if you want to create a new record with a collaborator field, you would have to have that collaborator on another record already and pull from that.
Currently you can only send text and numbers over to Airtable. All other types, like the Date field*,* will cause an error as it is not yet supported.
If you rename a table that you have previously connected, this can cause existing references to fail until Bubble knows the updated name. You can resolve this by going into your Plugins tab, finding the particular instance whose table name you want to update, and clicking the Base dropdown as if you would select a different base but selecting the same base again. You should now see the new table name.