ConvertKit automations
Email Marketing · 1 integration
Creators and bloggers use ConvertKit (now officially rebranded as Kit) to manage subscriber lists, trigger email sequences, and tag contacts based on behavior — and automation platforms make it possible to connect those actions to storefronts, course platforms, and CRMs without manual work. Common use cases include adding buyers as subscribers, enrolling contacts in sequences after a purchase, and syncing tags between Kit and other tools. Choosing the right automation platform matters because Kit's API has meaningful rate limits and a recent v3-to-v4 migration that affects how each platform authenticates and calls the API.
What it costs to automate ConvertKit
Platform pricing at different volumes. Annual billing shown.
| Platform | Free tier | 100 tasks/mo | 1K tasks/mo | 10K tasks/mo |
|---|---|---|---|---|
| Zapier | 100 tasks/mo | Free | $69/mo | $69+/mo |
| Power Automate | 750 runs/mo | Free | $15/mo | $15/mo |
| Make | 1,000 credits/mo | Free | Free | $10.59/mo |
| Pipedream | 100 credits/mo | Free | $29/mo | $79/mo |
| n8n | Yes | $20/mo | $20/mo | $50/mo |
ConvertKit integrations
Each page compares all five platforms for that pair.
ConvertKit triggers & actions by platform
Which capabilities each platform supports for ConvertKit.
| Capability | Pipedream | Zapier | Power Automate | Make | n8n |
|---|---|---|---|---|---|
| Triggers | |||||
| New Sale (Gumroad) | ✓ | ✓ | — | — | — |
| Gumroad Ping (instant) | ✓ | — | — | — | — |
| HTTP Webhook (Gumroad Ping) | — | — | — | — | ✓ |
| Kit Trigger (native) | — | — | — | — | ✓ |
| New Product (Gumroad) | — | ✓ | — | — | — |
| New Subscriber (Kit) | ✓ | — | — | — | — |
| New Subscription (Gumroad) | — | ✓ | — | — | — |
| Watch New Sales (Gumroad) | — | — | — | ✓ | — |
| Watch New Subscribers (Kit) | — | — | — | ✓ | — |
| Watch Refunds (Gumroad) | — | — | — | ✓ | — |
| Actions | |||||
| Add to Sequence (Kit) | ✓ | ✓ | — | ✓ | ✓ |
| Add Subscriber to Form (Kit) | — | ✓ | — | ✓ | — |
| Add Tag (Kit) | ✓ | — | — | — | ✓ |
| Add Tag to Subscriber (Kit) | — | ✓ | — | ✓ | — |
| Remove Tag (Kit) | — | ✓ | — | ✓ | — |
| HTTP Request | ✓ | — | — | — | — |
| HTTP Request (Gumroad) | — | — | — | — | ✓ |
| List Sales (Gumroad) | — | — | — | ✓ | — |
| Run Node.js | ✓ | — | — | — | — |
| Unsubscribe (Kit) | — | ✓ | — | — | — |
Things to know about automating ConvertKit
API Key vs. OAuth Rate Limits
Kit enforces two distinct rate limit tiers: API key authentication allows only 120 requests per 60-second rolling window (~2 req/sec), while OAuth allows 600 requests per 60 seconds (~10 req/sec). For any serious integration volume, OAuth is the only viable authentication path — platforms like Zapier and Make handle this for you, but custom setups on n8n, Pipedream, or Power Automate must explicitly use OAuth to avoid constant 429 errors.
v3 to v4 API Migration
Kit's v4 API (hosted at api.kit.com/v4/) introduces breaking changes from v3: pagination is now cursor-based using before/after parameters instead of page offsets, the unsubscribe endpoint requires a subscriber ID instead of an email, and the email parameter for adding subscribers has been renamed to email_address. If your workflows on any platform — Zapier, Make, n8n, Pipedream, or Power Automate — use custom HTTP calls or older integration versions, they may silently break if they're still targeting api.convertkit.com/v3/.
Double Opt-In Blocks Automation Triggers
By default, Kit requires new subscribers to confirm via a double opt-in email before they appear as active subscribers, which means automation triggers on Zapier, Make, and other platforms won't fire until that confirmation happens. If you need instant downstream actions — like enrolling a buyer in a sequence immediately after purchase — you must disable double opt-in in the relevant Form Settings under 'Incentive Email.'
Free Plan Blocks API Access
A commonly missed blocker: Kit requires a paid plan before it grants access to API keys, which means free plan users cannot authenticate with Zapier, Make, n8n, Pipedream, or Power Automate at all. If onboarding fails silently with an authentication error, the account's plan tier is the first thing to check.
Production Webhook Bug in n8n
There is a confirmed bug in n8n where activating a ConvertKit trigger workflow creates only the test webhook URL with Kit's API — not the production URL. This means workflows appear to work during testing but never fire in live production when real events like tag additions or form subscriptions occur. Until this is patched, n8n users should validate production webhook registration directly in Kit's webhook logs after activation.
Manual Imports Bypass All Triggers
Adding subscribers through Kit's built-in 'Import Subscribers' bulk upload button bypasses every automation trigger — including Zapier Zaps, Make scenarios, n8n workflows, and webhooks entirely. Subscribers must be added via a form, landing page, or the Kit API to fire any downstream automation, making manual CSV imports a dead end for trigger-based workflows.
What breaks at scale
If your automation platform uses API key authentication — the default for personal setups on n8n, Pipedream, or Power Automate — you will hit Kit's 120 requests/60-second limit the moment you process more than about 2 subscriber operations per second. This is easy to reach during a batch tag operation, a sequence enrollment loop, or a product launch that sends a surge of new subscribers. The result is a flood of 429 errors; if your platform doesn't handle exponential backoff natively, requests will silently fail and subscribers will be left untagged or un-enrolled with no obvious error in Kit's UI.
Kit uses a single unified subscriber list architecture, which means a single unsubscribe event removes a contact from every sequence, automation, and broadcast associated with your account — not just the one they opted out of. At high subscriber volumes with multiple active automations running in parallel, this creates cascading failures: a subscriber who unsubscribes from a lead magnet sequence gets silently removed from an active paid course sequence too. Additionally, subscribers can get stuck in an 'on-hold' state inside Kit's visual automations at scale, requiring manual bulk-action intervention to progress — there is no API endpoint to bulk-release on-hold subscribers.
Kit's bulk import via CSV provides almost no error transparency: if 5 out of 1,000 records fail to import, you receive only a total count discrepancy with no detail on which records failed or why. More critically, any subscriber added through the 'Import Subscribers' button bypasses all automation triggers entirely — no Zaps fire, no Make scenarios activate, no webhooks are sent. At scale, this means bulk onboarding workflows that rely on Kit triggers are architecturally incompatible with manual imports, and you must route all high-volume additions through the API or a form submission to maintain trigger integrity.
Frequently asked questions
How do I automate ConvertKit (Kit) with Zapier, Make, or n8n?
All five major platforms — Zapier, Make, n8n, Pipedream, and Power Automate — support Kit integrations, though the depth varies. Zapier and Make offer native pre-built triggers and actions covering common operations like adding subscribers and applying tags, while n8n has built-in nodes for core features. Pipedream and Power Automate typically rely on Kit's v4 REST API via HTTP requests, giving more flexibility at the cost of more setup. Note that a paid Kit plan is required to access API credentials on any platform.
What are the ConvertKit API rate limits for automation?
Kit enforces a limit of 120 requests per 60-second rolling window when authenticating with API keys, and 600 requests per 60 seconds when using OAuth. Exceeding either limit returns a 429 status code, and the recommendation is to implement exponential backoff rather than immediate retries. If you're running high-frequency workflows on platforms like Pipedream, n8n, or Power Automate using custom HTTP calls, you should use OAuth authentication to get the higher quota.
Does ConvertKit support webhooks for automation?
Yes, Kit supports webhooks through its v4 API, and they can be used to trigger workflows in Zapier, Make, n8n, Pipedream, and Power Automate when events like new subscriptions or tag changes occur. However, Kit does not support webhooks for all event types, so some integrations will require polling. There is also a known production bug in n8n where activating a workflow registers only a test webhook with Kit rather than the production URL, causing live triggers to silently fail.
What breaks when migrating ConvertKit integrations from API v3 to v4?
Kit's v4 API changes the base URL to api.kit.com/v4/, switches all pagination from page/offset to cursor-based (before/after parameters), and modifies several endpoint behaviors — including requiring a subscriber ID instead of email for unsubscribes, and renaming the email field to email_address when adding subscribers. V3 API keys are not compatible with v4, so separate credentials are required. Any custom HTTP modules in Make, Pipedream, n8n, or Power Automate that still point to api.convertkit.com/v3/ will need to be updated.