Automations come with their own words. Some are the same in other tools, some are different. This page explains each Tape term in one or two sentences. If you're used to flows, items, and hooks, look for your word in the lists below.
Note: Tape uses the words on this page in the product. Words you may know from other tools are mentioned so you can find them, not because Tape uses them.
Words for your data
Record: One entry in a database app, such as one task, one lead, or one property. You may know it as an item, an entry, or a row.
Database app: A collection of records that share the same fields, such as
TasksorLeads. Automations live in database apps.Dashboard app: An app for showing information, such as charts and numbers. It has no records or fields of its own and can't hold automations.
Form app: An app for entering data through a form. It isn't a table of records and can't hold automations.
Workspace: A group of apps for one team or topic. You may know it as a space.
Organization: The account that holds all workspaces and people.
Field: One value of a record, such as
StatusorDue date.View: A saved way to look at the records of a database app. Actions such as
Get viewcan use shared views and your own private views. You may know it as a team view.Related records: Records that a record points to, or that point to it, through a relation field. You may know them as referenced items.
Words for how an automation starts
Automation: A set of steps that Tape runs on its own. You may know it as a flow.
Trigger: The event that starts an automation, for example
When a record is created. Read Automation triggers →.Filter: A check that decides whether the automation continues after it started. Read Automation filters →. You may know it as a field changed or field value match.
Manual run: Starting an automation yourself, for example on records you choose. It has real effects. Don't mix it up with a manual flow in other tools: the Tape equivalent of a manual flow is
When another automation calls.Simulated run: A test run that skips filters and doesn't change data. You may know it as a test run or simulate vars. Read Test automations →.
Words for what an automation does
Action: One step of an automation, for example
Update the current record. Actions are also the unit that Tape counts for your usage. You may know them as bricks or blocks. Read Automation actions →.Current record: The record that started the automation. Actions such as
Update the current recordwork on it.Collected records: A list of records that an action found, for example with
Search for records,Get view, orGet related. Later actions, such asUpdate collected, work on the whole list. You may know this as a collector. Read Work with collected records →.Variable: A value that you can insert into an action, such as the title of the current record. Type
@in a field that saysType '@' for variablesto pick one. You may know it as a token. Read Use record values and variables →.Flow control: Actions that decide the order of steps:
Conditional actions,Loop actions,Delay execution, andEnd run. You may know this as logic, an if block, or for each.Script and calculation:
Execute scriptandPerform calculationrun JavaScript and save the result in variables for later steps. You may know this as a calc or a custom variable.Web link: A link you create with an action. When someone opens it,
When a web link is clickedstarts an automation. You may know it as an external link. Read Web links in automations →.Webhook: A web address that Tape listens on. When another system sends data to it,
When a webhook is receivedstarts an automation.
Words in an action's menu
Silent: An option for actions that change records or add comments. A silent change sends no notifications.
Trigger automations and Trigger webhooks: Decide whether a change made by this action starts other automations or sends webhooks. You may know these as hooks or hook events. Both are off by default.
Author: An option for actions that change records or add comments. It sets who a change is attributed to. Without an author, the change is attributed to the automation itself. You may know it as authentication or run as.
Continue on error: Lets the automation carry on when this step fails. Read Handle errors in automations →.
Deactivate: Turns an action off without removing it.
Read Action settings in automations → for the full menu.
Words about results
Run: One execution of an automation. Each run has a status and a list of steps. You may know it as a log. Read Automation runs →.
Status of a run:
Scheduled,Running,Success,Throttled,Failed, orCancelled.Throttled: Tape slows runs down for a short time when the automations of an organization cause a lot of activity at once. Read Automation limits and throttling →.
Usage: How many actions you've used and how many are available. Read Automation usage →.
Where the words changed
A flow is an automation.
An item is a record.
A space is a workspace.
A hook or hook event is
Trigger automationsandTrigger webhooksin an action's menu.A token is a variable.
A collector is a set of collected records.
Flow logs are runs.
To find an automation you may have looked up by flow ID, use the search in the Automation Center →. You can search for an automation by its name or description, not by its ID.
FAQs
Is a flow the same as an automation?
Is a flow the same as an automation?
Yes! Tape calls it an automation.
Is an item the same as a record?
Is an item the same as a record?
Yes! A record is one entry in a database app.
What's the difference between a manual run and a simulated run?
What's the difference between a manual run and a simulated run?
A manual run changes your data. A simulated run doesn't, and it skips filters.
What is a hook event in Tape?
What is a hook event in Tape?
Tape doesn't use this term. The same idea is in the action menu items Trigger automations and Trigger webhooks.
Still have questions? Find answers and get help from community experts in the Tape community →
