Skip to main content
skill CX Codex

convertkit-automation — Claude Code skill

convertkit-automation automates ConvertKit (Kit) workflows via Rube MCP: search and filter subscribers, assign tags, view broadcasts, and pull campaign stats. Requires Rube MCP and an active Kit connection.

MIT 123 installs ★ 3,785 updated 2026-10-25

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add davepoon/buildwithclaude --skill convertkit-automation -a claude-code
Open on GitHub

What convertkit-automation does

This skill integrates with Rube MCP and Composio's Kit toolkit to handle subscriber management, tagging for segmentation, and broadcast tracking. Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas, as the API can evolve.

Key tasks: search subscribers with filters and cursor-based pagination, tag subscribers, unsubscribe permanently, list broadcasts with performance metrics, and remove drafts or sent campaigns. Setup is minimal—add https://rube.app/mcp to your client config and authenticate via RUBE_MANAGE_CONNECTIONS; no API keys needed.

Watch parameter types carefully: include_total_count is a string 'true', not a boolean; email_address matches exactly (no substring search); sorting by cancelled_at requires status='cancelled'. Unsubscribing a subscriber is permanent, and deleting a broadcast does not unsend already-delivered messages.

What it helps with

  • Search for a subscriber by email and retrieve their profile
  • Tag multiple subscribers for audience segmentation
  • Permanently unsubscribe a subscriber from all messages
  • View broadcast history with open and click statistics
  • Delete a campaign draft before sending

Example prompts for the agent

  • Find the subscriber with email [email protected] and show their ID and status
  • Tag all active subscribers with ID 42
  • Unsubscribe subscriber 3887204736 from all communications

How to install convertkit-automation

1Skills CLI (Vercel)

npx skills add davepoon/buildwithclaude --skill convertkit-automation -a claude-code

2Manually: put the files in place

~/.claude/skills/convertkit-automation/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/convertkit-automation/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about convertkit-automation

How do I install convertkit-automation in Claude Code?

Run npx skills add davepoon/buildwithclaude --skill convertkit-automation -a claude-code, then view ~/.claude/skills/convertkit-automation/SKILL.md. For other platforms, use the appropriate flag: -a codex for Codex, -a cursor for Cursor, -a gemini-cli for Gemini CLI.

What does convertkit-automation do?

It lets you manage ConvertKit directly from your AI editor via Rube MCP. Search subscribers, assign tags, unsubscribe users, and retrieve campaign performance—all without logging into the Kit web interface.

What setup do I need?

Add Rube MCP by including https://rube.app/mcp in your client config. Authenticate Kit via RUBE_MANAGE_CONNECTIONS. Call RUBE_SEARCH_TOOLS before each operation to fetch current schemas. No API keys required.

Source text

SKILL.md · MIT
---
name: convertkit-automation
description: "Automate ConvertKit (Kit) tasks via Rube MCP (Composio): manage subscribers, tags, broadcasts, and broadcast stats. Always search tools first for current schemas."
requires:
  mcp: [rube]
category: email
---

# ConvertKit (Kit) Automation via Rube MCP

Automate ConvertKit (now known as Kit) email marketing operations through Composio's Kit toolkit via Rube MCP.

