Skill

Automate ConvertKit Subscriber Management

Automates ConvertKit (Kit) subscriber management, tagging, and broadcast operations through Composio's Kit toolkit via Rube MCP.

Works with convertkitkit

76
Spark score
out of 100
Updated 2 days ago
Version 15.7.0
Models
universal

Add to Favorites

Why it matters

Streamline your email marketing by automating subscriber management within ConvertKit. This asset allows for efficient listing, tagging, and unsubscribing of subscribers, directly integrating with your existing ConvertKit setup.

Outcomes

What it gets done

01

List and search ConvertKit subscribers with advanced filtering.

02

Manage subscriber tags for effective audience segmentation.

03

Unsubscribe individual subscribers from all communications.

04

View and manage ConvertKit broadcasts and their statistics.

Install

Add it to your toolbox

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/ag-convertkit-automation | bash

Overview

ConvertKit (Kit) Automation via Rube MCP

A skill automating Kit (ConvertKit) subscriber, tag, and broadcast operations via Composio's Rube MCP toolkit. Use for Kit subscriber search, tagging, unsubscribe, or broadcast operations through Rube MCP with an active Kit connection.

What it does

This skill automates ConvertKit (now Kit) email marketing operations through Composio's Kit toolkit via Rube MCP (https://rube.app/mcp, no API keys needed). Prerequisites: Rube MCP connected with RUBE_SEARCH_TOOLS available, an active Kit connection via RUBE_MANAGE_CONNECTIONS with toolkit kit (completed via the returned auth link if not yet ACTIVE), and always calling RUBE_SEARCH_TOOLS first for current tool schemas.

Its core workflows: listing and searching subscribers via KIT_LIST_SUBSCRIBERS with filters (status, exact email match, YYYY-MM-DD created/updated date ranges, sort by id/cancelled_at/updated_at, cursor-based pagination) - noting sorting by cancelled_at requires status='cancelled' and include_total_count must be the string 'true' not a boolean; managing subscriber tags by first finding the subscriber ID via email lookup, then KIT_TAG_SUBSCRIBER (both tag_id and subscriber_id must be positive integers; tags themselves are created via the Kit web UI, not this API; tagging an already-tagged subscriber is idempotent) and optionally listing subscribers per tag; unsubscribing a subscriber via KIT_DELETE_SUBSCRIBER (permanently unsubscribes from ALL communications while retaining historical data, is idempotent, returns HTTP 204 on success, and 404s on a non-existent ID); listing and viewing broadcasts via KIT_LIST_BROADCASTS (per_page up to 500, cursor pagination) and KIT_GET_BROADCAST/KIT_GET_BROADCAST_STATS (stats only available for sent broadcasts, not drafts); and permanently deleting a broadcast via KIT_DELETE_BROADCAST after verifying it's the correct one (deletion cannot be undone, and does not unsend already-sent emails).

Common patterns: subscriber lookup by email (call LIST_SUBSCRIBERS with email_address, extract the subscriber ID, then use it for tagging/unsubscribing/other operations); cursor-based pagination (check the response for an after cursor, pass it as after in the next request, continue until no cursor is returned, using include_total_count: 'true' to track progress); and tag-based segmentation (create tags in the Kit web UI, assign via KIT_TAG_SUBSCRIBER, view membership via KIT_LIST_TAG_SUBSCRIBERS).

Known pitfalls: all IDs (subscriber, tag, broadcast) are positive integers, not strings; subscriber statuses are 'active', 'inactive', or 'cancelled' with some operations restricted by status; several parameters that look boolean are actually string enums (include_total_count, sort_order); Kit enforces per-account rate limits requiring backoff on HTTP 429 and paced bulk operations; and response data may be nested under data or data.data, requiring defensive parsing with cursor values used exactly as returned.

1. Call KIT_LIST_SUBSCRIBERS with email_address='user@example.com'
2. Extract subscriber ID from the response
3. Use ID for tagging, unsubscribing, or other operations

When to use - and when NOT to

Use this skill when listing/searching subscribers, tagging subscribers for segmentation, unsubscribing a subscriber, or listing/viewing/deleting broadcasts in Kit (ConvertKit) through Rube MCP.

Inputs and outputs

Inputs: a Kit subscriber or broadcast operation request (search, tag, unsubscribe, list, or delete) with the relevant filters or IDs.

Outputs: subscriber lists or lookups, tag assignments, unsubscribe confirmations, and broadcast details/stats or deletion confirmations, all resolved through the correct numeric IDs and cursor-based pagination.

Integrations

Rube MCP (https://rube.app/mcp), Composio's Kit toolkit (KIT_LIST_SUBSCRIBERS, KIT_TAG_SUBSCRIBER, KIT_DELETE_SUBSCRIBER, KIT_LIST_BROADCASTS, KIT_GET_BROADCAST_STATS, KIT_DELETE_BROADCAST), Kit (ConvertKit) OAuth.

Who it's for

Teams automating Kit (ConvertKit) email marketing operations - subscriber management, tag-based segmentation, and broadcast review/cleanup - via Rube MCP.

FAQ

Common questions

Discussion

Questions & comments · 0

Sign In Sign in to leave a comment.