ActionKnockUpdated May 2026

How do I fire a Knock notification workflow?

Short answer: Drop the "Knock → Trigger Knock Workflow" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 1 Knock actions

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 workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Trigger Knock Workflow support batch operations?

Yes. Run Trigger Knock Workflow inside a Loop node to process arrays. Tiny Command handles Knock's rate limits automatically so you don't have to throttle manually.

Send trigger knock workflow from your workflows.

Triggered by anything in the catalog. Free tier available. No credit card.

Try for free Request a demo