- Getting started with Airtable
- Introduction to Airtable basics
- Contacting Airtable Support Updated
- Airtable home screen
- Glossary of Airtable terminology
- Airtable technical requirements
- Feature differences between Airtable on desktop and mobile
- Airtable keyboard shortcuts
- Using Markdown in Airtable
- Adding descriptions in Airtable
- Finding Airtable IDs
- Airtable Automations
- Automations Overview
- Automation feature walkthroughs
- Integrated automation walkthroughs
- Airtable automation walkthroughs
- Linking existing records using automations
- Conditional groups of automation actions
- Repeating groups of Airtable automation actions
- Creating recurring records using automations
- How to delay Airtable automation runs
- Prevent automations from triggering by mistake
- Use automations to timestamp status updates
- Automation Triggers
- Airtable Triggers
- Airtable automation trigger: When record matches conditions
- Airtable automation trigger: When a form is submitted
- Airtable automation trigger: When record created
- Airtable automation trigger: When record updated
- Airtable automation trigger: When record enters view
- Airtable automation trigger: At scheduled time
- Airtable automation trigger: When webhook received
- Airtable automation trigger: When a button is clicked
- Airtable automation trigger: When email received Updated
- Integrated Triggers
- Airtable Triggers
- Automation Actions
- Airtable Actions
- Airtable automation action: Send email Updated
- Airtable automation action: Create record
- Airtable automation action: Update record
- Airtable automation action: Find records
- Airtable automation action: Sort list
- Airtable automation action: Run a script Updated
- Airtable automation action: Generate with AI
- Integrated Actions
- Airtable automation actions: Slack
- Airtable automation actions: Google Workspace
- Airtable automation action: Send MS Teams message
- Airtable automation actions: Outlook
- Airtable automation actions: Jira Cloud
- Airtable automation actions: Jira Server / Data Center
- Airtable automation actions: Salesforce
- Airtable automation action: Create post in Facebook Pages
- Airtable automation actions: GitHub Issues
- Airtable automation action: Hootsuite post
- Airtable automation action: Send Twilio SMS
- Airtable Actions
- Airtable Bases
- Using Airtable Cobuilder
- Airtable bases overview
- Creating and managing Airtable bases
- Structuring bases in Airtable
- Moving bases between workspaces in Airtable
- Creating and managing tables in Airtable
- Creating Airtable base share links
- Importing third-party data into Airtable
- Using insights in Airtable
- Troubleshooting Airtable base performance
- Airtable Betas
- Collaborating in Airtable
- Airtable Enterprise Support
- General Enterprise information
- External badging in Airtable
- Using app library and components in Airtable Updated
- Ask an Expert beta overview
- European data residency at Airtable
- Airtable user groups overview
- Airtable Enterprise API
- Creating and managing data retention policies in Airtable
- eDiscovery APIs in Airtable
- Airtable and data loss prevention
- Accessing Enterprise audit logs in Airtable
- Set up Jira Server / Data Center to connect with Airtable
- Admin panel pages
- Airtable admin panel overview
- Users - Airtable enterprise admin panel
- Airtable admin panel user details
- Groups - Airtable admin panel
- Workspaces - Airtable Enterprise Admin Panel
- Bases - Airtable admin panel
- Interfaces - Airtable admin panel
- Data sets - Airtable admin panel
- Managed apps - Airtable admin panel
- Components - Airtable admin panel
- Reports - Airtable admin panel
- Settings - Airtable admin panel Updated
- Managing Enterprise organizations
- Managing Enterprise admins in admin panel
- Using Organizations
- Organization branding for apps in Airtable
- Enterprise Hub in Airtable
- Enterprise Hub: Org unit assignment with user groups Updated
- Deactivating, removing access, and reactivating users in the admin panel
- Managing user access to workspaces and bases
- Airtable Enterprise Key Management Updated
- Custom terms of use New
- Enterprise SSO
- General Enterprise information
- Airtable Extensions
- Airtable Fields
- Fields Overview
- Attachment
- Date-based fields
- Formula
- Getting Started with Formulas
- Formula Foundations
- The essentials of Airtable formulas
- Formula writing tips for beginners
- Troubleshooting formulas
- Basic calculations
- Conditional statements
- Logical arguments
- Working with dates
- Displaying DATETIME_FORMAT using the date field in Airtable
- Working with date functions in Airtable
- Calculating the difference between dates in Airtable
- Supported DATETIME_DIFF unit specifiers in Airtable
- Supported DATETIME_FORMAT format specifiers in Airtable
- Using the DATETIME_PARSE() formula in Airtable
- Working with timezones
- Record functions
- Text functions
- Numeric functions
- Common Solutions: Beginner
- Common Solutions: Intermediate
- Common Solutions: Advanced
- Long Text Field
- Linked Record Field
- Linking records in Airtable
- Limiting linked record selection to a view in Airtable
- Dynamic filtering in linked record fields
- Linking to one, many, or a subset of Airtable records
- Converting existing fields to Airtable linked records
- Reordering record links in Airtable
- Understanding linked record relationships in Airtable
- Number-Based Fields
- Other Fields
- Rollup, lookup, and count fields
- Select and user fields
- Integrating with Airtable
- API
- Getting started with Airtable's Web API
- Creating personal access tokens
- Airtable Webhooks API Overview
- Service accounts overview
- Airtable Web API - Using filterByFormula or sort parameters
- Airtable API Deprecation Guidelines
- Airtable API: Common troubleshooting
- Managing API call limits in Airtable
- URL length limitations for web API requests
- Integration services
- Third-party integrations via OAuth overview
- Troubleshooting disconnected OAuth integrations in Airtable
- Options for integrating with Airtable
- Third-party integrations - Common troubleshooting
- Low-code integrations - Common troubleshooting
- Integrating Airtable with external calendar applications
- Visualizing records from Airtable in Tableau
- Visualizing Airtable records in Microsoft Power BI & Power Query
- Integrating HubSpot with Airtable
- Using Zapier to integrate Airtable with other services
- Using Zapier's Multi-Step Zaps to find and update records
- Using IFTTT to integrate Airtable with other services
- Integrating with AWS Lambda & DynamoDB
- Developer tools
- API
- Airtable Interface Designer
- Interface Designer overview articles
- Interface layouts
- Interface elements
- Adding and removing elements in interfaces
- Adding layouts to interfaces
- Formatting elements in interfaces
- Interface element: Button
- Interface element: Calendar
- Interface element: Chart
- Interface element: Filter
- Interface element: Gallery
- Interface element: Grid
- Interface element: Kanban
- Interface element: Number
- Interface element: Record picker
- Interface element: Text
- Interface element: Timeline
- Learning and Resources
- Managing Airtable
- Airtable Policy
- Airtable Records
- Airtable Sync
- Airtable Views
- Airtable Workspaces
- Print
- Share
- DarkLight
- PDF
Airtable automation trigger: When a form is submitted
- Updated on 19 Dec 2024
- 4 Minutes to read
- Print
- Share
- DarkLight
- PDF
Learn how to use the “When a form is submitted” trigger to kick off an automation run. Think of this automation trigger as the beginning step of the ability to automate custom workflows that will follow a form submission.
Introduction
All plan types with varying limitations | |
Permissions |
|
Platform(s) | Web/Browser, Mac app, and Windows app |
Related reading |
Setting up an automation to trigger when a form is submitted
Step 1: Create a new automation
To start creating an automation, from the open base of your choice click on Automations in the upper left corner of your screen to open the automation configuration window. Click the + Create automation option to begin the setup process. If you would like, you can rename the automation right away to make it easier to understand what it does.
Step 2: Configure the “When a form is submitted” trigger
Next, you will need to click + Add trigger option.
Once clicked, the available triggers will be displayed for you to choose from. Choose the When a form is submitted option.
Under the “Table” section, select the table containing the view you want this automation to watch.
Under the “Form” section click Select a form.
From here, choose the standalone form or form view of your choice.
Step 3: Test the trigger
It’s important to test the trigger at this point so that you can utilize dynamic tokens in the automation action steps. This trigger allows you to pull in information from the record that triggered this automation such as record ID or created time (when the form was submitted). Those are just a few examples, but there is much more information that you can potentially use in later automation steps.
Step 4: Add one or more automation actions
Check out our help center’s Automation actions section to learn more about each action Airtable offers.
Just as one example, a helpful action you can pair with this trigger is the update record action. You can then categorize records (by single select field for instance) that are created from a form. This is beneficial for situations when there may be a mix of records being created externally (via a form) and internally (by Airtable collaborators). We cover this use case example below.
Step 5: Test and turn on the automation
Again, be sure to test all of the steps in the automation that you are building. Once every part of the automation has tested successfully, you’ll likely be ready to turn the automation on. Find the red colored “OFF” toggle and click it so the automation now appears as “ON” in green.
Using the “When a form is submitted” trigger to categorize form submissions
After configuring the automation steps 1-3 listed in the section above, you can move on to adding action steps. In the example below, we’ll accomplish two things by adding an “Update record” action:
Identify new project ideas created via form (externally)
Categorize those records by updating the record with the automation action
Step 1: Add “Update record” action and match it to the submitted record
To set this up, add the “Update record” action. Select the same table that you used in the trigger step and populate the “Record ID” field with the Airtable record ID option like shown below.
Step 2: Categorize the submission by utilizing a select field option
Next, choose a field to categorize the record as being created from a form. In our case, the “Submission Type” field will be updated with the option “External (via form)”.
After selecting the field to update along with the value to update it, run a test to ensure the action is working correctly. Now, whenever a new form submission appears in the selected table, the automation will update the record with the values set in the action.
FAQs
Can multiple forms be selected in the trigger step?
No, each trigger is scoped to use 1 table at a time.
Is the "When a form is submitted" trigger needed for every form?
No, forms created in the standalone form builder or the form view can be submitted regardless of whether or not there is an automation containing this trigger. Instead, this trigger allows users to automate custom workflows after forms are submitted. In other words, this trigger is additive, but not mandatory.
Can this trigger be used with interface form layouts?
The “When a form is submitted” trigger allows both base form views and standalone interface forms to be selected.
When an automation isn't firing when a form is submitted, the wrong form is likely selected in the trigger step. As a first troubleshooting step, we recommend verifying that the correct form is chosen in the automation’s configuration and ensuring that users are filling out the corresponding form accordingly.
Can i include a timestamp of when the form was submitted?
Yes you can by utilizing an “Actual run time” token in one of the action steps of the automation you are building. To learn more about the “Actual run time” token as outlined in step 2 of this section in the timestamping automations article