**Toolkit docs**: [composio.dev/toolkits/kit](https://composio.dev/toolkits/kit)

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Kit connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `kit`
- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas

## Setup

**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.


1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `kit`
3. If connection is not ACTIVE, follow the returned auth link to complete Kit authentication
4. Confirm connection status shows ACTIVE before running any workflows

## Core Workflows

### 1. List and Search Subscribers

**When to use**: User wants to browse, search, or filter email subscribers

**Tool sequence**:
1. `KIT_LIST_SUBSCRIBERS` - List subscribers with filters and pagination [Required]

**Key parameters**:
- `status`: Filter by status ('active' or 'inactive')
- `email_address`: Exact email to search for
- `created_after`/`created_before`: Date range filter (YYYY-MM-DD)
- `updated_after`/`updated_before`: Date range filter (YYYY-MM-DD)
- `sort_field`: Sort by 'id', 'cancelled_at', or 'updated_at'
- `sort_order`: 'asc' or 'desc'
- `per_page`: Results per page (min 1)
- `after`/`before`: Cursor strings for pagination
- `include_total_count`: Set to 'true' to get total subscriber count

**Pitfalls**:
- If `sort_field` is 'cancelled_at', the `status` must be set to 'cancelled'
- Date filters use YYYY-MM-DD format (no time component)
- `email_address` is an exact match; partial email search is not supported
- Pagination uses cursor-based approach with `after`/`before` cursor strings
- `include_total_count` is a string 'true', not a boolean

### 2. Manage Subscriber Tags

**When to use**: User wants to tag subscribers for segmentation

**Tool sequence**:
1. `KIT_LIST_SUBSCRIBERS` - Find subscriber ID by email [Prerequisite]
2. `KIT_TAG_SUBSCRIBER` - Associate a subscriber with a tag [Required]
3. `KIT_LIST_TAG_SUBSCRIBERS` - List subscribers for a specific tag [Optional]

**Key parameters for tagging**:
- `tag_id`: Numeric tag ID (required)
- `subscriber_id`: Numeric subscriber ID (required)

**Pitfalls**:
- Both `tag_id` and `subscriber_id` must be positive integers
- Tag IDs must reference existing tags; tags are created via the Kit web UI
- Tagging an already-tagged subscriber is idempotent (no error)
- Subscriber IDs are returned from LIST_SUBSCRIBERS; use `email_address` filter to find specific subscribers

### 3. Unsubscribe a Subscriber

**When to use**: User wants to unsubscribe a subscriber from all communications

**Tool sequence**:
1. `KIT_LIST_SUBSCRIBERS` - Find subscriber ID [Prerequisite]
2. `KIT_DELETE_SUBSCRIBER` - Unsubscribe the subscriber [Required]

**Key parameters**:
- `id`: Subscriber ID (required, positive integer)

**Pitfalls**:
- This permanently unsubscribes the subscriber from ALL email communications
- The subscriber's historical data is retained but they will no longer receive emails
- Operation is idempotent; unsubscribing an already-unsubscribed subscriber succeeds without error
- Returns empty response (HTTP 204 No Content) on success
- Subscriber ID must exist; non-existent IDs return 404

### 4. List and View Broadcasts

**When to use**: User wants to browse email broadcasts or get details of a specific one

**Tool sequence**:
1. `KIT_LIST_BROADCASTS` - List all broadcasts with pagination [Required]
2. `KIT_GET_BROADCAST` - Get detailed information for a specific broadcast [Optional]
3. `KIT_GET_BROADCAST_STATS` - Get performance statistics for a broadcast [Optional]

**Key parameters for listing**:
- `per_page`: Results per page (1-500)
- `after`/`before`: Cursor strings for pagination
- `include_total_count`: Set to 'true' for total count

**Key parameters for details**:
- `id`: Broadcast ID (required, positive integer)

**Pitfalls**:
- `per_page` max is 500 for broadcasts
- Broadcast stats are only available for sent broadcasts
- Draft broadcasts will not have stats
- Broadcast IDs are numeric integers

### 5. Delete a Broadcast

**When to use**: User wants to permanently remove a broadcast

**Tool sequence**:
1. `KIT_LIST_BROADCASTS` - Find the broadcast to delete [Prerequisite]
2. `KIT_GET_BROADCAST` - Verify it is the correct broadcast [Optional]
3. `KIT_DELETE_BROADCAST` - Permanently delete the broadcast [Required]

**Key parameters**:
- `id`: Broadcast ID (required)

**Pitfalls**:
- Deletion is permanent and cannot be undone
- Deleting a sent broadcast removes it but does not unsend the emails
- Confirm the broadcast ID before deleting

## Common Patterns

### Subscriber Lookup by Email

```
1. Call KIT_LIST_SUBSCRIBERS with email_address='[email protected]'
2. Extract subscriber ID from the response
3. Use ID for tagging, unsubscribing, or other operations
```

### Pagination

Kit uses cursor-based pagination:
- Check response for `after` cursor value
- Pass cursor as `after` parameter in next request
- Continue until no more cursor is returned
- Use `include_total_count: 'true'` to track progress

### Tag-Based Segmentation

```
1. Create tags in Kit web UI
2. Use KIT_TAG_SUBSCRIBER to assign tags to subscribers
3. Use KIT_LIST_TAG_SUBSCRIBERS to view subscribers per tag
```

## Known Pitfalls

**ID Formats**:
- Subscriber IDs: positive integers (e.g., 3887204736)
- Tag IDs: positive integers
- Broadcast IDs: positive integers
- All IDs are numeric, not strings

**Status Values**:
- Subscriber statuses: 'active', 'inactive', 'cancelled'
- Some operations are restricted by status (e.g., sorting by cancelled_at requires status='cancelled')

**String vs Boolean Parameters**:
- `include_total_count` is a string 'true', not a boolean true
- `sort_order` is a string enum: 'asc' or 'desc'

**Rate Limits**:
- Kit API has per-account rate limits
- Implement backoff on 429 responses
- Bulk operations should be paced appropriately

**Response Parsing**:
- Response data may be nested under `data` or `data.data`
- Parse defensively with fallback patterns
- Cursor values are opaque strings; use exactly as returned

## Quick Reference

| Task | Tool Slug | Key Params |
|------|-----------|------------|
| List subscribers | KIT_LIST_SUBSCRIBERS | status, email_address, per_page |
| Tag subscriber | KIT_TAG_SUBSCRIBER | tag_id, subscriber_id |
| List tag subscribers | KIT_LIST_TAG_SUBSCRIBERS | tag_id |
| Unsubscribe | KIT_DELETE_SUBSCRIBER | id |
| List broadcasts | KIT_LIST_BROADCASTS | per_page, after |
| Get broadcast | KIT_GET_BROADCAST | id |
| Get broadcast stats | KIT_GET_BROADCAST_STATS | id |
| Delete broadcast | KIT_DELETE_BROADCAST | id |

---
*Powered by [Composio](https://composio.dev)*

© davepoon · MIT · davepoon/buildwithclaude

Similar skills

All skills for Marketing and content →
customer-sales-automation Seth Hobson The customer-sales-automation plugin automates customer work: support requests, sales pipeline, email campaigns and CRM integration. Useful when the agent has to handle conversations and deals, not just code. CX Codex ★ 42,780repo stars codex-oauth-automation-extension reason-machines codex-oauth-automation-extension installs a Chrome extension that walks the whole OpenAI OAuth signup and login: pulls the email code, confirms the callback, repeats for several rounds. CX Codex +1 512installs Mailchimp Automation Claude Office Skills Mailchimp Automation — a skill that automates Mailchimp email marketing: builds campaigns, segments subscribers, sets up email sequences and reads engagement reports. CX Codex +1 4,800installs marketing-content-pipeline-automation reason-machines marketing-content-pipeline-automation — a Claude Code skill that sets up a pipeline for trend research, article generation, and video rendering with Remotion. One keyword turns into a written piece and a clip for Reels, TikTok, or Shorts. CX Codex +1 783installs marketing-automation akillness The marketing-automation skill turns a vague marketing request into one operating mode, one discipline and one operator packet with an owner and proof. CX Codex +1 381installs reddit-automation flowkit-labs reddit-automation finds Reddit threads where people actually need what you sell, then drafts short helpful replies that disclose your affiliation. CX Codex +1 1,500,000installs

From the same set235

The whole set →
helpdesk-automation helpdesk-automation reads HelpDesk tickets, agent views, and canned replies through Rube MCP and Composio. Built for support agents managing ticket backlogs. CX Codex +1 124installs sentry-automation sentry-automation is a Claude Code skill for managing Sentry errors, alerts, and releases via Rube MCP. Search issues, inspect events, and track deployments from your IDE. CX Codex +1 123installs cal-com-automation cal-com-automation automates Cal.com scheduling, availability lookups, and webhooks via Rube MCP. Useful when an agent needs to manage booking slots or team calendars directly. CX Codex +1 123installs segment-automation The segment-automation skill connects an agent to Segment through Rube MCP for events, user profiles, groups, page views, and batch requests. CX Codex +1 123installs miro-automation miro-automation automates Miro boards through Rube MCP, creating sticky notes, frames, and connectors or managing team sharing. CX Codex +1 123installs vercel-automation vercel-automation is a Claude Code skill that manages Vercel projects through Rube MCP, including deployments, settings, environment variables, domains, and DNS. CX Codex +1 123installs close-automation close-automation automates Close CRM operations through Rube MCP, managing leads, call logging, SMS, tasks, and notes directly from your coding agent. CX Codex +1 122installs circleci-automation circleci-automation is a Claude Code skill for CircleCI via Rube MCP: trigger pipelines, check workflow and job status, and download artifacts and test results. Requires an active CircleCI connection via Composio. CX Codex +1 122installs

Project sponsors

Companies that keep this analytics open