Smart values¶

Smart values are dynamic placeholders that get replaced with real data when a workflow runs. They let you personalize emails, set property values dynamically, build conditional logic, and pass data between actions.

Where to use smart values¶

Smart values work in any text field across workflow actions:

• Send Email — subject, body, recipients, reply-to
• Set Contact Property — value field (when set to smart value mode)
• If/Then — condition values (compare a property against a smart value)
• Webhook — included automatically in the JSON payload

The smart values panel appears on the right side of the action editor. Click any value to copy its token to your clipboard, then paste it into your action's fields.

Available smart values by trigger¶

Different triggers make different data available. The smart values panel automatically shows only the tokens relevant to your workflow's trigger.

Contact values¶

Available for triggers that have a contact in scope: Order Made, Product Purchased, Form Submitted, Contact Created, Contact Property Updated, Contact Date Property, Days Before/After Contact Date.

Event values¶

Available for triggers with an event in scope: Order Made, On Event Date, Days Before/After Event Date, Event Created.

Order values¶

Available for: Order Made, Product Purchased.

Form values¶

Available for: Form Submitted.

Ticket values¶

Available for: Order Made, Product Purchased.

Product values (per-unit)¶

Available for: Product Purchased (fires per ticket).

Trigger metadata¶

Available for all triggers.

Generators¶

Available for all triggers. These produce a fresh value on every workflow run.

Prior action outputs¶

When actions are chained, each action's output becomes a smart value for subsequent actions. This is how you pass data forward through the workflow.

Set Contact Property outputs¶

When Set Contact Property runs, it produces an output token:

{{action.set-custom-property.<property id>.value}}

Where <property id> is the property's internal ID — a 24-character hex string, not the human-readable name. You won't type this by hand: open the smart-value picker and search for the property, then click it to insert the full token with the real ID at your cursor.

Example: If you set a property called "Member ID" using a generator, the token a later action needs looks like:

{{action.set-custom-property.<Member ID property id>.value}}

and resolves at runtime to the generated code the set-property action produced.

Using outputs in emails¶

In a Send Email action that follows a Set Contact Property action — grab the token from the smart-value picker, not by typing:

Your membership code is: {{action.set-custom-property.<Member ID property id>.value}}

This code was generated on {{trigger.date}}.

The <Member ID property id> bit is a placeholder — swap it out by searching the smart-value picker for the property and clicking the match. {{trigger.date}} resolves literally and can stay as-typed.

At runtime, this resolves to:

Your membership code is: K7M3Q9X2

This code was generated on 2025-06-13T15:44:02.000Z.

Using outputs in conditionals¶

In an If/Then action, you can branch based on a prior action's output:

• Property: action.set-custom-property.Status.value
• Operator: is equal to
• Value: Active

This checks whether the Set Contact Property action wrote "Active" to the Status property, and routes the workflow accordingly.

Smart value types¶

Smart values are typed — the system knows whether a token represents text, a number, a date, an email, etc. This matters in two places:

1. If/Then conditions — the condition editor shows type-appropriate operators and inputs. A date property shows a date picker; a select property shows a dropdown with the actual options.

2. Set Contact Property — when setting a property to a smart value, only compatible tokens are shown (e.g. you can't set a date property to a text token).

Tips¶