Kit (ConvertKit)

Integration

Kit (ConvertKit)

Plandalf integrates with Kit (ConvertKit) as a email, marketing, website, sdk platform.

What it does

Product surfaces

Where Kit (ConvertKit) fits in the buying workflow

Integrations work best when the checkout surface, payment state, invoice record, and post-purchase automation all point at the same commercial object. These product screens show the Plandalf controls that should be configured before Kit (ConvertKit) receives checkout, payment, tax, or workflow context.

The Numi offer editor showing layout, product, theme, automation, invoice, and settings controls.

Offer configuration stays visible

Use Offers to decide what Kit (ConvertKit) receives: product, price, buyer, checkout mode, invoice, and automation context.

The Numi checkout elements palette showing content, interactive, and selling blocks.

Checkout layout and selling blocks stay editable

Before Kit (ConvertKit) enters the stack, operators still need checkout templates, products, prices, coupons, order bumps, upsells, and branded offer content they can inspect.

The Numi offer editor automation tab showing sequence controls beside the checkout canvas.

Purchase events can start follow-up

Kit (ConvertKit) should fit into the work after checkout: fulfilment, records, CRM updates, support context, webhooks, and sequences.

The Numi offer editor showing hosted checkout mode controls.

Builder paths

Stack guides that use Kit (ConvertKit)

Use these stack guides when a builder needs the whole path: sales surface, Plandalf offer, payment handoff, automation, fulfilment, records, and downstream integrations.

Overview

Kit — previously ConvertKit — is the email platform of choice for creators. Its Visual Automations product supports a native Send-a-webhook action, making Plandalf enrolment one automation step away from any subscribe event.

What Plandalf does here

  • Broadcast countdown — a <img> tag with Kit’s {{ subscriber.email_address }} merge tag renders per recipient.
  • Automation-driven enrolment — Send-a-webhook POSTs a full JSON subscriber payload; the catch URL reads the email and creates a participant per unique subscriber.

Setup templates

Drop-in implementations

Copy-paste setups for the most common ways to wire Kit (ConvertKit) into Plandalf.

promo · email

Drop the Plandalf countdown image into a Kit broadcast

Paste this <img> tag into a Kit broadcast or sequence email via the HTML source view. {{ subscriber.email_address }} is Kit's merge tag — it substitutes per recipient at send time.

<img
  src="{{ promo.countdown_url }}?ref={{ subscriber.email_address }}"
  alt="Time remaining on this offer"
/>

promo · automation

Enrol Kit subscribers via a Visual Automation

  1. In Kit, go to Automate → Visual Automations and create one.
  2. Pick a trigger — Subscribes to a form, Completes a sequence, or Purchases a product are the most common fits.
  3. Add an action: Run an action → Send a webhook.
  4. URL:
    {{ promo.catch_url }}
    
  5. Kit POSTs a JSON payload containing subscriber.email_address and related fields. No body editing needed.
  6. Save and publish the automation.

Automation graph

Connecting Kit (ConvertKit)

How Kit (ConvertKit) participates in Plandalf sequences: what events it exposes upward, and what actions Plandalf can perform on it.

Triggers from Kit (ConvertKit)

Events Plandalf can subscribe to through webhooks, API work, checkout state, payment context, and connected integrations.

convertkit.subscriber_added
Fires when a new subscriber is added to Kit (ConvertKit).
convertkit.automation_step_reached
Fires when a contact reaches a designated step in a Kit (ConvertKit) automation.
convertkit.form_submitted
Fires when a form on Kit (ConvertKit) is submitted.
convertkit.webhook
Fires when Kit (ConvertKit) POSTs to a Plandalf webhook URL — use for anything not covered by a native trigger.

Actions on Kit (ConvertKit)

Things Plandalf sequences can do after checkout, payment, invoice, customer, or deadline events.

convertkit.add_subscriber
Add a contact to a list or audience in Kit (ConvertKit).
convertkit.tag
Apply a tag or segment to an existing Kit (ConvertKit) contact.
convertkit.send_email
Send a one-off transactional or broadcast email through Kit (ConvertKit).
convertkit.start_automation
Enrol a contact into a Kit (ConvertKit) automation.
convertkit.custom_api_call
Hit any Kit (ConvertKit) REST endpoint with a templated payload.

