ConvertKit (Kit) integration

What it does

The ConvertKit (Kit) integration lets your agency run a client's email marketing without leaving TaskJuice. Connect a client's Kit account once and you can list and look up subscribers, create or upsert subscribers from any upstream form or CRM, tag existing subscribers, and add subscribers to forms. Two polling triggers turn subscriber activity into workflow runs: one watches the subscribers endpoint for newly created records, the other watches a chosen tag for newly tagged subscribers.

Connect a ConvertKit (Kit) account

1. Open your workspace in TaskJuice and navigate to Connections.
2. Choose ConvertKit (Kit) and click Connect.
3. Sign in with the Kit account whose subscribers you want to manage on behalf of your client.
4. Authorize the connection on app.kit.com. Kit currently only exposes a single public OAuth scope, so a connected account inherits the permissions of the user who signed in.
5. TaskJuice returns you to the workspace with the connection ready to use in any workflow.

To revoke access at any time, sign in to Kit, open Account Settings, choose Apps, and disconnect the TaskJuice entry.

Triggers

• convertkit/subscriber-created polls the subscribers endpoint and fires once per cycle whose items array carries every subscriber whose created_at is greater than the previous watermark. Drop a Loop node downstream to process each subscriber individually, or aggregate a digest.
• convertkit/subscriber-tagged polls a chosen tag's subscribers endpoint and fires once per cycle whose items array carries every subscriber tagged since the previous watermark.

Actions

• convertkit/list-subscribers lists subscribers with optional status and email filters, paginated via the cursor returned in pagination.end_cursor.
• convertkit/get-subscriber fetches a single subscriber by numeric Kit ID, including custom field values.
• convertkit/create-subscriber creates (or upserts) a subscriber by email address. Custom fields are accepted as a map but must already exist on the account.
• convertkit/tag-subscriber applies a tag to an existing subscriber by tag and subscriber ID. Returns 200 if the subscriber already carries the tag, 201 if newly applied.
• convertkit/add-subscriber-to-form adds an existing subscriber to a Kit form, with an optional referrer URL captured at form submission.

Known limitations

• Kit's first-party webhooks ship as unsigned POSTs, which do not match the signed-payload contract used by the rest of the integration platform. The Kit integration therefore uses polling triggers instead. With the default 300 second interval, a single connection stays well under Kit's OAuth request budget of 600 requests per rolling minute.
• Kit currently only exposes a single public OAuth scope. Fine-grained access control via scopes is documented as "coming soon" on the Kit developer portal. A connected account inherits the permissions of the user who signed in.
• Kit's Create Subscriber action rejects custom field keys that do not already exist on the account. Create the custom field in Kit first, then reference its key in the action payload.
• Kit enforces 600 requests per OAuth client per rolling 60 second window. Very short poll intervals across many connections can exhaust the budget for the entire integration.