Skip to main content

Use record values and variables

Insert live data into emails, comments, and PDFs. Type @ to add field values, the record link, or earlier results, and Tape fills them in on every run.

Written by Leo

Record values and variables are placeholders you add to an action (they stand in for real data that Tape fills in each time the automation runs). They're meant to help you write one message, comment, or file name that adapts to every record.

An email action in an automation for Expenses. To holds @Expense / Approver / Email and Subject reads Approval needed: @Expense / Expense. In the message, someone types Hi and @Appr, the list of values opens, and selecting Approver / Name adds the tag @Expense / Approver / Name.

You can use record values and variables for many things, including:

  • Greeting a seller by name in an email when their lead status changes.

  • Putting a contract number in the file name of a PDF.

Note:

  • Values are filled in during each run. The same automation produces different text for every record.

  • A variable only exists for actions below the one that creates it. An action can't use a result that comes later in the automation.

Add a value to an action

To add a value to an action:

  1. Open the automation and select the action you want to change.

  2. Select a text box that shows Type '@' for variables. Other boxes, such as Subject and Value, accept values too.

  3. Type @.

  4. Choose a value from the list.

  5. Select Save changes.

In the editor, a value appears as a tag, for example @Expense / Title. When the automation runs, Tape replaces the tag with the data from the record. You can mix tags with normal text, for example "Approval needed: " followed by @Expense / Title.

What you can insert

The list opens with the values of the record that started the automation, followed by results of earlier actions.

  • Field values: Every field of the record, for example @Expense / Amount. Tape inserts the value as text.

  • Record URL: A link to the record, for example @Expense / Record URL.

  • Person field properties: A person field offers more than one value:

  • Email is the person's email address. Use it in To, or in any box that expects an address.

  • Name is the person's name. Use it in a message, for example "Hi Juliet,".

  • Mention mentions the person. Use it in a comment, for example @Expense / Approver / Mention.

  • Record details: Record ID, All Comments, Created by, Last edited by, and more.

  • Values from before a change: Add Get previous values to read what a field contained before the record was updated.

  • Results of earlier actions: Actions that save a result add a variable you can use further down:

  • Search for records saves a list of records. Learn more in Work with collected records →.

  • Create PDF saves the file in a variable called PDF.

  • Perform calculation saves its result in Calculation result.

  • Execute script saves its output in variables such as Script output 1.

  • Send HTTP request saves the answer in HTTP response.

  • Data from the trigger: When a webhook is received lists the data it received under Variables. Learn more about webhooks →

  • Current date and time: Current date and Current date & time, in the automation's time zone. In scripts, you also get the current time, and each value in local time and in UTC.

Tip: Be careful with dates. A date can have a different value in your time zone and in UTC. Learn more about dates and time zones →

Check your values before a run

To see how a message will look, select Show preview in an action that has one, such as Send email or Create PDF. Select Simulate variables to start a simulated run on a record you choose and fill the tags with its values, then select Exit preview to go back to editing.

Send a test run to a record that has your own address in it, so no customer gets a draft email. Learn more about testing →

Let's look at an example

Let's say your finance team wants managers to get a short email when an expense needs approval. Here's how:

  1. Set the trigger to When a record is updated.

  2. Select Add action → Send email.

  3. In To, type @ and choose the Email value of the Approver field.

  4. In Subject, enter "Approval needed: " and add @Expense / Title.

  5. In the message, enter "Hi ", add the Name value of Approver, then add @Expense / Title, @Expense / Amount, and @Expense / Record URL.

  6. Select Show preview, then Simulate variables to check the result.

  7. Select Save changes.

The next time an expense is updated, the approver gets an email that starts with "Hi Juliet" and shows the expense title, the amount, and a link to the record.

Record value errors

  • If a tag shows the wrong text, check which record the value comes from. Values from Search for records belong to a list of records, not to the current record.

  • If a value is empty, the field on that record has no content. Tape inserts nothing at that spot.

  • If a value stops working after you delete or change a field, remove the old tag and add the value again.

Learn more

FAQs

Can I use values from another record in my message?

Yes! Use Get related to collect records connected to the current record, then use the values of the collected records. Learn more about collected records →

Can I add the link to a record in an email?

Yes. Type @ and choose Record URL. The tag becomes a link to the record when the email is sent.

How do I mention a person in a comment?

Type @, choose the person field, then choose Mention. The comment then mentions that person.

Can I use a number or date in a calculation?

Yes. Add Perform calculation and type @ in the code box to insert values. The result is saved in a variable that later actions can use. Learn more about Perform calculation →

Why can't I see a variable from an earlier action?

The action that creates it is probably below the action you're editing. Move it up, or add it above. Variables from inside a loop or condition are available to every action below it, also outside the loop or condition.

Are you a developer using the Tape API for automations?

The automation API has its own documentation for developers. Full reference: Dynamic values in the developer docs →

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

Did this answer your question?