Documentation
Automation

Builder Variables

Store runtime data and reusable configuration for automation funnels.

Builder variables let blocks read customer context, reuse configuration, and store values during a funnel run.

Variable Types

TypePrefixBehavior
Systemsys.Provided automatically from the current client, chat, operator, and message. Read-only.
Funnelfunnel.Runtime data that blocks can read and update during the current funnel run.
Environmentenv.Reusable configuration for the funnel. Read-only in expressions.

Funnel Variables

Create a funnel variable when the workflow needs to remember a decision, score, identifier, or intermediate response.

Examples:

funnel.lead_score
funnel.payment_status
funnel.api_response

Funnel variables support text, number, and boolean values. A default value is optional. Use the Set variable block to update them.

Environment Variables

Environment variables are useful for values reused by several blocks, such as a region code, API URL, or campaign identifier.

env.REGION_CODE
env.API_URL

Treat environment variables as configuration rather than runtime state. They cannot be changed by builder blocks.

System Variables

System values are available without creating a variable. Common examples include:

sys.client.name
sys.client.customfield.language
sys.chat.id
sys.chat.channel
sys.message.text
sys.operator.id

Set Variable Sources

The Set variable block can use:

  • a manual value;
  • a system variable;
  • another funnel variable;
  • an expression.

Example expression:

sys.client.name ~ " - " ~ env.REGION_CODE

For complete syntax, functions, conditions, and naming rules, see Expression Language.

On this page