Personalize steps with data mapping tokens

Data mapping lets you drop live values — a lead's first name, their phone number, your brokerage name, or a call transcript — into any text field in a workflow step. Instead of hard-coding "Hi there," you write Hi {{contact.firstName}} and SAMI OS fills in the real name when the step runs.

What data mapping tokens are

A token is a placeholder wrapped in double curly braces, like {{contact.firstName}} or {{org.name}}. When a workflow runs, each token is swapped for that contact's actual data.

You'll use tokens anywhere you can type in a step — the body of an SMS or email, an integration field, a webhook URL, a note. Common tokens include:

• {{contact.firstName}} and {{contact.lastName}} — the lead's name
• {{contact.phone}} and {{contact.email}} — their contact details
• {{org.name}} — your organization or brokerage name
• {{trigger.transcript}} — fields carried in by whatever started the workflow, such as a SAMI Bots call transcript

Tokens fall into a few sources: contact and org fields are always available, trigger fields come from the event that started the workflow, and steps fields come from earlier steps in the same flow.

Insert a token with the picker

Every mappable field in the builder has a small plus button beside it labeled "Use workflow data." That opens the data picker, where you browse and insert tokens instead of typing the path by hand.

1. Open a step that has text fields

   In the Workflows builder, select a step like Send SMS or Send Email so its settings open in the side panel.

2. Click Use workflow data

   Next to the field you want to personalize, click the plus button. A "Use workflow data from" panel opens with a search box.

3. Pick a field

   Steps are grouped and color-coded — the trigger, then each upstream step. Expand a group, or search by name, and click a field to insert its token at your cursor. Fields that appeared in your latest test show "Seen in latest test" with a sample value.

4. Preview and adjust

   The inserted token shows as a pill reading the field label and a sample, like "First Name: John." Add surrounding text around it, and use Advanced edit to tweak the raw {{...}} text directly.

Where available fields come from

The picker only offers data the step can actually reach at that point in the flow. Two sources feed it:

• Trigger sample data — the fields the workflow's trigger provides. Internal triggers like a tag being added expose a known set; external triggers (a webhook or an integration lead) only list fields after a real payload arrives, so you may need to test first.
• Upstream step outputs — anything a step before this one produces. A Lookup Contact step, for example, exposes its result as {{steps.<node>.email}} for every later step to use.

Because the list is built per step, a field added by step three won't appear for step two. Set up your SAMI Bots and lookup steps in the order you need their data.

How publish validation checks tokens

When you publish, SAMI OS checks every trigger. and steps. token against the data that's truly available at that step. If a token points at a field the selected trigger schema or your latest test output doesn't include, publishing flags it so you can fix or remove it before it goes live. Unavailable tokens are also marked in the builder with a warning pill, so you can spot a broken merge field before a contact ever sees a blank message.

Tokens for your own Contacts and organization data aren't gated this way — they always resolve — so the check focuses on trigger and step data that might not exist yet.

Related articles

• Sending SMS and email from a workflow
• Choosing a trigger to start your workflow
• Publishing and activating a workflow