Short answer: Drop the "Novu → Trigger Novu 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 |
|---|---|---|---|
Workflow Trigger ID name | string | Required | Workflow Trigger ID. e.g. "welcome-email" |
Subscriber ID to_subscriberId | string | Required | Subscriber ID |
Subscriber Email to_email | Optional | The email address. Used as the recipient or identifier depending on context. | |
Payload payload | json | Optional | Payload. (JSON object). e.g. "{"name":"John","plan":"pro"}" |
{"name": "welcome-email","to_subscriberId": "{{trigger.to_subscriberId}}","to_email": "e.g. user@example.com","payload": "{\"name\":\"John\",\"plan\":\"pro\"}"}
{"data": {"status": "processed","acknowledged": true,"transactionId": "txn123"}}
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.