An automation is a set of steps that Tape runs on its own whenever something happens. It saves you from copying values, sending reminders, and creating follow-up records by hand. If you're used to flows, items, and hooks, you'll find the same ideas here under different names. See Automation terms →.
You can use automations for many things, including:
Creating onboarding tasks when a candidate moves to the
Hiredstage.Emailing the seller when a lead's status changes to
Offer sent.
Note:
Automations belong to a database app. You build them in the database whose records start them.
Runs have real effects. A manual run changes records, sends emails, and counts toward your usage.
Runs have limits. See Automation limits and throttling →.
Who can use automations?
Automations are available on the Free, Plus, and Premium plans. The number of automation actions per month depends on your plan. See the limits for your plan on our pricing page.
Workspace admins can create, edit, and delete automations.
How an automation works
Every automation has three parts that you build from top to bottom:
The trigger decides when the automation starts, for example
When a record is updated.The filter decides whether it continues. If the conditions aren't met, the automation stops before any action runs.
The actions do the work, one after the other, for example
Update the current recordorSend an email.
Each time an automation gets past its filter, Tape records a run. If the filter stops it, there's no run. You can open a run later to see what happened in every step. Learn more in Automation runs →.
Find your way around
Where you work depends on the task:
Build and change one automation in the Automation editor →.
See all automations, runs, and your usage in the Automation Center →.
See the automations of one database: open the database app and click the automations icon in the top bar (tooltip
Create and view automations). The icon is only there for workspace admins, and not on mobile.
Automation triggers
A trigger starts the automation. Tape has nine:
When a record is createdruns once for every new record. Trigger when a record is created →When a record is updatedruns when a record changes. When a record is updated →When a record is deletedruns when a record is deleted. Trigger when a record is deleted →When a comment is addedruns when someone comments on a record or replies to a comment. Trigger when a comment is added →When a date field arrivesruns when the date in a field is reached. Trigger when a date field arrives →On a scheduled time or intervalruns once or on a repeating schedule. Trigger on a schedule →When another automation callsruns when another automation calls it. Trigger from another automation →When a web link is clickedruns when someone opens a web link you created. Trigger from a web link →When a webhook is receivedruns when another system sends data to Tape. Trigger from a webhook →
Not sure which one to use? Read Automation triggers →.
Automation filters
Filters check values before the actions run, for example that the status has changed to Done. Read Automation filters → to see every condition you can build.
Automation actions
Actions are the steps that change data, send messages, or control the flow. Select Add action to choose from the list. Some actions work on one record, such as Update record or Create PDF. Others collect records first, such as Search for records, then work on all of them, such as Update collected. Conditional actions and Loop actions decide which steps run. Read Automation actions → for the full list, and Action settings in automations → for the options each step has in its ••• menu.
Test, run, and monitor
Test automations → with
Manual runorSimulated run.Run an automation on existing records → when records were there before the automation.
Automation runs → shows what each run did.
Active, paused, and broken automations → explains the status of an automation.
Organize your automations → helps you keep many automations tidy.
FAQs
What's the difference between an automation and a flow?
What's the difference between an automation and a flow?
Nothing, they mean the same. Tape uses the word automation. A flow in other tools is an automation here.
Can one automation have more than one trigger?
Can one automation have more than one trigger?
No, each automation has exactly one trigger. You can change the trigger later with Turn into in the trigger's ••• menu. The database app and your actions stay. The settings of the old trigger are reset.
Do automations run on records that existed before I created them?
Do automations run on records that existed before I created them?
No, not by themselves. Triggers react to events that happen after the automation is saved, such as an update to a record that was already there. To run an automation on records that already exist, read Run an automation on existing records →.
Can I stop an automation without deleting it?
Can I stop an automation without deleting it?
Yes! Set it to Paused. Read Active, paused, and broken automations →.
Still have questions? Find answers and get help from community experts in the Tape community →
