ConvertKit (Kit)
Connect ConvertKit so approved affiliates land in a Kit form automatically, with tags.
Rekomi's ConvertKit (now branded as Kit) integration subscribes every approved affiliate to a Kit form you pick. ConvertKit's data model is form-centric rather than list-centric: a subscriber joins your account by being attached to a form, then automations and sequences fire off that form.
What syncs
When an affiliate is approved (or, optionally, when they apply), Rekomi runs Kit's v4 create-then-form sequence:
POST /v4/subscriberscreates or updates the subscriber by email withemail_address,first_name, andfields.last_name(Kit's v4 form endpoint only accepts subscribers that already exist, so this step always comes first).POST /v4/forms/{form_id}/subscribersadds the subscriber to your chosen form.- Each configured tag is applied by name (missing tags are auto-created in Kit).
The subscriber create is a documented upsert, re-subscribing the same email never duplicates the subscriber, it just refreshes their attributes. Being re-added to a form they are already on is also a no-op.
Finding your API key
In Kit:
- Open Settings → Developer.
- Click Generate API Key to create a v4 API key.
- Copy the key. Legacy v3 API secrets do not work; if you only have a v3 secret, generate a fresh v4 key.
Connecting ConvertKit in Rekomi
- Go to Integrations in the dashboard sidebar.
- Click the Kit (ConvertKit) card.
- Paste your v4 API key. Click Connect.
- Rekomi runs a test call against
GET /v4/accountto verify the key. - Once connected, pick a default form from the Form dropdown. Click refresh after creating a new form in Kit.
Tags
Optional. Comma-separated tag names. Rekomi resolves each name against your Kit account's tags and creates any that don't exist yet (Kit's tag creation is idempotent and case-insensitive), then attaches them to the subscriber.
The default Rekomi affiliate system tag is applied the same way, so every Rekomi-synced subscriber is identifiable in Kit out of the box. Tag failures are non-fatal: the subscriber is already on your form by the time tags are applied, so a tag hiccup never blocks the sync.
When sync fires
- Default: only
Approvedaffiliates sync. - Optional: enable "Include applicants before approval" in Advanced to sync
Pendingaffiliates immediately on apply.
Per-campaign overrides
Each campaign can route to a different Kit form or skip Kit entirely. Open the campaign's Integrations tab to set:
- A campaign-specific form (override the account default).
- Additional tag IDs (added to whatever's set at the account level).
- A per-campaign disable toggle.
Per-affiliate sync visibility
The affiliate detail page has a CRM sync panel showing each connected CRM and the latest sync state for that affiliate. The Resync button clears prior job rows and re-fires the sync from scratch, useful after fixing a misconfigured tag ID or form selection.
Troubleshooting
- "Kit migrated to API v4...", Your connection was created with a legacy v3 API secret, which does not authenticate against v4. Disconnect, generate a v4 API key in Kit (Settings → Developer → Generate API Key), and reconnect.
- "Form not found", The form was deleted in Kit after Rekomi cached its ID. Refresh the form picker and choose a current one.
- Tags not applying, Tag application is non-fatal, so the subscriber still lands on the form. Check the affiliate's CRM sync panel for the tag error, then hit Resync.
- Sync fails with 401/403 after working before, Rekomi marks the integration "action needed" and emails you a reconnect prompt once per breakage. Reconnect with a fresh v4 key, then use Resync all on the Failed tile of the integration page.
A note on API versions
Rekomi uses Kit's v4 API with personal API keys (header-based auth). Kit retired active development on v3, and v3 API secrets are a separate credential pair from v4 keys, which is why existing v3 connections must reconnect with a v4 key; there is no automatic migration.
Disconnecting
Click Disconnect on the Kit connect page. The integration row + any per-campaign overrides are deleted. Historical sync rows are preserved for audit.
See the convertkit integration overview on the marketing site for use-cases, persona fit, and unique automation patterns.