Short answer: Drop the "Knock → Trigger Knock Workflow" 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 Key workflow | string | Required | Workflow Key. e.g. "new-comment" |
Recipient ID recipientId | string | Required | Recipient ID |
Actor ID actorId | string | Optional | Who triggered this notification |
Data data | json | Optional | Data. (JSON object). e.g. "{"comment_text":"Great post!"}" |
{"workflow": "new-comment","recipientId": "{{trigger.recipientId}}","actorId": "{{trigger.actorId}}","data": "{\"comment_text\":\"Great post!\"}"}
{"workflow_run_id": "wfr_123"}
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.