What variables are and their syntax ({{$...}})

Variables replace placeholders like {{$contact.first_name}} with real values when the workflow runs. Learn the syntax and how to insert them.

Jun 26, 2026

Watch this step in the video · Variables

What it is and when to use it

A variable is a placeholder that the workflow replaces with a real value the moment it runs. Instead of writing a fixed name, you write {{$contact.first_name}} and, when the workflow runs, Omnifox swaps it for the contact's name. That way a single message works for everyone.

They're used to personalize messages and emails, build the body of an HTTP request to another system, or make decisions inside a condition.

The syntax: {{$...}}

The recommended form wraps the name in double curly braces with a $ sign:

{{$contact.first_name}}

Omnifox also accepts two equivalent forms:

  • Without the $ sign: {{contact.first_name}}
  • Inline, without braces: $contact.first_name (followed by a space or punctuation)

Important: if a variable is empty (for example a contact with no last name) or doesn't exist, it's replaced with empty text. You'll never see the raw {{...}} in the message that gets sent.

Where you can use them

You can type variables into almost any text field of the action nodes:

  • The body of a message (Send message).
  • The subject and body of an email (Send email).
  • The body and headers of an HTTP request.
  • A task title, an internal note, and so on.

Steps to insert a variable

  1. Open the workflow from Automations and select an action node.
  2. Open the editor's Variables panel.
  3. Find the variable you want (for example contact.first_name).
  4. Click Copy: it copies the token {{$contact.first_name}}.
  5. Paste it into the text field, wherever you want the value to appear.

Create your own variables

Besides the built-in ones, you can define your own with the Set variable node. Each assignment has:

  • name — without the $, for example attempts.
  • value — a fixed text or one that itself uses other variables.
  • operation — set, append (concatenate), or increment (add, ideal for retry counters).

Then you reference it further down the flow as {{$attempts}}.

Verification

Use the editor's Test run button with a real contact and open the timeline: you'll see the message with values already substituted. If you see the token unreplaced, the name doesn't match.

If it doesn't work

  • Empty text shows where you expected a value: that contact field is empty, or you misspelled the variable name.
  • A literal {{$something}} appears in the message: check the braces (they must be double) and the exact name; copy the variable from the Variables panel to avoid typos.
  • A custom variable comes out empty: make sure the Set variable node runs before the node that uses it.

Tips

  • Always copy variables from the Variables panel; that prevents name errors.
  • To count retries use increment: it starts empty and adds 1 on each pass.

Related articles

Was this helpful?

Related articles

Message us on WhatsApp