AActionAcumbamailUpdated May 2026

How do I add a subscriber to an Acumbamail list?

Short answer: Drop the "Acumbamail → Add Subscriber to List" 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
List ID list_id	string	Required	The List ID assigned by Acumbamail. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label.
Email email	string	Required	The email address. Used as the recipient or identifier depending on context.
Name name	string	Optional	Optional subscriber name.
Double Opt-in double_optin	options	Optional	—

Sample request

{
  "list_id": "12345",
  "email": "user@example.com",
  "name": "{{trigger.name}}",
  "double_optin": "{{trigger.double_optin}}"
}

Returns

{
  "status": "added",
  "subscriber_id": 12345
}

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

Triggered by

Apps that pair well as the trigger for Add Subscriber to List.

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 Add Subscriber to List.

What does the Add Subscriber to List action do in Acumbamail?

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.

What inputs does Add Subscriber to List require?

Required: List ID, Email. 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 Add Subscriber to List support batch operations?

Yes. Run Add Subscriber to List 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