Short answer: Drop the "Courier → Send Notification" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Event/Template ID event | string | Required | Event/Template ID |
Recipient Email recipientEmail | Required | Recipient Email | |
Template Data data | json | Optional | Template Data. (JSON object). e.g. "{"name":"John","order_id":"12345"}" |
{"event": "{{trigger.event}}","recipientEmail": "{{trigger.from}}","data": "{\"name\":\"John\",\"order_id\":\"12345\"}"}
{"requestId": "req123"}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.