Merge tags help you personalize parts of an automation using information that already exists in the workflow.
Instead of sending the same static content every time, merge tags let you pull in details like names, project information, or other values connected to the automation.
What merge tags do
Merge tags insert dynamic information into supported action fields.
That means your automation can automatically fill in relevant details instead of making you type the same information over and over.
For example, instead of writing:
Hi there
You can write something more specific using available workflow data, like:
Hi {Client Name}
This helps your automations feel more personal and more useful.
Why merge tags matter
Merge tags make automations smarter.
They help you:
personalize emails
create more useful task titles or descriptions
pass cleaner information into the next step
reduce manual editing
make automated messages feel less generic
Where merge tags can be used
Merge tags can be used in supported action fields where dynamic content makes sense.
This is most helpful in places like:
email subject lines
email body content
task titles
task descriptions
document-related messaging
other supported action text fields
What kind of information merge tags can pull in
Merge tags can pull in details connected to the workflow.
Depending on the automation, that may include information related to:
the trigger
the client or contact
the project
the document
the business
looped items inside a workflow
That means the information available can change depending on how the automation starts and what steps are involved.
Good examples of merge tags in action
Example 1
Use a merge tag in a follow-up email so the message includes the client’s name.
This makes the email feel more direct and personal.
Example 2
Use a merge tag in a task title so your team can instantly see which client or project the task is connected to.
This makes internal workflows easier to read and act on.
Example 3
Use merge tags in a workflow that depends on project details so the next step carries the right context forward automatically.
When to use merge tags
Use merge tags when the same action should feel customized for each automation run.
They are especially useful when:
the workflow is client-facing
your team needs clearer internal context
the same action repeats often
you want to reduce manual edits inside automations
A simple way to think about it
Merge tags are what make automations feel dynamic instead of generic.
They let one workflow adapt its content based on the information already connected to that run.
Things to keep in mind
Merge tags are most useful when they’re used intentionally.
A few well-placed dynamic details usually go further than stuffing every field with as much variable content as possible.
The goal is clarity and relevance, not complexity.