From January 25th, 2022, we are rolling out a small change to the URL format for Airtable tables, views and records used by Automations triggers and actions.
The change is that the base ID (appXXXXXXXXXXXXXX) will appear at the start of the URL. This change coincides with the recent decision to include base IDs in Airtable URLs throughout the rest of the product. The change in the record URL format will occurs in these places:
The url property of a record output by a trigger/action.
Example record output by a trigger/action:
The url property of a Table or View model retrieved by the Run Script action.
Example run script:
Potential breaking changes: This may be a breaking change if your automation makes hard assumptions about the format of a url property (e.g. by deconstructing the returned URL into its component parts with substring() or similar). In this case, to manage the transition, please update your automation to be able to handle both the new format and the old format.
No action should be needed if your automation only uses the URL for browser navigation. We will support browser navigation for the old-style Airtable URLs via redirects. That said, we may not support these redirects indefinitely.
Custom URL Constructors: If you built an automation that constructs Airtable URLs from scratch, we recommend updating the construction logic to also include the base ID. URLs with the base ID are supported from the time you’re reading this.
Full list of triggers:
- Record enters view
- Record created
- Record updated
- Record matches conditions
- Form submitted.
Full list of actions:
- Create record
- Update record
- Find records
- Run Script
Let us know if you have any questions!