Send Transactional Email
This action sends a transactional email to a single recipient using a published HubSpot email. It is a typical way to notify a customer about an event in another system, for example, a new order or a delivered parcel.
To use this action, you need to prepare and publish the email in HubSpot first. See Preparing Email in HubSpot for details.
When Skyvia retrieves the action schema, for example, when you configure the action, it doesn't send the email.
Action Parameters
| PARAMETER NAME | DESCRIPTION |
|---|---|
| EmailId | Identifier of the published transactional email (required). |
| To | Recipient email address (required). You can specify only one address. HubSpot finds or creates a contact with this address. |
| From | Sender in the Name <address> format. If not specified, the sender from the email settings is used. |
| SendId | Idempotency key. HubSpot sends no more than one email for the same SendId in an account. If not specified, Skyvia generates a unique value. It prevents duplicates caused by repeated HTTP requests, but not by repeated trigger runs. We recommend passing a stable event key, for example, recharge-order-412871245. |
| ReplyTo | Reply-to addresses. |
| Cc | CC addresses. |
| Bcc | BCC addresses. |
| ContactProperties | JSON object with contact properties, for example, {"firstname":"Jane"}. These values are saved to the HubSpot contact and are available in the template as contact properties. |
| CustomProperties | JSON object with values for this email only, for example, {"order_number":"#1047"}. Use them in the template as {{ custom.<name> }} tokens. HubSpot doesn't store these values. Only flat key-value pairs are supported. Nested objects are not displayed, and arrays work only in programmable emails. |
ReplyTo, Cc, and Bcc accept either a JSON array, for example,
["a@example.com","b@example.com"], or a list of addresses separated by commas or semicolons.
Result
The action sends the email and returns one record with the following fields.
| FIELD NAME | DESCRIPTION |
|---|---|
| StatusId | Identifier of the send operation in HubSpot. |
| Status | Send status. Possible values are PENDING, PROCESSING, CANCELED, and COMPLETE. The sending is asynchronous, so the status is usually PENDING right after the action is performed. It doesn't mean that the email is delivered. |
| SendResult | Result of the sending, if HubSpot already knows it. For example, SENT, QUEUED, INVALID_TO_ADDRESS, PREVIOUSLY_BOUNCED, MISSING_CONTENT (invalid EmailId or the email isn't configured for sending through the API), MISSING_TEMPLATE_PROPERTIES (CustomProperties don't contain the tokens used in the template). |
| RequestedAt | Time when the sending was requested. |
| StartedAt | Time when the sending started. |
| CompletedAt | Time when the sending completed. |
| EventId | Identifier of the send event, if the email is already sent. |
Requirements
To use this action, you need the following:
- HubSpot Marketing Hub Professional or Enterprise subscription with the Transactional Email add-on.
- The transactional-email scope in the HubSpot connection. For OAuth connections, Skyvia requests this scope as optional. Thus, if you created your connection before this feature appeared, re-sign in to HubSpot in the connection. For private app connections, add the transactional-email scope to the app settings in HubSpot.
See SendTransactionalEmail for more details.