Embeddable surfaces: Plandalf countdown image and buy button HTML · Per-recipient countdown GIF with merge-tag substitution

Example sequence
trigger: stripe.payment_succeeded
actions:
  - convertkit.add_subscriber:
      list: paying-customers
      tag: tier-${plan}
  - plandalf.grant_entitlement: ${product_slug}

Integration methods

How Kit (ConvertKit) connects to Plandalf

Each method below is the minimum viable setup. Pick the one closest to how you already use Kit (ConvertKit) with checkout, payments, invoices, webhooks, API work, SDK checkout, and integrations.

  1. Method 1

    Embed a Plandalf buy button

    Drop the Plandalf embed script into a Kit (ConvertKit) HTML block and tag any element with `data-plandalf-present` to open the configured flow on click.

    <script src="https://cdn.plandalf.com/embed.js" async></script>
    
    <button data-plandalf-present="offer_abc123">
      Buy now
    </button>
  2. Method 2

    Drop in a per-recipient countdown image

    Add an HTML block to any Kit (ConvertKit) email and paste the Plandalf countdown URL. Kit (ConvertKit)'s merge tag `{{ subscriber.email_address }}` substitutes per recipient so each subscriber sees a timer pegged to their own deadline.

    <img
      src="https://cdn.plandalf.com/timers/{TIMER_ID}.gif?ref={{ subscriber.email_address }}"
      alt="Time remaining on this offer"
      width="600"
      height="120"
    />
  3. Method 3

    Trigger a sequence from a form

    Point a Kit (ConvertKit) form's webhook / POST URL at Plandalf's intake endpoint and every submission starts whatever sequence you've mapped to it.

    curl -X POST https://api.plandalf.com/v1/intake/convertkit \
      -H "Content-Type: application/json" \
      -d '{"email": "{{ form.email }}", "source": "convertkit"}'
  4. Method 4

    Enrol from an automation step

    Inside Kit (ConvertKit)'s automation builder, add a Webhook step that POSTs the contact to a Plandalf sequence catch URL. Use this to mirror Kit (ConvertKit) journey logic into Plandalf without re-building the segmentation.

    {
      "email": "{{ contact.email }}",
      "sequence": "post-signup-onboarding",
      "source": "convertkit"
    }
  5. Method 5

    REST API webhook

    For anything not covered by a native trigger, configure a Kit (ConvertKit) webhook to POST to Plandalf. The payload is forwarded into the sequence as `${event}`.

    curl -X POST https://api.plandalf.com/v1/webhooks/convertkit \
      -H "Authorization: Bearer $PLANDALF_API_KEY" \
      -H "Content-Type: application/json" \
      -d @event.json
Official Kit (ConvertKit) docs and sign-up: kit.com

FAQ

Common questions about the Kit (ConvertKit) integration

Do I need a paid plan to use Kit (ConvertKit) with Plandalf?

Plandalf itself is free to connect. Kit (ConvertKit)'s native webhook step is on its paid tiers — on the free plan, route the trigger through Zapier instead, which still works end-to-end.

How long does setup take?

Under 10 minutes. OAuth (or paste an API key), pick the lists/segments you care about, and you're live. No code unless you want it.

Can I disconnect Kit (ConvertKit) later without losing data?

Yes. Disconnecting only revokes the credentials — historical events Plandalf fired stay in your sequence logs, and Kit (ConvertKit)'s own records are untouched. You can reconnect any time and resume from the last seen event.

Does Plandalf store Kit (ConvertKit) data?

Plandalf stores the Kit (ConvertKit) contact ID and the events Plandalf fired against that contact. Email content stays in Kit (ConvertKit); Plandalf doesn't mirror your audience or newsletter archive.

What if my email need isn't covered by the actions or triggers listed here?

Use the generic `convertkit.custom_api_call` action or the inbound `convertkit.webhook` trigger. Anything Kit (ConvertKit)'s REST API can do, a Plandalf sequence can drive.

Is there a usage limit?

Plandalf respects Kit (ConvertKit)'s API rate limits and backs off on 429s. For very high-volume use cases, ask about a dedicated worker pool.

Where do I find Kit (ConvertKit)'s own documentation?

Kit (ConvertKit)'s homepage at https://kit.com links to their developer docs. For Plandalf-side questions about the Kit (ConvertKit) integration, see the Plandalf docs.

Feature detail