ActionIterableUpdated September 2026

How do I send an Iterable triggered email?

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

Iterable Send Triggered Email in Iterable — start free All 6 Iterable actions

Iterable Send Triggered Email in Iterable — 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
Campaign ID campaignId	string	Required	–
Recipient Email recipientEmail	string	Required	–
Data Fields (JSON merge) dataFields	string	Optional	–

Sample request

{
  "campaignId": "{{trigger.campaignId}}",
  "recipientEmail": "{{trigger.recipientEmail}}",
  "dataFields": "{{trigger.dataFields}}"
}

Returns

{
  "msg": "Success",
  "code": "Success"
}

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

Triggered by

Apps that pair well as the trigger for Iterable Send Triggered Email.

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

Google Sheets → Iterable

2 Google Sheets triggers

HubSpot → Iterable

18 HubSpot triggers

FAQ

Questions about Iterable Send Triggered Email.

What does the Iterable Send Triggered Email action do in Iterable?

Fires a specific transactional template at a user with merged data. Respects user subscription preferences. For "password reset, order confirmation" workflows where the email content is reviewed in Iterable but the trigger is external.

What inputs does Iterable Send Triggered Email require?

Required: Campaign ID, Recipient 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 Iterable returns an error?

The run history shows the failed step with its input and the error message Iterable 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 Iterable Send Triggered Email support batch operations?

Run Iterable Send Triggered 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 Iterable's rate limits.

More actions