Skip to main content
All CollectionsAdvanced Form for AirtableForm FAQs
How to trigger an Airtable Automation when a Form is submitted
How to trigger an Airtable Automation when a Form is submitted

In Airtable I can use the "When a Form is submitted" trigger, but that doesn't work with miniExtensions.

Updated over 2 weeks ago

Airtable automations have several different ways of being triggered, some of which can be used effectively with the miniExtensions form to ensure that an automation is triggered after a form is submitted. Below we list which triggers work in which scenario, while using the miniExtensions form, and which don't work well:

Triggers used when creating new records

  • When record created: As the name would suggest, this trigger only works when creating new records, not when updating existing records.

  • When a record enters a view: This is the most versatile trigger, since it is very easy to define exactly which records will trigger the automation. Any time a record enters a view, the automation will run. This applies to both new and updated records. If you want to capture all new records the view used should be an unfiltered view (e.g. All records).

  • When a record matches a condition: This is similar to the above, but you need to define the conditions within the trigger, which creates extra work to set up and maintain. We recommend you use When a record enters a view instead.

Triggers used when editing records

  • When record enters a view: Please see the explanation in the previous section.

  • When record matches a condition: Please see the explanation in the previous section.

  • When record updated: This trigger does work when updating field values using the miniExtensions form. However, we have seen some issues with this in the past so we recommend using the other two triggers instead.

Triggers that do not work (well) with miniExtensions

  • When a form is submitted: This trigger only works with Airtable's own forms, not with the miniExtensions form.

  • When a button is clicked: This trigger only works with Airtable's own interfaces, not with the miniExtensions form.

  • When webhook is received: This does theoretically work with the miniExtensions form (using this feature). However, this trigger does not currently provide the record ID for the record that triggered the automation when used with the miniExtensions form, which limits its usefulness.

Did this answer your question?