Per-pair page

Connect Knock to Slack in two minutes.

Real-time triggers from Knock, ready-made actions in Slack. Filter, transform, and route without writing a line of code.

Connect Knock to Slack — start free See reverse direction

Trigger app

Knock as the trigger

Workflows fire when something happens in Knock.

Knock has no triggers yet. Use the catalog's universal Webhook trigger as the upstream.

Action app

Slack as the action

Workflows do something in Slack, instantly.

See all 45 actions →

Both directions

Pick the way that fits your stack.

Pair pages are mirrored. Each direction gets its own dedicated page.

Knock → Slack

When something happens in Knock, do it in Slack.

0 Knock triggers wired to 45 Slack actions.

Slack → Knock

Or fire it the other way around.

13 Slack triggers wired to 1 Knock actions downstream.

See Slack → Knock →

How it works

Connect Knock and Slack in five steps.

No code, no glue, no half-day setup. Each step is one click.

1
Connect
Authorize Knock and Slack
Open TinyCommand, authorize Knock and Slack once each. Both connections are available to every workflow on your account.
2
Trigger
Pick a Knock trigger
Drop the Knock → New event trigger onto the canvas. TinyCommand auto-registers the webhook.
POST /v1/webhooks/knock.event
3
Transform
Add a filter or AI step
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
4
Action
Add the Slack action
Drop the Slack → Add Reaction action below it. Map fields from the Knock payload into the Slack inputs.
slack.add-reaction
5
Publish
Publish and forget
Hit Publish. TinyCommand runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about Knock + Slack.

How long does it take to connect Knock and Slack on TinyCommand?

Under two minutes. Authorize Knock and Slack once each, drop the Knock trigger and Slack action onto a workflow canvas, map a couple of fields, and publish. No code, no glue.

Is the Knock ↔ Slack integration real-time?

Yes. Both Knock and Slack expose webhooks, so events from one fire workflows in the other within seconds rather than on a polling interval.

Can I filter or transform data between Knock and Slack?

Yes. Add a Filter node to only pass through matching events, a Switch node to branch by value, or an AI / Code node to transform payloads before they hit Slack.

What Knock events can trigger a Slack workflow?

Use TinyCommand's universal Webhook trigger to receive Knock events, then run any of the 45 Slack actions downstream.

Do I need a paid plan to use Knock with Slack?

No. There's a free tier that covers most Knock+Slack use cases without a credit card. Paid plans unlock higher run volumes and team features when you outgrow it.

What if I want Slack → Knock instead?

Build it the same way, in reverse. There's a dedicated /integrations/slack/with/knock page with the reverse-direction triggers and actions.