Variables Module

Change it once. Update everywhere.

Store visible, non-secret values such as an admin email, public support URL, company label, or counter once. Reference their tokens in supported fields instead of copying the same value into each configuration.

Start centralizing View all modules

One token, every module Safe delete with usage check Import / export ready

Variables

Need help?

Create Variable

Import

Export

	Variable	Value	Actions
	{{var.admin_email}}	ops@acmecorp.com
	{{var.support_url}}	https://acmecorp.com/help
	{{var.company_name}}	Acme Corporation
	{{var.refund_days}}	30
	{{var.store_label}}	Example Store
	{{var.email_signature}}	Thanks, The Acme Team

Interface examples use sample data. Results, counts, and timing vary by site and configuration.

See it in action

Define a value once, reuse it everywhere.

A short walk-through of the Variables module: create a reusable {{var.name}} token, drop it into commands, macros, and email or PDF templates, then change the value in one place and watch every use update.

Recordings show the interface at the time of capture and can differ from the current build. Follow this page and the current command reference for supported behavior.

The Problem

You typed the same email fourteen times.

Your support email lives in every welcome email template, every abandoned cart flow, every receipt PDF. The day you change providers is the day you find all fourteen places. If you're lucky. If you're not, a customer emails the wrong inbox for six months.

Without Variables

Paste the same email address into 14 templates and 7 macros

Change a public support URL. Find every message that references it

Rename your company. Grep through the database for old name

Inevitably miss one. Customer emails a dead inbox for 6 months

Legal footer text changes. Republish every email by hand

Copy-paste proliferation Hours per rename Guaranteed to miss one

With Variables

Define {{var.admin_email}} once. Paste the token anywhere

Change a non-secret value once; supported consumers resolve it at execution

Store non-secret labels, email addresses, public URLs, and counters

Safe delete: warns you before removing a variable in use

One value, everywhere in sync Edit the variable. Every email, PDF, API, macro updates next run.

DRY by default Seconds to update Safe refactors

The token system

Type a name. Get a token.

Names go in bare. The plugin wraps them. You drop the token into any field that supports variables, and at run time it resolves to the stored value.

Auto-wrappingYou type admin_email. Stored as {{var.admin_email}}. No typos possible.

Name normalizationDashes, dots, spaces collapse to underscores. Case forced to lowercase.

Visible, non-secret valuesValues are visible non-secret data. Credential-like legacy rows require review.

One-click copyGrab the wrapped token from any row. Paste it into a macro step or template.

One token, every module

Define once. Used everywhere.

Variables resolve across seven execution paths. Edit the value, and the next run of every consumer picks it up. No redeploys, no editing 14 templates.

Email templatesBody HTML resolves tokens at send time. Use sanitized non-secret text values.

PDF templatesSame replacement, same tokens, same everything.

API callsURL, headers, body. Reuse public endpoints and non-secret values. Store credentials in the integration configuration.

Macro parametersAny step, any field, any category. One dispatch point covers it all.

Safe delete

Know before you break it.

Delete a variable in use, and six macros silently fail tomorrow. So we check first. Before removal, you see exactly where the token is referenced and how many consumers break if you proceed.

Reference scanChecks macros, email templates, PDF templates, APIs, scheduled, startup, shortcuts.

Usage breakdownShows counts by module. "3 macros, 2 templates, 1 API" before you click delete.

No zombie tokensYou decide: delete anyway or cancel and refactor first.

Export before risky changesJSON export gives you a rollback snapshot in one click.

The Math

Fewer copies. Fewer mistakes.

One rename that used to take 45 minutes and a grep-through-templates session now takes 10 seconds.

To update 20 consumers

Change the variable. Next run of every macro and template picks it up.

Resolve the same tokens

Macros, email, PDF, APIs, scheduled, startup, shortcuts.

Broken references after delete

Pre-delete check lists every consumer. You decide before it breaks.

$59/yr

One prevented rename-miss pays for the license. And Variables is just one of ten modules. See pricing

FAQ

Questions? Answered.

Where can I use {{var.x}} tokens?

Supported macro parameters, email and PDF template fields, API URL/header/body fields, and supported scheduled, startup, or shortcut parameters resolve tokens at execution time. Review the consuming command and field; not every input accepts variable substitution.

Can I store HTML or multi-line content?

Variables store sanitized plain-text, non-secret values. HTML and scripts are not a reusable-template mechanism here. Use the Templates module for document content and review Custom Commands for executable logic.

Are API keys in Variables safe?

No. Variables are not a secret store. Values are visible reusable data; credential-like values and legacy masked rows are withheld for review instead of resolved or exported. Do not put passwords or API tokens here.

What happens if I delete a variable that's still in use?

The module checks recognized usages before deletion. Review the consumers it reports and replace references before removing a value; usage detection is not a guarantee that every authored string has been found.

Ready?

Stop typing the same value twice.

Define once. Reference everywhere. Update anywhere with a single edit.