---
title: ConvertKit API Integration on Truto
slug: convertkit
category: Marketing Automation
canonical: "https://truto.one/integrations/detail/convertkit/"
---

# ConvertKit API Integration on Truto



**Category:** Marketing Automation  
**Status:** Generally available

## Unified APIs

### Unified Marketing Automation API

- **Campaigns** — The campaign represent a campaign in the remote system.
- **Contacts** — The contact represent a contact in the remote system.
- **Lists** — The list represent a list of contacts in the remote system.
- **Tags** — The tags on a contact in the remote system.

## How it works

1. **Link your customer's ConvertKit account.** Use Truto's frontend SDK; we handle every OAuth and API key flow so you don't need to create the OAuth app.
2. **Authentication is automatic.** Truto refreshes tokens, stores credentials securely, and injects them into every API request.
3. **Call Truto's API to reach ConvertKit.** The Proxy API is a 1-to-1 mapping of the ConvertKit API.
4. **Get a unified response format.** Every response uses a single shape, with cursor-based pagination and data in the `result` field.

## Use cases

- **Sync course completion events to trigger creator marketing workflows** — Online course and LMS platforms can push student progress data into ConvertKit by applying tags and updating custom fields, allowing creators to automatically trigger upsell sequences, send certificates, or segment students by completion status — all without leaving their existing marketing tool.
- **Route webinar and event registrants into creator funnels** — Event and webinar platforms can create contacts in ConvertKit, subscribe them to specific Forms (the entry points for creator funnels), and tag them based on attendance behavior like no-shows or replays watched — enabling creators to run targeted follow-up campaigns automatically.
- **Push behavioral and transactional signals into subscriber profiles** — SaaS platforms handling commerce, surveys, or product usage can write custom field values (like NPS scores, purchase amounts, or referral links) and apply tags to ConvertKit contacts, giving creators the segmentation data they need to personalize their email automations.
- **Keep subscriber lifecycle status in sync across platforms** — Membership, billing, and community platforms need to reflect subscription changes — upgrades, downgrades, cancellations — as tag additions or removals in ConvertKit, so creators' automated sequences stay accurate and don't market to churned users.
- **Surface subscriber marketing context inside support and CRM tools** — Helpdesk and CRM platforms can pull ConvertKit contact data — including tags, active sequences, and custom fields — to give support agents or account managers full visibility into a user's marketing journey without switching tabs.

## What you can build

- **Tag-based automation trigger sync** — Let your users map in-app events (e.g., course completed, invoice paid, survey submitted) to ConvertKit tags that automatically kick off the creator's pre-built visual automations.
- **Custom field passthrough for dynamic personalization** — Write arbitrary data like referral links, NPS scores, or plan names into ConvertKit custom fields so creators can inject them into emails using Liquid templating.
- **Form-based funnel entry point mapping** — Allow your users to select a ConvertKit Form as the destination for new leads, subscribing contacts to the correct entry point in the creator's marketing funnel.
- **Subscriber context sidebar for support agents** — Fetch a contact's tags, active sequences, and custom field values from ConvertKit and render them in your product's UI so agents have full marketing context during support interactions.
- **Campaign performance reporting dashboard** — Pull broadcast and sequence data from ConvertKit to display open rates, click rates, and unsubscribe metrics alongside your platform's own analytics.
- **Bidirectional lifecycle tag management** — Automatically add or remove ConvertKit tags when users change subscription tiers, cancel memberships, or hit milestones in your platform — and react to ConvertKit webhook events when subscribers opt out.

## FAQs

### How does ConvertKit handle lists differently from other marketing automation tools?

ConvertKit does not use traditional lists. Every subscriber exists exactly once in the database, and segmentation is driven entirely by Tags. To map to a 'list' concept, you subscribe contacts to ConvertKit Forms, which serve as funnel entry points. Truto's Unified Marketing Automation API maps the Lists resource to ConvertKit Forms accordingly.

### What authentication method does ConvertKit use?

ConvertKit supports both API Key (API Secret) authentication and OAuth 2.0. Truto handles the auth flow for your end users, so they can connect their ConvertKit accounts without you managing token exchange or refresh logic directly.

### How do Campaigns map in ConvertKit's API?

ConvertKit distinguishes between Sequences (automated drip campaigns) and Broadcasts (one-off sends). Both map to the Campaigns resource in Truto's Unified Marketing Automation API. Sequences are typically used for enrollment via integrations, while Broadcasts are more commonly read-only for reporting purposes.

### Are ConvertKit-specific tools available in Truto today?

ConvertKit tools are built on request. The integration is supported through Truto's Unified Marketing Automation API, which covers Campaigns, Contacts, Lists, and Tags. If you need ConvertKit-specific endpoints beyond the unified schema, Truto can build custom tools for your use case.

### Can I write custom fields to ConvertKit subscriber profiles via the integration?

Yes. ConvertKit supports custom fields on subscriber profiles (e.g., referral links, company names, scores). These can be written when creating or updating contacts. Note that ConvertKit's V3 API requires sequential updates for custom fields rather than bulk creation in a single call.

### Does ConvertKit support webhooks for real-time event handling?

Yes. ConvertKit's V4 API provides native webhook endpoints for events including subscriber activation, unsubscribes, tag additions, and purchases. These are valuable for building bidirectional syncs where your platform needs to react when a creator's subscriber opts out or changes state.
