AActionAcumbamailUpdated September 2026

How do I send a single transactional email via Acumbamail?

Short answer: You can send transactional email in Acumbamail by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Acumbamail Send Transactional Email action to a workflow, map its 5 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Send Transactional Email in Acumbamail — start free All 3 Acumbamail actions

Send Transactional Email in Acumbamail — start free

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 run history shows the failed step with its input and the error message Acumbamail returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Send Transactional Email support batch operations?

Run Send Transactional Email inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Acumbamail's rate limits.

More actions

Other Acumbamail actions.

Action

Add Subscriber to List

Adds a contact to a specific Acumbamail subscriber list. Respects the list's configured double-opt-in setting — confirmed-only lists send the verification email first. The standard hook for "form submission → push to Acumbamail" workflows in Spanish/LATAM-targeted email programs.

Action

Get Subscriber Lists

Returns every list on the connected Acumbamail account with name, subscriber count, and configuration (double opt-in, custom fields). Use it to populate list-pickers at workflow setup or to inventory the account during audits.

Send Transactional Email in Acumbamail — start free