Variables

Messages, conditions and date triggers can refer to details of the contact, the event that started the automation and your workspace, with {{placeholders}}.

Available variables

Variable	Value
{{contact.name}}	The contact’s full name
{{contact.first_name}}	The first word of their name
{{contact.phone}}	Phone number, in international format
{{contact.email}}	Email address
{{contact.external_id}}	Your own ID for them
{{contact.<field>}}	Any custom field, for example {{contact.renewal_date}}
{{event.<field>}}	Anything in the event’s data, for example {{event.amount}}
{{workspace.name}}	Your workspace’s name

Nested fields use dots: {{event.order.number}} reads "order": {"number": "1042"}.

Example

The event:

{
  "name": "payment.due",
  "contact": { "external_id": "cus_1042", "phone": "+15551234567", "name": "Jane Doe" },
  "data": { "amount": "$120.00", "due_date": "1 October", "pay_url": "https://pay.example.com/inv-1042" }
}

The SMS text:

Hi {{contact.first_name}}, your payment of {{event.amount}} is due on {{event.due_date}}. Pay here: {{event.pay_url}}

What Jane receives:

Hi Jane, your payment of $120.00 is due on 1 October. Pay here: https://renotify.app/l/k3P9q

The link is shortened and tracked, so clicks count towards the message’s results.

WhatsApp templates

WhatsApp templates use numbered placeholders ({{1}}, {{2}}) that Meta approves. In a message step, give each one a value, which can be a variable: {{1}} → {{contact.first_name}}, {{2}} → {{event.amount}}.

Missing values

A placeholder with no value renders as nothing rather than showing braces to a customer. Use a test run to see how your messages render before going live.

Formatting values

Send values ready to show. Format amounts and dates in your system before sending the event: "amount": "$120.00" rather than 120, and "due_date": "1 October" for messages. Keep a YYYY-MM-DD copy in a custom field if a date trigger or wait needs it.