Merge field
Email & SMS deliveryAlso called: personalization token, merge tag, variable
A merge field is a placeholder in message content that is replaced with that contact's data at send time — {{name}} becoming Priya — so one written message can address thousands of people individually.
Merge fields are the oldest trick in email and still the easiest to get wrong, because they fail silently. A missing value does not raise an error; it renders as nothing, and the message goes out reading Hi , which is worse than not personalising at all.
The genuinely valuable merges are rarely names. Referencing the thing someone actually did — the quote amount, the appointment time, the plan they are on — carries information, and information is what earns a reply.
Data arriving from another system deserves particular care, because it is not yours and can change shape. A payload field that was a string last month can arrive as a number this month, and a message built on it will not notice.
How it works in FrazzleCRM
- ✓Subjects, bodies, preheaders and from-names accept merge fields for name, email, phone, contact id and any custom field.
- ✓Values from an inbound webhook are available to the run, so a message can quote an order number or an appointment time that never had to be stored on the contact first.
- ✓Appointment details merge into reminder content, which is what lets one reminder flow serve every appointment type.
- ✓Trigger link destinations accept merges too, so each contact can be sent to their own URL — a per-contact magic link held in a field, for instance.
Where teams get this wrong
Personalising a subject line with a field that is empty for a third of the list is a measurable loss, not a neutral one — those subject lines arrive visibly broken. Branch on whether the field exists, or write a version that does not need it.
Common questions
What happens if the merge field has no value?
It renders as empty. Nothing errors, nothing is skipped, and the gap ships — which is why fallbacks and existence checks matter.
Can I merge data from a webhook without saving it to the contact?
Yes. Values from the incoming payload are available to that run, so one-off details can be quoted without permanently storing them.
See it on a real map
Free templates where this shows up as an actual node. Clone one and the diagram runs as the automation.
Appointment No-Show Killer
Confirmation, two SMS reminders, and an automatic reschedule email for no-shows.
E-commercePost-Purchase + Review Request
Confirm, ship, then ask — and only send the happy customers to the public review page.
EventsWorkshop & Event Tickets
Sell the seat, get them in the room, then sell the thing that comes after.
Related terms
Custom field
A custom field stores a value on a contact that the standard fields do not cover — a renewal date, a plan name, a quoted price, an external system's id — for use in personalisation, branching and date-driven automation.
Inbound webhook
An inbound webhook is a URL your CRM exposes so that other systems can push events into it — a payment succeeded, a booking made, a form submitted — enrolling a contact and carrying the event's data into the automation.
Trigger link
A trigger link is a tracked URL that records who clicked it and can start or advance an automation before forwarding the visitor to the real destination — turning a click into an event without needing a form.
Or browse all 24 terms — grouped by what part of the funnel they belong to.
Draw it once, and it runs
In FrazzleCRM the funnel map IS the automation — every node you draw is a real step, and every step you edit redraws the map. Free plan, no credit card.
Start free