Variables Module

Change it once. Update everywhere.

One email address lives in 14 email templates, 7 macros, and 3 API headers. Rename the company. Rotate the API key. Update the support URL. One token change. Everywhere updates.

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.stripe_pk}}	••••••••••••••••
	{{var.email_signature}}	<div>Thanks,<br>The Acme Team</div>

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.

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

Rotate your Stripe key. Find every header 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

Rotate keys in one place. Every macro and API updates instantly

Store HTML fragments: signatures, disclaimers, legal footers

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.

Values masked by defaultAPI keys and secrets stay hidden until you click reveal.

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. HTML fragments render inline.

PDF templatesSame replacement, same tokens, same everything.

API callsURL, headers, body. Auth tokens live in Variables so rotations take one edit.

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?

Every macro step parameter, every email and PDF template body, every API URL/header/body, every scheduled, startup, or shortcut parameter. Resolution happens at execution time. The token is replaced with the stored value right before the consumer runs.

Can I store HTML or multi-line content?

Yes. Values inject raw into HTML, so you can store email signatures, legal footers, disclaimers, even an entire reusable section. This means you're also responsible for the content you put in: if you store <script>, it renders as a script tag. Only team members with admin access can edit variables.

Are API keys in Variables safe?

Values are stored in your WordPress database, not in plaintext files or commits. The list UI masks values by default. Click reveal to see them. Access is gated by the manage_options capability, so only admins can view or edit. Treat the database itself with the care you'd give any secret store.

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

Delete is guarded. Before confirming, the plugin scans every module (macros, templates, APIs, scheduled, startup, shortcuts) and shows you exactly how many consumers reference it. You can cancel and refactor first, or delete anyway if you know what you're doing.

Ready?

Stop typing the same value twice.

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