Skip to content
Per-pair page

Connect Kit (ConvertKit) to Notion in two minutes.

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

Trigger app
Kit (ConvertKit) as the trigger

Workflows fire when something happens in Kit (ConvertKit).

Action app
Notion as the action

Workflows do something in Notion, instantly.

See all 12 actions →
Both directions

Pick the way that fits your stack.

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

Kit (ConvertKit)Notion

When something happens in Kit (ConvertKit), do it in Notion.

3 Kit (ConvertKit) triggers wired to 12 Notion actions. Most-used pairing: Form SubscribedAppend Content.

NotionKit (ConvertKit)

Or fire it the other way around.

3 Notion triggers wired to 4 Kit (ConvertKit) actions downstream.

See NotionKit (ConvertKit)
Popular pairings

Common Kit (ConvertKit) → Notion workflows.

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

Showing 9 of 36 combinations
When form subscribed in Kit (ConvertKit), append content in Notion.

Fires when a new subscriber confirms opt-in via a specific Kit form (after double-opt-in completes if enabled). Payload includes the subscriber with custom fields and the form they subscribed via. Scope to a single form ID at trigger setup.

When form subscribed in Kit (ConvertKit), create database in Notion.

Fires when a new subscriber confirms opt-in via a specific Kit form (after double-opt-in completes if enabled). Payload includes the subscriber with custom fields and the form they subscribed via. Scope to a single form ID at trigger setup.

When form subscribed in Kit (ConvertKit), create page in Notion.

Fires when a new subscriber confirms opt-in via a specific Kit form (after double-opt-in completes if enabled). Payload includes the subscriber with custom fields and the form they subscribed via. Scope to a single form ID at trigger setup.

When form subscribed in Kit (ConvertKit), delete block in Notion.

Fires when a new subscriber confirms opt-in via a specific Kit form (after double-opt-in completes if enabled). Payload includes the subscriber with custom fields and the form they subscribed via. Scope to a single form ID at trigger setup.

When subscriber activated in Kit (ConvertKit), append content in Notion.

Fires when a subscriber clicks the double-opt-in confirmation link. The granular hook for "they confirmed, now they're a real subscriber" downstream automation.

When subscriber activated in Kit (ConvertKit), create database in Notion.

Fires when a subscriber clicks the double-opt-in confirmation link. The granular hook for "they confirmed, now they're a real subscriber" downstream automation.

When subscriber activated in Kit (ConvertKit), create page in Notion.

Fires when a subscriber clicks the double-opt-in confirmation link. The granular hook for "they confirmed, now they're a real subscriber" downstream automation.

When subscriber activated in Kit (ConvertKit), delete block in Notion.

Fires when a subscriber clicks the double-opt-in confirmation link. The granular hook for "they confirmed, now they're a real subscriber" downstream automation.

When tag added in Kit (ConvertKit), append content in Notion.

Fires when a tag is added to a subscriber — by Kit automation, by manual edit, or by API. Tags are how Kit represents engagement state and interest, so this is the high-signal hook for behavioural workflows.

How it works

Connect Kit (ConvertKit) and Notion in five steps.

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

  1. 1
    Connect
    Authorize Kit (ConvertKit) and Notion

    Open Tiny Command, authorize Kit (ConvertKit) and Notion once each. Both connections are available to every workflow on your account.

  2. 2
    Trigger
    Pick a Kit (ConvertKit) trigger

    Drop the Kit (ConvertKit) → Form Subscribed trigger onto the canvas. Tiny Command auto-registers the webhook.

    POST /v1/webhooks/convertkit.trigger-form-subscribed
  3. 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. 4
    Action
    Add the Notion action

    Drop the Notion → Append Content action below it. Map fields from the Kit (ConvertKit) payload into the Notion inputs.

    notion.append-blocks
  5. 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 Kit (ConvertKit) + Notion.

How long does it take to connect Kit (ConvertKit) and Notion on Tiny Command?
Under two minutes. Authorize Kit (ConvertKit) and Notion once each, drop the Kit (ConvertKit) trigger and Notion action onto a workflow canvas, map a couple of fields, and publish. No code, no glue.
Is the Kit (ConvertKit) ↔ Notion integration real-time?
Yes. Both Kit (ConvertKit) and Notion 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 Kit (ConvertKit) and Notion?
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 Notion.
What Kit (ConvertKit) events can trigger a Notion workflow?
Any of the 3 Kit (ConvertKit) triggers, including "Form Subscribed". Each fires in real time when the matching event happens in Kit (ConvertKit).
Do I need a paid plan to use Kit (ConvertKit) with Notion?
No. There's a free tier that covers most Kit (ConvertKit)+Notion use cases without a credit card. Paid plans unlock higher run volumes and team features when you outgrow it.
What if I want Notion → Kit (ConvertKit) instead?
Build it the same way, in reverse. There's a dedicated /integrations/notion/with/convertkit page with the reverse-direction triggers and actions.
Related

Other apps that pair well with Kit (ConvertKit).


Wire Kit (ConvertKit) to Notion in 2 minutes.

Free tier available. No credit card. No onboarding call.