HubSpot: Send Transactional Email

Send an existing HubSpot transactional email, such as a receipt or account notice, to one recipient.

Tool ID: hubspot_send_transactional_email

Run this action

This action has conditional or dynamic inputs. A static example cannot describe these inputs reliably. Read the live contract before you execute this action:

deepline describe hubspot_send_transactional_email --json

Example response

The static output schema lacks the details for a reliable example. Use deepline describe hubspot_send_transactional_email --json for the complete live contract.

Input reference

Send an existing HubSpot transactional email to one recipient through the transactional single-send API. Requires the HubSpot transactional email add-on and the transactional-email scope. Transactional email ignores subscription status, so use it only for receipts, account notices, and other relationship email.

Name	Type	Required	Default	Details
`payload.email_id`	`string`	Yes	—	Content ID of the HubSpot email to send, from the email editor URL or hubspot_list_marketing_emails. Pattern: `^[0-9]+$`.
`payload.to`	`string`	Yes	—	Recipient email address.
`payload.from`	`string`	No	—	Override for the From header, for example `Sender Name <sender@example.com>`. The address must be a verified HubSpot sending address. Minimum length: 1.
`payload.reply_to`	`array`	No	—	Reply-To addresses.
`payload.cc`	`array`	No	—	Cc addresses.
`payload.bcc`	`array`	No	—	Bcc addresses.
`payload.send_id`	`string`	No	—	Deduplication key. HubSpot sends at most one email per send ID per account. Inside a Play, Deepline derives one from the step when omitted so a retried step does not send twice. Minimum length: 1. Maximum length: 200.
`payload.contact_properties`	`record`	No	—	Contact property values to write on the recipient record before sending, available in the template as contact tokens.
`payload.custom_properties`	`record`	No	—	Values referenced in the email as `{{ custom.NAME }}`. HubSpot does not store them.

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`record`	Yes	—	Provider response payload.
`result.meta`	`record`	No	—	Additional response metadata (status, paging).

Deepline cost

Pricing model: fixed (per call).
Estimated Deepline credits: 0 per pricing unit.
Provider-native pricing may still exist outside Deepline credit billing.

​Run this action

​Example response

​Input reference

​Output reference

​Deepline cost

​Related documentation

Run this action

Example response

Input reference

Output reference

Deepline cost

Related documentation