OtherReal-timeUpdated May 2026

Knock

Knock notification orchestration platform

Knock is the developer-focused notification orchestration platform — similar shape to Courier and Novu, single API to send notifications across email, SMS, push, in-app channels with per-user preference management. Tiny Command exposes one action, no triggers (Knock emits delivery events via webhooks configured per-channel; point at a Tiny Command webhook trigger URL): Trigger Workflow (fire a Knock workflow for a recipient with optional data payload — Knock handles channel routing per the workflow definition and user preferences). The connection uses a Knock API key. For developer-led notification orchestration that competes with Courier and Novu, Knock is a strong choice — particularly noted for clean API design and developer DX. Pricing is per-user; per-channel delivery costs (your SendGrid/Twilio bill) are separate.

Connect Knock

0triggers

1action

≈ 2 minto set up

Freetier · no card

Actions

Do anything Knock can do, from a workflow.

Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.

Action	What it does	Inputs
Trigger Knock Workflow	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.	4 fields	View →

Recipes

Pre-built Knock workflows.

Clone any recipe and customize it in one click. Every recipe is fully editable.

Knock → Slack alerts

AI-triage every Knock event, ping the right channel only when it matters.

Knock → Google Sheets log

Every event matching a filter, appended to a running spreadsheet.

Knock → Notion database

Turn Knock into a Notion-backed source of truth, auto-tagged.

Before you build

Three things worth knowing.

Filter at the trigger

Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.

Authorize once, reuse anywhere

Connect Knock once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.

No JSON to read

Every Knock field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.

FAQ

Questions about the Knock integration.

If we missed yours, ping support. We usually reply within an hour.

How do I connect Knock to Tiny Command?

Open the Tiny Command workflow builder, drop in a Knock node, and click Connect. Authorize Knock once and any workflow on your account can use its triggers and actions. Most teams finish the connection in under two minutes.

What Knock triggers does Tiny Command support?

Tiny Command focuses on outbound actions for Knock today. Use Tiny Command's universal Webhook or Schedule trigger to start Knock workflows, then run any Knock action you need.

What Knock actions can I run from a workflow?

1 Knock action are available out of the box, covering other operations like "Trigger Knock Workflow". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.

Is the Knock integration real-time?

Knock actions execute synchronously inside your workflow. Tiny Command waits for Knock's API to confirm before continuing to the next step, so downstream nodes can rely on the result.

Do I need to write code to use Knock with Tiny Command?

No. Every Knock trigger and action is fully configurable from the visual workflow builder. For edge cases that aren't covered, drop in a custom HTTP node and call any Knock API endpoint directly.

How much does the Knock integration cost?

There's a free tier you can start on without a credit card. Higher run volumes and team features come with paid plans. The Knock integration itself has no per-app surcharge.