Yes, you can pull HubSpot standard objects into automated emails, but the object type and your workflow setup determine what data actually appears

HubSpot standard objects — contacts, companies, deals, and tickets — can be inserted into automated emails through personalization tokens. When you set up a workflow that sends an email, you choose which object the workflow is based on (the primary object), and that object's properties become available as merge fields in your email template. A contact-based workflow can pull contact properties like first name or email address. A deal-based workflow can pull deal properties like deal name or amount. The limitation is that you can only directly reference properties from the primary object and, in some cases, associated records of that object.

The practical difference matters: if you want to send an email to a contact that includes their company name, HubSpot can do that because contacts are associated with companies. If you want to send an email to a contact that includes details from a deal they are involved in, you need the workflow to be deal-based, not contact-based — or you need to use a workaround like a custom property on the contact that pulls deal data.

Key Takeaways

  • Contact-based workflows can pull contact properties and associated company properties directly into emails using personalization tokens.
  • Deal-based workflows can pull deal properties and associated contact or company properties, but not arbitrary contact data outside that deal relationship.
  • Ticket-based workflows can pull ticket properties and associated contact properties, making them useful for support automation.
  • If you need data from an object that is not directly associated with your workflow's primary object, you must either change the workflow's primary object or use a custom property to bridge the data.

Contact-Based Workflows and What They Can Pull

Contact-based workflows are the most common automated email setup. When your workflow is triggered by a contact action — like filling out a form, reaching a lifecycle stage, or matching a list — the email can reference any contact property. This includes standard fields like first name, last name, email, phone, and company name. It also includes any custom properties you have created on the contact object.

Because contacts are associated with companies in HubSpot, you can also pull company properties into a contact-based email. If you want to reference the company's industry, annual revenue, or number of employees, those fields are available as merge fields. The syntax in the email template looks like this: if you want the contact's first name, you use {{contact.firstname}}; if you want their associated company name, you use {{contact.hs_lead_status}} for contact properties or navigate to company properties through the associated company object.

The limitation is that you cannot pull data from deals or tickets directly in a contact-based workflow email, even if that contact is involved in deals or tickets. If you need deal information in the email, you must either switch to a deal-based workflow or create a custom property on the contact that stores deal data (which requires a separate automation or integration to keep it updated).

Deal-Based Workflows and Associated Object Data

Deal-based workflows send emails triggered by deal events — like a deal entering a stage, being created, or reaching a certain value. In these workflows, the primary object is the deal, so all deal properties are available as merge fields: deal name, deal amount, deal stage, close date, and any custom deal properties you have created.

Deal-based emails can also reference associated contact and company data. If the deal is associated with a contact, you can pull that contact's name, email, or other contact properties. If the deal is associated with a company, you can pull company properties. However, you cannot pull data from multiple contacts or multiple companies associated with the same deal — HubSpot will use the primary contact and primary company associated with the deal.

A common use case is sending a deal update email to a contact when a deal moves to a specific stage. The email can include the deal name, amount, and expected close date, plus the contact's name and company. If you need to include information from a related ticket or a different contact on the deal, you will need to either use a different workflow structure or store that data in a custom property.

Ticket-Based Workflows and Support Automation

Ticket-based workflows are triggered by ticket events — like a ticket being created, assigned, or moved to a status. The primary object is the ticket, so ticket properties like ticket ID, subject, description, priority, and status are available in the email template.

Ticket-based emails can pull associated contact properties because tickets are linked to contacts. You can reference the contact's name, email, phone, and company information. This is useful for sending automated support emails that address the customer by name or reference their company. However, you cannot directly pull deal data or other ticket data in a ticket-based workflow email.

If you need to include deal information in a support email, you would need to either create a custom property on the ticket that references the deal, or set up a separate workflow that is deal-based instead of ticket-based.

How to Insert Personalization Tokens in Your Email Template

In HubSpot's email editor, you insert merge fields by clicking the personalization icon (usually a curly-bracket symbol) in the email template. A menu appears showing all available properties for the workflow's primary object and its associated objects. You select the property you want, and HubSpot inserts the token — for example, {{contact.firstname}} or {{deal.dealname}}.

If a contact does not have a value for a property you have referenced, HubSpot can display a fallback value. You can set this in the personalization token settings — for example, if a contact has no first name, the email might say "Hello there" instead of leaving a blank space. This prevents awkward emails when data is missing.

You can also use conditional content blocks to show or hide sections of the email based on whether a property has a value. For example, you might show a special offer only to contacts in a specific industry, or include deal details only if the deal amount exceeds a certain threshold. This requires using HubSpot's conditional logic, which is available in the email editor.

When You Cannot Pull the Data You Need

The most common limitation is trying to pull data from an object that is not associated with your workflow's primary object. For example, if you have a contact-based workflow and you want to include information from a specific deal that contact is involved in, HubSpot cannot do that directly because the workflow does not know which deal to reference — the contact may be involved in multiple deals.

The workaround is to change the workflow's primary object to deal, so the email is sent based on deal events rather than contact events. This gives you access to deal properties and the associated contact. Alternatively, you can create a custom property on the contact that stores the relevant deal information, and use a separate automation to keep that property updated whenever the deal changes.

Another limitation is that you cannot pull data from related objects beyond one level of association. For example, in a deal-based workflow, you can pull contact and company data, but you cannot pull ticket data associated with that contact. If you need ticket information, you would need to create a custom property or use a different workflow structure.

Testing Your Merge Fields Before Sending

Before you publish a workflow that sends emails with personalization tokens, HubSpot allows you to preview the email with real data from a test contact or deal. Click the preview button in the email editor, select a record from your database, and HubSpot will show you exactly how the email will look with that record's data. This catches missing data, broken tokens, or awkward formatting before the email goes out to your entire audience.

If a merge field shows as blank in the preview, it means that test record does not have a value for that property. You can either choose a different test record that has the data, or add a fallback value to the token so the email still reads correctly even when data is missing.

Frequently Asked Questions

Can I pull data from multiple deals in a single contact-based email?

No. Contact-based workflows can only reference contact and company properties, not deal properties. If you need deal information in the email, switch the workflow to be deal-based. If you need information from multiple deals, you would need to create a custom property on the contact that stores aggregated deal data, updated by a separate automation.

What happens if a contact is not associated with a company?

The company merge fields will be blank. You can set a fallback value in the personalization token settings so the email still reads correctly — for example, "Hello [contact name]" instead of "Hello [contact name] at [blank]". Use conditional content blocks to hide company-related sections if the company field is empty.

Can I pull custom properties I created on standard objects?

Yes. Any custom property you create on a contact, company, deal, or ticket object can be referenced in an automated email the same way as standard properties. The personalization menu shows all available properties, including custom ones.

Can I send an email to multiple contacts from a deal-based workflow?

No. Deal-based workflows send to the primary contact associated with the deal. If you need to email all contacts on a deal, you would need to create a separate contact-based workflow or use a custom property to store multiple contact information.

Do I need to manually update merge fields if a contact's data changes?

No. Merge fields pull live data from HubSpot at the time the email is sent. If a contact's first name changes before the email goes out, the email will use the updated name. The only exception is custom properties that are updated by external integrations — those update only when the integration runs.