AActionAcumbamailUpdated May 2026

How do I send a single transactional email via Acumbamail?

Short answer: Drop the "Acumbamail → Send Transactional Email" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 3 Acumbamail actions

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
From Email from_email	string	Required	The email address. Used as the recipient or identifier depending on context.
From Name from_name	string	Optional	Acme Support
To Email to_email	string	Required	The email address. Used as the recipient or identifier depending on context.
Subject subject	string	Required	Message subject line.
HTML Body body	string	Required	Message body content. Plain text unless the API specifies HTML/markdown.

Sample request

{
  "from_email": "no-reply@acme.com",
  "from_name": "Acme Support",
  "to_email": "user@example.com",
  "subject": "e.g. Quick update",
  "body": "e.g. Hi there, thanks for reaching out."
}

Returns

{
  "id": "msg_abc123",
  "status": "sent"
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Send Transactional Email.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Acumbamail

2 Google Sheets triggers

HubSpot → Acumbamail

18 HubSpot triggers

FAQ

Questions about Send Transactional Email.

What does the Send Transactional Email action do in Acumbamail?

Sends a one-shot transactional email to a single recipient with subject, HTML body, and optional attachments. For sender-reputation hygiene, use separate Acumbamail sub-accounts/keys for transactional and marketing — mixing degrades deliverability over time.

What inputs does Send Transactional Email require?

Required: From Email, To Email, Subject, HTML Body. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Acumbamail returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Send Transactional Email support batch operations?

Yes. Run Send Transactional Email inside a Loop node to process arrays. Tiny Command handles Acumbamail's rate limits automatically so you don't have to throttle manually.

More actions