Krom Automation Pro connects to ConvertKit (now rebranded as Kit), the email marketing platform widely used by bloggers, course creators, and independent creators. With five actions available, you can subscribe users, add them to forms and sequences, apply or remove tags, and keep subscriber data in sync with WordPress events automatically.

An API key is required. No webhooks or OAuth setup needed.

Requirements #

• Krom Automation Pro installed and activated
• A ConvertKit account
• A ConvertKit API key

Configuration #

1. Log in to your ConvertKit account.
2. Go to Settings > Advanced.
3. Copy your API Key from the API section.
4. In your WordPress admin, go to Krom Automation > Settings.
5. Find the ConvertKit settings section and paste your API key into the API Key field.
6. Click Save.

Screenshot: ConvertKit Settings page with the Advanced tab open and the API Key highlighted.

Screenshot: Krom Automation Settings page with the ConvertKit API Key field filled in.

ConvertKit does not require an account URL or additional credentials. The API key alone is sufficient.

Available actions #

ConvertKit is an actions-only integration in Krom Automation Pro. There is no ConvertKit trigger — Krom Automation drives data into ConvertKit based on WordPress events, rather than receiving events from ConvertKit.

Subscribe or Update Subscriber

Adds a new subscriber to ConvertKit or updates an existing subscriber’s data if they already exist (matched by email address). This is an upsert operation — safe to call on contacts who may already be in ConvertKit.

Field	Required	Description
email	Yes	The subscriber’s email address. Use the appropriate merge tag from your trigger.
first_name	No	Subscriber’s first name.
Custom fields	No	Any ConvertKit custom fields you’ve defined can be updated here.

Common use: Syncing new WordPress user registrations to ConvertKit, adding WooCommerce customers as subscribers on purchase, or keeping subscriber first names updated when users edit their WordPress profile.

Subscribe to Form

Adds a subscriber to a specific ConvertKit form. In ConvertKit, forms can trigger automations and sequences, so subscribing someone to a form is often how you kick off a ConvertKit automation.

Field	Required	Description
form_id	Yes	The ConvertKit form ID. Find this in ConvertKit under Forms — it’s shown in the form’s URL and settings.
email	Yes	The subscriber’s email address.
first_name	No	Subscriber’s first name.

Common use: Enrolling a new WordPress user in a ConvertKit welcome form that triggers an automated email sequence, or adding a WooCommerce customer to an onboarding form after their first purchase.

Add Tag

Applies a tag to a ConvertKit subscriber. If the tag doesn’t exist in ConvertKit yet, it is created automatically.

Field	Required	Description
email	Yes	The subscriber’s email address.
tag_name	Yes	The tag to apply. Use a consistent naming convention across your workflows — tags are created automatically if they don’t exist.

Common use: Tagging a subscriber when they complete a LearnDash course, purchase a specific product, or reach a membership milestone. Tags in ConvertKit can trigger automations, making this action particularly powerful when combined with ConvertKit’s internal automation rules.

Remove Tag

Removes a tag from a ConvertKit subscriber. If the tag doesn’t exist or the subscriber doesn’t have it, the action completes silently without error.

Field	Required	Description
email	Yes	The subscriber’s email address.
tag_name	Yes	The tag to remove.

Common use: Removing an “active subscriber” tag when a WooCommerce Subscription is cancelled, or removing a “trial user” tag when a trial converts to a paid plan.

Add to Sequence

Enrolls a subscriber in a ConvertKit email sequence. The subscriber starts receiving the sequence’s emails from the first email in the sequence.

Field	Required	Description
sequence_id	Yes	The ConvertKit sequence ID. Find this in ConvertKit under Sequences — it’s visible in the sequence URL and settings.
email	Yes	The subscriber’s email address.

Common use: Enrolling a WooCommerce customer in a post-purchase email sequence, adding a new course enrollee to an onboarding sequence in ConvertKit, or starting a re-engagement sequence when a subscription is cancelled.

Setting up your first ConvertKit workflow #

1. Go to Krom Automation > Workflows and click Add New Workflow.
2. Choose your trigger. Common triggers for ConvertKit workflows are User Registered, WooCommerce Order Completed, LearnDash Course Completed, and MemberPress Member Signup Completed.
3. Click + and add a ConvertKit action — usually Subscribe or Update Subscriber first to ensure the contact exists, then any tagging or sequence actions.
4. Enter the email merge tag from your trigger, add a first name if available, and fill in any form, tag, or sequence IDs.
5. Simulate to confirm the action fields resolve correctly.
6. Activate.

Screenshot: Krom Automation canvas with a User Registered trigger connected to a ConvertKit Subscribe or Update Subscriber action, followed by a ConvertKit Add to Sequence action.

Finding ConvertKit IDs #

Several ConvertKit actions require IDs that aren’t immediately obvious to find.

Form ID: In ConvertKit, go to Grow > Landing Pages and Forms. Click on a form. The form ID appears in the URL — for example, app.kit.com/forms/1234567/edit. The number is your form ID.

Sequence ID: Go to Send > Sequences. Click on a sequence. The sequence ID appears in the URL similarly.

Tag name: Tags in ConvertKit are referenced by name, not ID. Enter the tag name exactly as you want it to appear in ConvertKit. Krom Automation creates it if it doesn’t exist yet.

Real-world automation examples #

Subscribe new users and start a welcome sequence Trigger: User Registered Action 1: ConvertKit Subscribe or Update Subscriber using {{user_email}} and {{first_name}} Action 2: ConvertKit Add to Sequence with your welcome sequence ID

Tag course completers in ConvertKit Trigger: LearnDash Course Completed Action: ConvertKit Add Tag to {{user_email}} with a tag like completed-course-name

Enrol purchasers in a post-purchase sequence Trigger: WooCommerce Order Completed Action 1: ConvertKit Subscribe or Update Subscriber using {{customer.email}} and {{customer.first_name}} Action 2: ConvertKit Add to Sequence with your post-purchase sequence ID

Remove tag on subscription cancellation Trigger: WooCommerce Subscriptions Cancelled Action: ConvertKit Remove Tag from {{customer.email}} removing the active-subscriber tag

Conditional tagging by product purchased Trigger: WooCommerce Order Completed Condition: items contains Product Name Yes branch: ConvertKit Add Tag with the product-specific tag No branch: ConvertKit Add Tag with a general purchaser tag

Pre-built templates #

Install these from Krom Automation > Templates:

Template	What it does
ck-user-registration-subscribe	Subscribes new WordPress users to ConvertKit
ck-woo-purchase-subscribe	Subscribes WooCommerce customers to ConvertKit on purchase
ck-learndash-course-complete-tag	Tags a ConvertKit subscriber on LearnDash course completion

Troubleshooting on ConvertKit integration #

The Subscribe or Update Subscriber action is failing

Check the execution log step detail for the specific error. The most common cause is an invalid or expired API key. Go to Krom Automation > Settings, re-enter your ConvertKit API key, and save.

The Add to Sequence action isn’t enrolling the subscriber

Confirm the subscriber exists in ConvertKit before running Add to Sequence. If they were just added by a Subscribe or Update Subscriber action in the same workflow, they should be available. Also confirm the sequence ID is correct — a wrong ID causes a silent failure or a not-found error in the log.

Tags are being created in ConvertKit with slightly wrong names

Krom Automation passes the tag name you enter exactly to the ConvertKit API, which creates it if it doesn’t exist. Check for extra spaces, different capitalisation, or a typo in the tag field. Consistent tag naming in Krom Automation action fields prevents duplicate tags building up in your ConvertKit account.