Pushbuild

How to stop an Airtable automation running more than once

An Airtable automation that sends two emails or creates two records for the same row usually has a trigger that fires on every edit. Changing the trigger and adding a status field makes each record run once.

Get a free written scope

We reply within 20 minutes with a written scope and a mockup of what we’d build.

At a glance

  1. Find what fired itOpen the automation and check its run history.
  2. Use a condition, not every update"When record updated" runs each time a watched field changes, so a record edited in several steps runs several times.
  3. Mark records as doneAdd a field such as Sent or Processed.

Find what fired it

  • Open the automation and check its run history. Each run shows the record and the trigger that started it.
  • If the runs are seconds apart on the same record, the trigger is firing on each edit to that record.

Use a condition, not every update

  • "When record updated" runs each time a watched field changes, so a record edited in several steps runs several times.
  • "When record matches conditions" runs when a record comes to meet the conditions. Use it with a condition such as Status is Ready.
  • If a record stops matching and later matches again, it runs again. That is expected.
  1. Find what fired it
  2. Use a condition, not every update
  3. Mark records as done
The parts of this guide, in order.

Mark records as done

  • Add a field such as Sent or Processed.
  • Add it to the trigger conditions as "is empty" or unchecked.
  • Make the last action of the automation set that field, so the record no longer matches.
  • Do not have the automation update a field its own trigger watches, or it can start itself again.

Updated 2026-11-12. General guidance, not advice for your situation; we scope each project in writing before any work starts.

Questions people ask first

Can a form submission trigger it twice?

A form creates one record. If you see two runs, check whether a second automation or an edit after submission also matches.

Where is the run history?

In the automation editor, on the run history tab for that automation.

Tell us what you need built.

Tell us the process and the tools involved, or call. We reply with questions or a written scope.

hello@pushbuild.com

(617) 299-8887