Per-pair page

Connect Notion to Knock in two minutes.

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

Connect Notion and Knock See reverse direction

Trigger app

Notion as the trigger

Workflows fire when something happens in Notion.

Action app

Knock as the action

Workflows do something in Knock, instantly.

Trigger Knock WorkflowAPI

Both directions

Pick the way that fits your stack.

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

Notion → Knock

When something happens in Notion, do it in Knock.

3 Notion triggers wired to 1 Knock actions. Most-used pairing: New Database Item → Trigger Knock Workflow.

Knock → Notion

Or fire it the other way around.

0 Knock triggers wired to 12 Notion actions downstream.

Use any trigger in the catalog as the upstream.

See Knock → Notion →

Popular pairings

Common Notion → Knock workflows.

Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.

Showing 3 of 3 combinations

When new database item in Notion, trigger knock workflow in Knock.

Fires when a new item is added to a Notion database. Common use: mirror submissions into another tracker, send notifications, or run AI enrichment on the new row.

When new page in Notion, trigger knock workflow in Knock.

Fires when a new page is created in a Notion database (functionally the same event as Database Item Added; pick whichever name feels natural).

When page updated in Notion, trigger knock workflow in Knock.

Fires when a page is updated in a Notion database. Combine with property filters to react only to specific transitions (e.g. Status to Done).

How it works

Connect Notion and Knock in five steps.

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

1
Connect
Authorize Notion and Knock
Open Tiny Command, authorize Notion and Knock once each. Both connections are available to every workflow on your account.
2
Trigger
Pick a Notion trigger
Drop the Notion → New Database Item trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/notion.trigger-database-item-added
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 Knock action
Drop the Knock → Trigger Knock Workflow action below it. Map fields from the Notion payload into the Knock inputs.
knock.trigger-workflow
5
Publish
Publish and forget
Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about Notion + Knock.

How long does it take to connect Notion and Knock on Tiny Command?

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

Is the Notion ↔ Knock integration real-time?

Yes. Both Notion and Knock 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 Notion and Knock?

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 Knock.

What Notion events can trigger a Knock workflow?

Any of the 3 Notion triggers, including "New Database Item". Each fires in real time when the matching event happens in Notion.

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

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

What if I want Knock → Notion instead?

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

Other apps that pair well with Notion.

Notion + Gmail

Notion + Slack

Communication

Notion + Google Sheets

Spreadsheets & Databases