TRANSACTIONAL EMAIL FOR HUBSPOT

How to send a transactional email from a HubSpot workflow

To send a transactional email from a HubSpot workflow, you need either HubSpot's Transactional Email add-on or an app that adds a transactional send action. HubSpot's built-in "Send email" action only sends marketing email, which skips anyone who has unsubscribed.

A HubSpot workflow that sends a transactional email and branches on its send status, with the Email template dropdown open

This guide walks through both routes, then builds one real example: a receipt that goes out when a deal closes.

Why the regular Send email action falls short

HubSpot workflows can send a marketing email to the enrolled contact. That's fine for nurture sequences. For a receipt, it has one serious gap: if the customer unsubscribed from your newsletter last year, HubSpot won't send them the receipt either.

Transactional email exists for exactly this. It's a relationship message the customer expects, so it goes out regardless of their marketing subscription status.

Route 1: HubSpot's Transactional Email add-on

As of October 2026, HubSpot lists its Transactional Email add-on at $600 a month. It's only available with Marketing Hub Professional or Enterprise, and you buy it through HubSpot's sales team. Read what it costs.

Route 2: A workflow action from an app

Cambium Transactional Email adds a Send transactional email action to the workflow editor. It works in contact, company, deal, ticket and custom-object workflows. You don't need Marketing Hub Professional: any Professional or Enterprise hub with workflows works, as long as you can use HubSpot's marketing email editor.

1. Build the email in HubSpot. Go to Marketing → Email and create a drag-and-drop email with HubSpot's standard modules. Use personalization tokens for contact properties ({{ contact.firstname }}) and the contact's primary company ({{ company.name }}). Save it as a draft. Don't publish, schedule or send it from HubSpot.

2. Add it as a template. A Super Admin opens Settings → Templates in the app, clicks Add a template and picks the email. The app checks its modules and runs the transactional content review, which usually finishes within a few minutes. Once the review approves it, the template appears in the workflow action.

Choosing a HubSpot email to add as a template

3. Create a sender profile. In Settings → Sending Setup, add a sender profile: the From name, the From address on your sending domain and an optional reply-to. Until you go live, you can test with the built-in sandbox sender instead.

The New sender profile form with From name, from address and reply-to

4. Add the action to a workflow. In the workflow editor, add Send transactional email. Choose the target, the template and the sender profile, and leave Recipient email blank. In a contact workflow the email goes to the enrolled contact; in other workflows, set the target to the associated contacts.

The Send transactional email action settings in a HubSpot workflow

5. Branch on the result. The action returns a send status, a message ID and an error code. Add a branch on Send status after it, so a failed send creates a task instead of disappearing.

A workflow branch on the Send status output with sent, queued and failure branches

Example: a receipt when a deal closes

Say a deal moves to Closed won and you want the buyer to get a receipt right away.

  1. Trigger: deal stage is Closed won.
  2. Copy the deal amount and close date onto the deal's associated contacts, so the template can use them as contact tokens.
  3. Send transactional email, with the target set to the deal's associated contacts, the template “Receipt”, the sender “Billing”, and Recipient email left blank.
  4. Branch on status. If it's anything other than sent or queued_warmup, create a task for the deal owner.

The receipt lands, and the send shows up on the contact's timeline.

Things that trip people up

The recipient doesn't have to be a HubSpot contact. When the address belongs to a contact, tokens fill in from that contact and the send shows on its timeline. When it doesn't, contact and company tokens are left empty and nothing is added to a timeline.

Tokens come from the contact and its primary company. Deal or ticket details need to be copied onto the contact first, as in step 2 of the example.

Custom modules don't render. Stick to HubSpot's standard modules (rich text, image, button, divider, spacer). A template with unsupported modules shows as Incompatible in Settings → Templates and never appears in the action's dropdown.

Promotional content gets blocked. Every template version gets the content review. A “20% off your next order” banner in a receipt will fail it, and the review shows the flagged passage, why and a suggested fix.

Install and try 20 free sends

FAQ

Frequently asked questions

Can the action send to more than one person?

Each email goes to one recipient, with no CC or BCC. In a deal, company or ticket workflow, set the target to the associated contacts and each of them gets their own email.

Can I attach a PDF?

Not today. Link to the file from the email instead, or store the link in a contact property and use it as a token.

What happens if the email bounces?

The bounce shows on the contact's timeline. Hard bounces, spam complaints and three soft bounces in a row suppress the address automatically and flag the contact. The next send to that address returns suppressed instead of trying again.

Does it work on ticket and custom object workflows?

Yes. Set the target to the record's associated contacts, or, when there's no contact to target, set Recipient email to a property that holds the address.