Skip to main content

Run an automation on existing records

Triggers only react to new events. To apply an automation to records that already exist, run it manually on chosen records or on all records of a database app.

Written by Leo

Say you build an automation that fills a new field when a task is created. It only reacts to tasks created from now on. A manual run applies it to records that are already there. You can use this for many things, including:

  • Filling a new field on every record in a database app.

  • Sending an email for records that already meet a condition.

The editor of an automation for Expenses with the filter Where Status Is Submitted, and Manual run at the top highlighted next to the run button and the ••• menu

Note:

  • A manual run has real effects. Test with Simulated run first. Read Test automations →.

  • Filters still apply. Only records that match the filter lead to a run.

  • Large runs count toward your usage. Every action in every run uses actions.

Before you start

  1. Build the automation and check it with Simulated run. You find it in the ••• menu at the top of the editor.

  2. Make sure the trigger fits the records you want. Filters like Has changed and Has changed to don't match in a manual run, because nothing changes. Use a filter on the current value, such as Is. Learn more in Filter automations by field changes →.

  3. Try one record first.

Run on records you choose

  1. Open the automation in the editor.

  2. Select Manual run, or press cmd/ctrl + J.

  3. Next to Run on, choose Selected records, then pick records from the list. Each record shows where it's from, for example Expense in Accounting.

  4. Select Start run. If you have unsaved changes, the button reads Save and start run and also saves them.

Selecting Manual run opens Run on selected records with a record search, Start run, and the list of expenses; choosing Client dinner marks it, and the pointer rests on Start run

Run on all records of a database app

  1. Open the automation in the editor and select Manual run.

  2. Next to Run on, choose one of these:

    • Selected view runs on the records in a view of the database.

    • Number of records runs on the most recent records. Enter how many.

    • All records runs on every record of the database.

  3. Select Start run. There's no extra confirmation, so check your choice first.

The Run on menu with Selected records, Selected view, Number of records, and All records

Check the result

Click ▷ next to Manual run (tooltip View all runs), or press cmd/ctrl + 1. Each record that matched the filter has its own run. Select a run to see its steps. Select Follow in the Runs panel to get a notification for every failed run. To stop runs that haven't finished, click ••• at the top right of the editor and select Cancel runs, then confirm. Learn more in Automation runs →.

Clicking the runs button next to Manual run to open the Runs panel, opening a failed run, and expanding the failed step Create a record to read its error

If many runs are slow

When a lot of runs start at once, Tape may slow down automations across your organization for a while. Runs can show the status Throttled. Tape checks the load again shortly and runs waiting automations automatically. To spread the work out, read Update many records in batches →.

Other ways to reach existing records

  • Use a schedule with Get view and Update collected to change many records in one run. Collection actions return at most 1,000 records.

  • Use When another automation calls and call the automation from another one.

Learn more

FAQs

Are you a developer using the Tape API for automations?

The automation API has its own documentation for developers. Full reference: Run and simulate in the developer docs →

Still have more questions? Find answers and get help from community experts in the Tape community →.

Did this answer your question?