Adding the Send transactional email action
Add the action to any HubSpot workflow, choose a template, a recipient, and a sender profile, and send.
Overview
Section titled “Overview”Send transactional email is a custom workflow action. Each time a record reaches it, the action sends one template to one recipient and returns a send status your workflow can branch on.
The action is available in every HubSpot workflow type — contact, company, deal, ticket, invoice, quote, order, subscription and custom object workflows — so you can send a receipt from an order workflow or a renewal notice from a company workflow.
Before you begin
Section titled “Before you begin”- A sender profile. See Creating a sender profile. In the sandbox you can use the built-in sandbox sender instead.
- A template that’s been added in Settings → Templates and approved. See Adding a template.
- Permission to edit workflows in HubSpot.
-
Open or create a workflow in Automation → Workflows.
-
Add an action where the email should go out, and search for Send transactional email. It’s listed under Transactional Email.
-
Choose the Email template. The dropdown lists the templates a Super Admin added in Settings → Templates that are compatible and approved by the content review, and you can search it by name. Don’t see your email? Add it first, or check its status there. See Adding a template.

-
Choose the Sender profile. The default profile is listed first, marked (default); pick the one this email should come from. Until you go live the list also offers Sandbox sender (sandbox only), which needs no setup but stops working once you’re live.

-
Decide who receives it — see the next section. Usually you leave Recipient email blank.
-
Save the action and turn the workflow on.

The action now sends the template to the recipient each time a record reaches it, and returns a Send status your workflow can branch on. Every send also appears in App Home’s Send log.
Who receives the email
Section titled “Who receives the email”The action sends to the contact it runs on — the action’s target. Leave Recipient email blank in these cases:
| Workflow | Target | Recipient email | Who receives it |
|---|---|---|---|
| Contact workflow | The enrolled contact | Blank | That contact |
| Deal, company, or other workflow | Associated contacts | Blank | Each associated contact, one email each |
| Order or other workflow without a contact | The enrolled record (e.g. the order) | A property with the address, e.g. Billing email | That address |
- Fill in Recipient email only when the target isn’t a contact. Choose the
property that holds the address, or an email output from an earlier action.
HubSpot’s picker lists every text property, not just email addresses; a
property that doesn’t hold an address fails with
recipient_invalid. - When Recipient email is set, it’s always used, even if the target is a contact.
- If Recipient email is blank and the target isn’t a contact, or the
contact has no email address, the action returns
recipient_missing. - Don’t target several records with a fixed Recipient email (for example all associated contacts with one contact’s email): every run sends to the same address.
The address doesn’t have to belong to a HubSpot contact. When it does, 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.
What happens next
Section titled “What happens next”- Edited templates are reviewed again. When someone edits the email in HubSpot, the new version is reviewed before it sends. The action keeps its template; sends wait up to 10 minutes for a review in progress. See How the transactional content review works.
- An action keeps showing its template when the dropdown no longer offers it. If the selected template is in review, flagged, incompatible, or removed in Settings → Templates, it stays selected and the dropdown labels it with the reason, for example Order receipt (in review) or Order receipt (removed in Settings). Other templates in that state can’t be picked until they’re approved again.
- Tokens fill in from the recipient’s contact, the one whose primary Email matches the address the email goes to. If several contacts share the address, the most recently updated one is used. Company tokens come from that contact’s primary company. With no matching contact, contact and company tokens are empty — in a company workflow too, company tokens are the contact’s primary company, not the enrolled company. Deal, ticket, quote, invoice, order, subscription, and custom object tokens fill in from the workflow’s enrolled record, even when the action sends to its associated contacts. See Personalizing emails with tokens.
- The workflow always moves on, whether or not the email went out. When it didn’t, the workflow history marks the step as failed and shows the reason. Branch on Send status to handle failures. See Branching on send results.
What the action returns
Section titled “What the action returns”| Output | What it holds |
|---|---|
Send status (status) |
sent, queued_warmup, or the reason the email didn’t send. |
Message ID (message_id) |
The ID of the sent email. Empty when nothing was sent yet. |
Error code (error_code) |
The same code as Send status when the email didn’t send; empty for sent and queued_warmup. |
Every value is explained in Send status and error codes.
- Each run sends to one address. To email everyone on a deal, target its associated contacts and leave Recipient email blank.
- Recipient email takes a property, not a typed address.
Related articles
Section titled “Related articles”Ask the help center
Answers come from these guides, with links to the articles used.
Ask anything about Transactional Email or VLOOKUP for Workflow.

