Skip to content

Personalizing emails with tokens

Fill in names, order details, and company information from the recipient's contact, their primary company, and the record the workflow runs on.

Tokens are placeholders in a template’s subject or body that Transactional Email replaces with real values at send time. Three kinds are supported:

  • {{ contact.<property> }} — a property of the recipient’s contact: the HubSpot contact whose primary Email is the address the email goes to. If several contacts share the address, the most recently updated one is used. When the address has no contact — an order’s billing email, say — contact and company tokens are empty, or use their default value.
  • {{ company.<property> }} — a property of that contact’s primary company.
  • {{ deal.<property> }}, {{ ticket.<property> }}, {{ quote.<property> }}, {{ invoice.<property> }}, {{ order.<property> }}, {{ subscription.<property> }}, and custom object tokens — a property of the record the workflow is enrolled on. See Tokens from the enrolled record.

Tokens inserted with HubSpot’s Personalize button in the email editor work too: they look like {{ personalization_token('contact.firstname', 'there') }}, and the second value is the default.

Use each property’s internal name, such as firstname, lastname, or a custom property like order_number. You’ll find it on the property’s details in HubSpot’s property settings.

You type The recipient sees
Hi {{ contact.firstname }}, Hi Dana,
Hi {{ contact.firstname | default('there') }}, Hi there, (when the contact has no first name)
Order {{ contact.order_number }} is confirmed Order 10482 is confirmed
Thanks for choosing {{ company.name }} Thanks for choosing Acme Inc.
Your {{ contact.plan_tier }} plan renews on {{ contact.renewal_date }} Your Gold plan renews on November 1, 2026
{{ personalization_token('deal.dealname', 'Your order') }} is {{ deal.dealstage }} Website redesign is Closed won (in a deal workflow)

In a deal, ticket, quote, invoice, order, subscription, or custom object workflow, the email can use the properties of the record the workflow runs on — the enrolled record — alongside the recipient’s contact and company tokens. This works when the action’s target is the record’s associated contacts, too: each contact gets their own email, all filled in from the same deal.

In a deal workflow sending to associated contacts Fills in from
{{ contact.firstname }} Each recipient’s own contact
{{ company.name }} That contact’s primary company — not the deal’s company
{{ deal.amount }} The enrolled deal
  • Use the token for the workflow’s object. deal.* tokens fill in only in deal workflows, ticket.* tokens only in ticket workflows, and so on. In any other workflow they’re empty, or use their default, and the send log lists them as unknown tokens.
  • Only the enrolled record’s own properties. Tokens don’t follow associations from the enrolled record. To show something from a record associated with the deal — the deal’s company, say — copy it onto the deal first (for example with a property sync or a Copy property value workflow action), then use the deal property.
  • Custom objects work the same way. Their tokens start with the object’s full name, which includes your account ID, for example {{ personalization_token('p243933280_app_licenses.license_id', 'your license') }} in an App Licenses workflow. Custom objects need HubSpot Enterprise.
  • HubSpot’s Personalize button offers these tokens only in an Automated email. In a Regular email it offers contact and company only; you can still type the tokens, for example {{ personalization_token('deal.dealname', 'your order') }}. See Creating a transactional email template.
  • If the enrolled record is deleted before the email sends, its tokens are empty, or use their default.
  • The app needs permission to read the record. HubSpot asks for read access to these objects as optional permissions when you install. Without them the tokens are empty, or use their default. See Granting the optional permissions.
  • Empty properties become empty text. If the property has no value, the token disappears — unless you give it a default with | default('…'), as in {{ contact.firstname | default('there') }}.
  • No primary company? Company tokens are empty, or use their default.
  • Unknown properties don’t block the send. If a token names a property that doesn’t exist — usually a typo — it becomes empty, the email still sends, and the send’s entry in the Send log lists the tokens it left empty under Unknown tokens left empty.
  • Dates read naturally. Date properties show as a date such as October 3, 2026, and date-and-time properties add the time in UTC, such as October 3, 2026 14:05 UTC.
  • Dropdown, radio, checkbox, and yes/no properties show their labels — the text you see in HubSpot, such as Gold plan — not the option’s internal value. Several selected options show as a comma-separated list. A label you change in HubSpot can take up to an hour to show in sent emails.
  • Special characters are escaped, so a property value can’t change the email’s layout.
  • Other HubL — {% if %} blocks, loops, and filters other than default.
  • Tokens for records other than the recipient’s contact, its primary company, and the workflow’s enrolled record — for example the deal’s associated company or its line items. Copy the value onto the enrolled record first.
  • Tokens for carts, payments, leads, or other objects HubSpot’s Personalize button doesn’t offer.
  • Unsubscribe, subscription-preference, and office-address tokens ({{ unsubscribe_* }}, {{ site_settings.* }}). They’re removed, because transactional email has no unsubscribe footer.
  • Type tokens exactly as shown above, with the contact., company., or record prefix (such as deal.), so they’re recognized.
  • Add a default to every token in a greeting or subject line, so a missing value never leaves a gap.
  • After changing tokens, send a test to yourself and check its entry in the Send log for unknown tokens. App Home’s error report doesn’t count them, so the send log is the place to look.