CActionCourierUpdated September 2026
How do I send a Courier notification?
Short answer: You can send notification in Courier by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Courier Send Notification 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.
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 |
|---|---|---|---|
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"}" |
Sample request
{"event": "{{trigger.event}}","recipientEmail": "{{trigger.from}}","data": "{\"name\":\"John\",\"order_id\":\"12345\"}"}
Returns
{"requestId": "req123"}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Send Notification.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Send Notification.
What does the Send Notification action do in Courier?
Fires a Courier notification for a recipient with optional data payload. Courier handles channel selection (email, SMS, push, in-app) per the template config and the recipient's preferences. The single-call abstraction over the multi-channel notification stack.
What inputs does Send Notification require?
Required: Event/Template 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 Courier returns an error?
The run history shows the failed step with its input and the error message Courier 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 Notification support batch operations?
Run Send Notification 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 Courier's rate limits.