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 them from any upstream form or CRM, apply and remove tags, add people to forms and sequences, manage custom fields, and record purchases against a subscriber. Six polling triggers turn Kit activity into workflow runs, so a new subscriber, a new tag, or a new purchase can start an automation on your client's behalf.

Connect a ConvertKit (Kit) account

1. Open the workflow editor, add any ConvertKit (Kit) node, and use the node's own Connection field. Connecting from the node binds the credential to the right workspace, which is what the resource pickers need.
2. Choose Connect via OAuth, then Connect Account.
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 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 editor with the connection ready to use.

Your agency supplies its own Kit OAuth client, so the consent screen carries your brand. Register the app in Kit under Automate, Apps, Build, turn on API access, and keep Secure application enabled so Kit issues a client secret.

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

Triggers

Every trigger polls on a schedule you control and fires once per cycle, with an items array carrying the records seen in that cycle. Drop a Loop node downstream to process each record individually, or leave it as-is for a digest. The first cycle after publishing records what is already there without firing, so a new workflow never replays history.

• convertkit/subscriber-created watches the account for newly created subscribers.
• convertkit/subscriber-tagged watches a tag you choose for subscribers who newly receive it.
• convertkit/form-subscriber-added watches a form you choose for people who newly join it.
• convertkit/sequence-subscriber-added watches a sequence you choose for people who newly enter it.
• convertkit/purchase-created watches the account for newly recorded purchases.
• convertkit/subscriber-unsubscribed watches for subscribers who cancel.

Actions

• convertkit/list-subscribers lists subscribers with optional status and email filters, paginated via the cursor 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.
• convertkit/tag-subscriber applies a tag to an existing subscriber.
• convertkit/remove-tag-from-subscriber removes a tag from a subscriber.
• convertkit/add-subscriber-to-form adds an existing subscriber to a form, with an optional referrer URL.
• convertkit/add-subscriber-to-sequence adds an existing subscriber to a sequence.
• convertkit/create-purchase records a purchase against a buyer's email address, creating the subscriber if none exists.
• convertkit/create-tag creates a tag, returning the existing one if the name is already taken.
• convertkit/create-custom-field, convertkit/update-custom-field, and convertkit/delete-custom-field manage the account's custom fields.
• convertkit/list-forms, convertkit/list-sequences, convertkit/list-tags, and convertkit/list-custom-fields enumerate what the account holds.
• convertkit/list-form-subscribers, convertkit/list-sequence-subscribers, and convertkit/list-tag-subscribers list the people attached to a form, sequence, or tag.

Known limitations

• Kit's list endpoints are eventually consistent: a write is visible to a subsequent read in about 30 seconds typically, and up to five minutes at the tail. Triggers poll over a rolling look-back window rather than a forward watermark so a record that becomes visible late is still picked up, and each record is emitted once.
• Kit exposes a single public OAuth scope. Fine-grained scopes are documented as coming soon, so a connected account inherits the permissions of the user who signed in.
• Kit enforces 600 requests per OAuth client per rolling 60 second window. Very short poll intervals across many connections can exhaust that budget for every connection on the same client.
• Create Subscriber accepts custom field values keyed by the field's key, not its display label, and silently returns a warning rather than an error when the key does not exist. Create the field first, then reference its key.
• Kit provides no API to delete a subscriber, a tag, or a purchase, so those actions cannot be undone from a workflow.
• Purchases require OAuth. They are unavailable to integrations authenticated with a Kit API key.
• Kit's second-generation webhooks are signed and carry an event type, but deliver a batch of events under a single envelope key. TaskJuice fans out from a top-level array, so the Kit integration uses polling triggers until that envelope shape is supported.