Browse Product guides

Kit setup

Connect your Kit account so your Plandalf automations can act on your subscribers. When someone buys, a sequence can tag them, add them to a Kit form or email sequence, and keep their custom fields up to date. Kit events, such as a new subscriber or a tag being added, can also start a Plandalf sequence.

Kit was called ConvertKit until 2024. You may still see that name in older guides and in some Plandalf URLs.

Before you start

  • A Kit account where you can create API keys.
  • The tags, forms, sequences and custom fields you plan to use, already set up in Kit. The Tag Subscriber step can also create new tags for you.
  • A Plandalf checkout to connect it to, if you want purchases to reach Kit.

Get your Kit API key

Plandalf connects with a V4 API key.

  1. Open the Developer settings in Kit

    Log in to Kit. Click your account name in the top-right corner, choose Settings, then open Developer.

  2. Create a V4 key

    Under V4 Keys, click Add a new key. Give it a name you will recognise later, such as “Plandalf”.

  3. Copy the key

    Copy the key Kit shows you and keep it somewhere safe until you paste it into Plandalf. Use the V4 key, not the legacy V3 key listed on the same page.

Connect Kit to Plandalf

  1. Find Kit in the Marketplace

    In Plandalf, open Automation in the sidebar and choose the Marketplace tab. Find Kit under Available now and click Connect.

  2. Paste the key

    In the Connect Kit window, keep or change the Integration name, paste your key into API Key, then click Connect.

  3. Check the result

    Plandalf checks the key with Kit straight away. When you see Kit connected, choose Build an automation to start a sequence, or Not now.

Your connection now appears under Automation → My apps. You can connect more than one Kit account; each step asks which account to use.

Steps you can add

Every step below takes the subscriber’s email address. In a purchase sequence, insert {{trigger.customer_email}} from the variable menu.

The steps that add something (a tag, a form, a sequence) create the subscriber first if Kit doesn’t have them yet, so you don’t need a separate create step. The steps that only change an existing subscriber skip cleanly when the email isn’t in Kit.

Find or Create Subscriber

Finds a Kit subscriber by email or creates one.

  • Email Address (required).
  • First Name, usually {{trigger.customer_first_name}}.
  • Custom Fields: pairs of a Kit custom field key and a value, for example last_name and {{trigger.customer_last_name}}. Use the key as Kit shows it for the field. Blank values are skipped, so an empty variable never wipes data in Kit.

Tag Subscriber

Adds one or more tags to a subscriber, creating the subscriber and any new tags as needed.

  • Email Address (required).
  • Tags (required): pick tags from your Kit account, or type a name to create a new tag. Typed names can include variables from the trigger or earlier steps.
  • First Name, used if the subscriber is new to Kit.

Remove Tag from Subscriber

Removes a tag. If the email isn’t in Kit, or the subscriber doesn’t have the tag, the step is skipped rather than failed.

  • Email Address (required).
  • Tag (required).

Add Subscriber to Form

Subscribes someone to a Kit form or landing page. Any Kit automation that starts from that form will run.

  • Email Address (required).
  • Form (required): a form or landing page from your Kit account.
  • First Name.
  • Referrer URL: an optional page address to record as the signup source. Kit reads UTM parameters from it.

Add Subscriber to Sequence

Starts a Kit email sequence for someone.

  • Email Address (required).
  • Sequence (required): the sequence must be active in Kit.
  • First Name.

Update Subscriber Fields

Updates custom fields on an existing subscriber. Skips if the email isn’t in Kit.

  • Email Address (required).
  • Custom Fields (required): Kit field keys and values, for example plan and Pro.
  • First Name: leave it empty to keep the name Kit already has.

Note. Purchases are not sent to Kit Kit only accepts purchase records from apps connected through Kit’s OAuth sign-in. Plandalf connects with an API key, so purchases don’t appear in Kit’s purchase history. Record what someone bought with a tag or a custom field instead.

Start a sequence from Kit

Choose Kit as the trigger app to start a Plandalf sequence from something that happens in Kit:

  • Subscriber Created: a new subscriber is added to your Kit account.
  • Tag Added to Subscriber: a tag is added. Pick a Tag to fire only for that tag, or leave it blank for any tag.
  • Subscriber Joined Form: someone subscribes through a form or landing page. Pick a Form, or leave it blank for any form.
  • Subscriber Unsubscribed: a subscriber unsubscribes from your Kit emails.

You don’t need to set up anything in Kit. When you save the trigger, Plandalf adds a webhook to your Kit account named after your sequence, and the trigger’s 2. Config tab shows Connected to Kit. Deleting the trigger removes the webhook again.

Each trigger gives later steps the subscriber’s email, first_name, subscriber_id, state and custom fields, plus the tag or form name where it applies. A common use is the Enroll in Promo step, which starts a promo timer for anyone who joins a Kit form.

Example: tag buyers and start onboarding

This sequence tags everyone who buys a checkout as a customer, then starts a Kit onboarding sequence.

  1. Create the sequence

    Go to Automation → My Sequences, create a sequence and name it, for example “Course buyers to Kit”.

  2. Set the trigger

    Choose Plandalf as the app and Checkout Completed as the trigger event. Under Offer, pick the checkout this sequence is for. On 3. Test, pick a recent checkout as the sample record so the variable menu fills with real values.

  3. Tag the buyer

    Click Add a step, choose Kit and Tag Subscriber, and pick your Kit account. Set Email Address to {{trigger.customer_email}}, add a tag such as “Customer” to Tags, and set First Name to {{trigger.customer_first_name}}.

  4. Start the Kit sequence

    Add a second step: Kit, Add Subscriber to Sequence. Use the same email and pick your onboarding sequence. Check it is active in Kit.

  5. Test and turn it on

    Run each step’s test. Testing makes a real change in Kit, so use your own email or a test subscriber. Then turn the sequence On.

Test purchases skip automations by default. To try the whole flow with a test card, open the sequence’s Settings, switch on Run on test purchases, buy through the checkout’s test link, and switch it off again when you’re done.

Common errors

What you seeWhat to do
Authentication failed when connectingCheck you pasted a V4 key from Settings → Developer, not the V3 key. Plandalf keeps the failed connection in My apps. Open it there, paste the right key and choose Test Connection, rather than connecting again.
“Email is empty”The email field didn’t resolve. Map it to {{trigger.customer_email}} or another step’s email output, and check the trigger sample has an email.
“The selected Kit tag no longer exists”The tag was deleted or renamed in Kit. Open the step and pick the tag again.
“Kit rejected the sequence”The Kit sequence is a draft or paused. Make it active in Kit, then re-run the step.
Remove Tag or Update Fields shows skippedKit has no subscriber with that email, or they don’t have the tag. Nothing needed changing.
“Kit didn’t accept the webhook” on a Kit triggerKit’s reason is shown underneath. Fix it, usually an expired key or a removed connection, then click Try again.
A step fails with a rate limit messageKit allows 120 requests a minute per key. Plandalf retries twice automatically. If it still fails, re-run the step once the burst has passed.

Feature detail