Write it once, personalize every run

Drop a {{variable}} into a step title, step content, a run title, an email, an SMS, or a webhook. Manifestly fills in the right value for each run — so one workflow speaks to every customer, site, and day by name.

Start your free trial · No credit card required.

Kickoff email · Customer Onboarding Template
You write once
Welcome to {{company_name}}, {{Customer}}!
Your onboarding kicked off on {{current_date.full}} and is due {{run.due_date.full}}.
resolves per run
This run sends
Welcome to Acme Tools, Riverside Bakery!
Your onboarding kicked off on August 9, 2026 and is due August 16, 2026.

One workflow instead of a dozen near-identical copies

Teams end up cloning the same workflow just to swap a name, a date, or a phone number — and then every copy drifts. Variables keep a single template that fills itself in, so there's one thing to maintain and nothing to keep in sync by hand.

Without variables
  • A separate workflow per customer or location
  • Details hard-typed and copy-pasted into steps
  • Change a phone number, edit it everywhere
With variables
  • One template, personalized for every run
  • Values resolve automatically as the run goes
  • Update a global value once — every run follows

Add a variable in three steps

1

Type the variable

Anywhere you write content, wrap a name in double braces — {{support_email}}. A token picker in step, title, email, SMS, and webhook editors lets you insert one with a click.

2

Decide what fills it

A variable can be a global value you define, run and date context Manifestly already knows, or a piece of data captured earlier in the run through a workflow field.

3

Run it

Each run resolves its own values as it progresses. The same template greets a different customer, on a different date, in every run — no editing required.

Three kinds of variable, one syntax

Everything uses the same {{…}} braces. What changes is where the value comes from.

Global variables

Reusable name/value pairs you define once — a support number, a company name, a policy link. Reference them anywhere.

{{help_center_phone}} → 1-800-555-0142

Built-in context

Details Manifestly already tracks about the run, the step, the current date, the user, and your organization — ready to use.

{{run.due_date.full}} → Aug 16, 2026

Captured data

Reference a workflow field or step data by its label. Whatever a teammate enters in the run flows into your other content.

{{Customer}} → Riverside Bakery

Manage shared values in one place

Global variables are name/value pairs your account keeps centrally. Write {{company_name}} across dozens of workflows, and when the value changes you edit it once. Rename a variable and Manifestly updates every reference for you.

  • Names use lowercase letters, numbers, and underscores — e.g. {{support_email}}.
  • Variables defined in the master department are available in every department.
  • A usage count shows how many steps, content items, and automations reference each one.
Global VariablesMaster department
VariableValueUsage
company_nameAcme Tools31
support_emailhelp@acme.co18
help_center_phone1-800-555-014212
return_policy_urlacme.co/returns7
Edit a value here and every {{variable}} that uses it updates.

Turn what people enter into content downstream

Give a step or a workflow field a label, and that label becomes a variable. Whatever a teammate captures in the run — a customer, an order number, an amount — flows straight into later step titles, instructions, emails, and messages. Reference a field by its label with {{Order Total}}.

When a field pulls from a Data Table, its sibling columns are variables too: {{Customer.AccountManager}} resolves to the matching column for the chosen row.

Step 1 · captures a field
Customer Riverside Bakery
reused later in the run
Step 4 · title
Schedule install for {{Customer}}Riverside Bakery
Completion email · body
Thanks, {{Customer}} — you're all set! → Thanks, Riverside Bakery — you're all set!

Context that's ready to use

Common run, date, user, and organization details are built in — no setup needed.

{{run.title}}The run's title {{run.due_date.full}}When the run is due {{current_date.full}}Today's date {{step.name}}The current step {{current_user.name}}Who's acting {{organization.name}}Your organization {{department.name}}The department {{run.participants}}Everyone on the run

Run titles can also use {{day_of_week}}, {{month}}, and {{year}} — handy for recurring runs.

Variables work everywhere you write

Step titles
Step content
Run titles
Email automations
SMS automations
Webhook payloads

Personalize your automations, too

Variables aren't just for steps. Put them in the automated emails and text messages Manifestly sends on step events, and in the JSON you post to a webhook — so downstream systems and recipients get run-specific details, not a generic blast.

  • Emails resolve variables in the recipient, subject, and body.
  • SMS messages resolve variables in both the recipient and the message body.
  • Webhook bodies can carry run values like {{run.url}} and {{run.percent_completed}}.
# Webhook body you author once
{
  "run":      "{{run.title}}",
  "customer": "{{Customer}}",
  "progress": "{{run.percent_completed}}%",
  "link":     "{{run.url}}"
}

# What actually posts for this run
{
  "run":      "Onboarding: Riverside Bakery",
  "customer": "Riverside Bakery",
  "progress": "60%",
  "link":     "https://app.manifest.ly/runs/48213"
}

What teams personalize with variables

Customer onboarding

Capture the customer once and greet them by name in every step and email.

Welcome to {{company_name}}, {{Customer}} — here's what happens next.

Recurring operations

Daily and weekly runs that title and date themselves automatically.

Store open — {{day_of_week}}, {{current_date.full}}

Consistent contact info

Keep support numbers and policy links in global variables, referenced everywhere.

Questions? Call {{help_center_phone}} or see {{return_policy_url}}.

Content variables, answered

Wrap a name in double curly braces, like {{support_email}}. The step, title, email, SMS, and webhook editors also include a token picker so you can insert a built-in or captured variable with a click.

Per run. The workflow template stays untouched with the {{variable}} in place; each run resolves it to that run's own values as work progresses — the current date, the captured customer, the run's due date, and so on.

Global variable names use lowercase letters, numbers, and underscores — for example help_center_phone_number. Give it a value and it's ready to reference anywhere as {{help_center_phone_number}}.

No. Change a value in one place and every reference resolves to the new value. Rename a variable and Manifestly updates the references for you across the steps, content, and automations that use it.

Yes. Reference a workflow field or step by its label — {{Order Total}} — and the value captured in the run flows into later titles, content, and messages. For a field that draws from a Data Table, sibling columns are available too, like {{Customer.AccountManager}}.

Global variables defined in your master department are available in every department, so shared values like your company name or support number stay consistent. Individual departments can also define their own variables.

Other Features

Design your process

Workflow Customization

Shape exactly how each workflow behaves — logic, data, timing, and documentation.

Trusted by organizations big and small for their recurring workflows

Compass logo
Sheraton logo
Foxconn logo
Coldwell logo
Plural Sight logo
BDO logo
KW logo
UT Austin logo

Write It Once, Personalize Every Run

With Manifestly, your team will Never Miss a Thing.