Convertkit Automation logo

Convertkit Automation

CommunityPopular
davepoon
convertkit-automation

Automate ConvertKit (Kit) tasks via Rube MCP (Composio): manage subscribers, tags, broadcasts, and broadcast stats. Always search tools first for current schemas.

Overview

Publisherdavepoon
Repositorybuildwithclaude
Skill nameconvertkit-automation
Stars
3.5K
Forks
509
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by davepoon on GitHub. Read the source before you install it.

Installation

Install the Convertkit Automation AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/davepoon/buildwithclaude.git /tmp/buildwithclaude
mkdir -p .claude/skills
cp -r /tmp/buildwithclaude/plugins/all-skills/skills/convertkit-automation .claude/skills/convertkit-automation
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Convertkit Automation in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Convertkit Automation on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Convertkit Automation is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

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='user@example.com'
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

TaskTool SlugKey Params
List subscribersKIT_LIST_SUBSCRIBERSstatus, email_address, per_page
Tag subscriberKIT_TAG_SUBSCRIBERtag_id, subscriber_id
List tag subscribersKIT_LIST_TAG_SUBSCRIBERStag_id
UnsubscribeKIT_DELETE_SUBSCRIBERid
List broadcastsKIT_LIST_BROADCASTSper_page, after
Get broadcastKIT_GET_BROADCASTid
Get broadcast statsKIT_GET_BROADCAST_STATSid
Delete broadcastKIT_DELETE_BROADCASTid

Powered by Composio

Frequently asked questions

What does the Convertkit Automation AI skill do?

Automate ConvertKit (Kit) tasks via Rube MCP (Composio): manage subscribers, tags, broadcasts, and broadcast stats. Always search tools first for current schemas.

Why use Convertkit Automation on TypingMind?

Because you install it once and use it with any model. Convertkit Automation is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Convertkit Automation in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/davepoon/buildwithclaude/tree/main/plugins/all-skills/skills/convertkit-automation. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Convertkit Automation?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Convertkit Automation?

As many as you like. As long as a model supports skills, you can use Convertkit Automation with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Convertkit Automation AI skill free?

Yes. It is published on GitHub by davepoon under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