Get the FREE Ultimate OpenClaw Setup Guide →

convertkit-automation

npx machina-cli add skill davepoon/buildwithclaude/convertkit-automation --openclaw
Files (1)
SKILL.md
7.1 KB

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

Source

git clone https://github.com/davepoon/buildwithclaude/blob/main/plugins/all-skills/skills/convertkit-automation/SKILL.mdView on GitHub

Overview

ConvertKit (Kit) Automation via Rube MCP lets you manage subscribers, tags, broadcasts, and broadcast stats from a unified toolkit. It relies on Rube MCP to connect Kit, discover current tool schemas with RUBE_SEARCH_TOOLS, and run predefined workflows.

How This Skill Works

Connect Rube MCP to Kit using an MCP server configured for toolkit kit, then authenticate via RUBE_MANAGE_CONNECTIONS. Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas, and then execute tool sequences like KIT_LIST_SUBSCRIBERS, KIT_TAG_SUBSCRIBER, KIT_DELETE_SUBSCRIBER, and KIT_LIST_BROADCASTS with the required parameters.

When to Use It

  • Browse, search, or filter subscribers by status, email, and date ranges.
  • Tag subscribers to support segmentation and targeted campaigns.
  • Unsubscribe a subscriber from all Kit communications.
  • List broadcasts and view details for planning campaigns.
  • Review broadcast performance and statistics to assess impact.

Quick Start

  1. Step 1: Verify Rube MCP is available by calling RUBE_SEARCH_TOOLS.
  2. Step 2: Set up the Kit connection with RUBE_MANAGE_CONNECTIONS and authenticate if prompted.
  3. Step 3: Run a core workflow, e.g., KIT_LIST_SUBSCRIBERS with filters or KIT_TAG_SUBSCRIBER to tag a subscriber.

Best Practices

  • Always verify RUBE_SEARCH_TOOLS returns current schemas before running workflows.
  • Ensure KIT_LIST_SUBSCRIBERS filters are precise (status, date ranges) and use exact email matching when searching.
  • When tagging, supply valid tag_id and subscriber_id as positive integers; tagging is idempotent.
  • Confirm the Kit connection is ACTIVE via RUBE_MANAGE_CONNECTIONS before executing workflows.
  • Use cursor-based pagination (after/before) and respect include_total_count as a string 'true'.

Example Use Cases

  • List all active subscribers created in the last 30 days.
  • Find a subscriber by email and apply a new tag.
  • Unsubscribe a subscriber by ID to stop all emails.
  • List all broadcasts and fetch details for a specific one.
  • Check broadcast stats to compare performance across campaigns.

Frequently Asked Questions

Add this skill to your agents

Related Skills

email-sequence

coreyhaines31/marketingskills

When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding-cro.

cold-email

coreyhaines31/marketingskills

Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Also use when the user mentions "cold outreach," "prospecting email," "outbound email," "email to leads," "reach out to prospects," "sales email," "follow-up email sequence," "nobody's replying to my emails," or "how do I write a cold email." Covers subject lines, opening lines, body copy, CTAs, personalization, and multi-touch follow-up sequences. For warm/lifecycle email sequences, see email-sequence. For sales collateral beyond emails, see sales-enablement.

activecampaign-automation

davepoon/buildwithclaude

Automate ActiveCampaign tasks via Rube MCP (Composio): manage contacts, tags, list subscriptions, automation enrollment, and tasks. Always search tools first for current schemas.

brevo-automation

davepoon/buildwithclaude

Automate Brevo (Sendinblue) tasks via Rube MCP (Composio): manage email campaigns, create/edit templates, track senders, and monitor campaign performance. Always search tools first for current schemas.

gmail-automation

davepoon/buildwithclaude

Automate Gmail tasks via Rube MCP (Composio): send/reply, search, labels, drafts, attachments. Always search tools first for current schemas.

klaviyo-automation

davepoon/buildwithclaude

Automate Klaviyo tasks via Rube MCP (Composio): manage email/SMS campaigns, inspect campaign messages, track tags, and monitor send jobs. Always search tools first for current schemas.

Sponsor this space

Reach thousands of developers