Start free
ActionKnockUpdated June 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.

FieldTypeRequiredDescription
Workflow Key
workflow
stringRequiredWorkflow Key. e.g. "new-comment"
Recipient ID
recipientId
stringRequiredRecipient ID
Actor ID
actorId
stringOptionalWho triggered this notification
Data
data
jsonOptionalData. (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.

Gmail → Knock
1 Gmail triggers
Slack → Knock
13 Slack triggers
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. TinyCommand handles Knock's rate limits automatically so you don't have to throttle manually.
Trigger Knock Workflow in Knock — start free