ActionKnockUpdated September 2026

How do I fire a Knock notification workflow?

Short answer: You can trigger knock workflow in Knock by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Knock Trigger Knock Workflow action to a workflow, map its 4 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Trigger Knock Workflow in Knock — start free All 1 Knock actions

Trigger Knock Workflow in Knock — 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
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!"}"

Sample request

{
  "workflow": "new-comment",
  "recipientId": "{{trigger.recipientId}}",
  "actorId": "{{trigger.actorId}}",
  "data": "{\"comment_text\":\"Great post!\"}"
}

Returns

{
  "workflow_run_id": "wfr_123"
}

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

Triggered by

Apps that pair well as the trigger for Trigger Knock Workflow.

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

Google Sheets → Knock

2 Google Sheets triggers

HubSpot → Knock

18 HubSpot triggers

FAQ

Questions about Trigger Knock Workflow.

What does the Trigger Knock Workflow action do in Knock?

Fires a configured Knock workflow for a recipient with data payload. Knock handles channel selection (email, SMS, push, in-app) per workflow definition and user preferences. The single-call abstraction over multi-channel notification.

What inputs does Trigger Knock Workflow require?

Required: Workflow Key, Recipient ID. 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 Knock returns an error?

The run history shows the failed step with its input and the error message Knock 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 Trigger Knock Workflow support batch operations?

Run Trigger Knock Workflow 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 Knock's rate limits.

Trigger Knock Workflow in Knock — start free