Automation basics

Using data in fields

Fill a field with data from earlier in the run: variables, the table, loop items and built-in functions.

Many text fields accept references: a name in double braces, replaced by its value just before the block runs. Where a field accepts them, typing {{ offers a list to pick from.

A reference starts with where the data lives, then a path into it, separated by dots. {{variables.email}} and {{variables@email}} mean the same thing. A list position is a number counting from 0.

The places you can read from: variables, the workflow's variables, including the Start block's parameters. table, the workflow's table. loopData, the current item of a loop, by its Loop ID. prevBlockData, what the block before this one handed on. globalData, the JSON set under Global data in the editor's toolbar. googleSheets, rows a Google Sheets block read under a reference key. workflow, what a workflow run by Execute workflow left behind, under its Execute Id (optional). secrets, the credentials in Databases. Resource, the accounts imported for the profile with Import resource on the Profiles page. activeTabUrl, the address of the page the run is on.

With table, a column name alone reads the first row. Use $last for the last row, or a number for a given row.

If a reference finds nothing, it stays in the field as written. When you see {{variables.email}} typed into a page, the variable was never set. A value that is not text, such as a list, is written as JSON.

Functions start with $. Inside a function, a reference goes in square brackets instead of braces: {{$increment([variables.page], 1)}}. Put text in quotes and separate the values with commas.

To compute a value, start the field with !!. Everything inside the braces is then evaluated as a JavaScript expression, for example !!{{variables.total > 100 ? 'large' : 'small'}}.

A WarpX Phone run has no profile and no page, so Resource and activeTabUrl have nothing to give there. Keep an account's secrets in secrets or the table instead.