mailchimp-automation
Automate Mailchimp email marketing including campaigns, audiences, subscribers, segments, and analytics via Rube MCP (Composio). Always search tools first for current schemas.
- License 许可
- MIT
- 最近更新
- 2026-11-10
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- mailchimp-automation
- risk
- critical
- source
- community
- date_added
- 2026-02-27
- description
- Automate Mailchimp email marketing including campaigns, audiences, subscribers, segments, and analytics via Rube MCP (Composio). Always search tools first for current schemas.
03 SKILL.md 正文
Mailchimp Automation via Rube MCP
Automate Mailchimp email marketing workflows including campaign creation and sending, audience/list management, subscriber operations, segmentation, and performance analytics through Composio's Mailchimp toolkit.
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Mailchimp connection via
RUBE_MANAGE_CONNECTIONSwith toolkitmailchimp - Always call
RUBE_SEARCH_TOOLSfirst 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.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitmailchimp - If connection is not ACTIVE, follow the returned auth link to complete Mailchimp OAuth
- Confirm connection status shows ACTIVE before running any workflows
Core Workflows
1. Create and Send Email Campaigns
When to use: User wants to create, configure, test, and send an email campaign.
Tool sequence:
MAILCHIMP_GET_LISTS_INFO- List available audiences and get list_id [Prerequisite]MAILCHIMP_ADD_CAMPAIGN- Create a new campaign with type, audience, subject, from name [Required]MAILCHIMP_SET_CAMPAIGN_CONTENT- Set HTML content for the campaign [Required]MAILCHIMP_SEND_TEST_EMAIL- Send preview to reviewers before live send [Optional]MAILCHIMP_SEND_CAMPAIGN- Send the campaign immediately [Required]MAILCHIMP_SCHEDULE_CAMPAIGN- Schedule for future delivery instead of immediate send [Optional]
Key parameters for MAILCHIMP_ADD_CAMPAIGN:
type: "regular", "plaintext", "rss", or "variate" (required)recipients__list__id: Audience/list ID for recipientssettings__subject__line: Email subject linesettings__from__name: Sender display namesettings__reply__to: Reply-to email address (required for sending)settings__title: Internal campaign titlesettings__preview__text: Preview text shown in inbox
Key parameters for MAILCHIMP_SET_CAMPAIGN_CONTENT:
campaign_id: Campaign ID from creation step (required)html: Raw HTML content for the emailplain_text: Plain-text version (auto-generated if omitted)template__id: Use a pre-built template instead of raw HTML
Pitfalls:
MAILCHIMP_SEND_CAMPAIGNis irreversible; always send a test email first and get explicit user approval- Campaign must be in "save" (draft) status with valid audience, subject, from name, verified email, and content before sending
MAILCHIMP_SCHEDULE_CAMPAIGNrequires a valid future datetime; past timestamps fail- Templates and HTML content must include compliant footer/unsubscribe merge tags
- Mailchimp uses double-underscore notation for nested params (e.g.,
settings__subject__line)
2. Manage Audiences and Subscribers
When to use: User wants to view audiences, list subscribers, or check subscriber details.
Tool sequence:
MAILCHIMP_GET_LISTS_INFO- List all audiences with member counts [Required]MAILCHIMP_GET_LIST_INFO- Get details for a specific audience [Optional]MAILCHIMP_LIST_MEMBERS_INFO- List members with status filter and pagination [Required]MAILCHIMP_SEARCH_MEMBERS- Search by email or name across lists [Optional]MAILCHIMP_GET_MEMBER_INFO- Get detailed profile for a specific subscriber [Optional]MAILCHIMP_LIST_SEGMENTS- List segments within an audience [Optional]
Key parameters for MAILCHIMP_LIST_MEMBERS_INFO:
list_id: Audience ID (required)status: "subscribed", "unsubscribed", "cleaned", "pending", "transactional", "archived"count: Records per page (default 10, max 1000)offset: Pagination offset (default 0)sort_field: "timestamp_opt", "timestamp_signup", or "last_changed"fields: Comma-separated list to limit response size
Pitfalls:
stats.avg_open_rateandstats.avg_click_rateare 0-1 fractions, NOT 0-100 percentages- Always use
status="subscribed"to filter active subscribers; omitting returns all statuses - Must paginate using
countandoffsetuntil collected members matchtotal_items - Large list responses may be truncated; data is under
response.data.members
3. Add and Update Subscribers
When to use: User wants to add new subscribers, update existing ones, or bulk-manage list membership.
Tool sequence:
MAILCHIMP_GET_LIST_INFO- Validate target audience exists [Prerequisite]MAILCHIMP_SEARCH_MEMBERS- Check if contact already exists [Optional]MAILCHIMP_ADD_OR_UPDATE_LIST_MEMBER- Upsert subscriber (create or update) [Required]MAILCHIMP_ADD_MEMBER_TO_LIST- Add new subscriber (create only) [Optional]MAILCHIMP_BATCH_ADD_OR_REMOVE_MEMBERS- Bulk manage segment membership [Optional]
Key parameters for MAILCHIMP_ADD_OR_UPDATE_LIST_MEMBER:
list_id: Audience ID (required)subscriber_hash: MD5 hash of lowercase email (required)email_address: Subscriber email (required)status_if_new: Status for new subscribers: "subscribed", "pending", etc. (required)status: Status for existing subscribersmerge_fields: Object with merge tag keys (e.g.,{"FNAME": "John", "LNAME": "Doe"})tags: Array of tag strings
Key parameters for MAILCHIMP_ADD_MEMBER_TO_LIST:
list_id: Audience ID (required)email_address: Subscriber email (required)status: "subscribed", "pending", "unsubscribed", "cleaned", "transactional" (required)
Pitfalls:
subscriber_hashmust be MD5 of the lowercase email; incorrect casing causes 404s or duplicates- Use
MAILCHIMP_ADD_OR_UPDATE_LIST_MEMBER(upsert) instead ofMAILCHIMP_ADD_MEMBER_TO_LISTto avoid duplicate errors status_if_newdetermines status only for new contacts; existing contacts usestatus- Use
skip_merge_validation: trueto bypass required merge field validation MAILCHIMP_BATCH_ADD_OR_REMOVE_MEMBERSmanages static segment membership, not list membership
4. View Campaign Reports and Analytics
When to use: User wants to review campaign performance, open rates, click rates, or subscriber engagement.
Tool sequence:
MAILCHIMP_LIST_CAMPAIGNS- List sent campaigns with report summaries [Required]MAILCHIMP_SEARCH_CAMPAIGNS- Find campaigns by name, subject, or content [Optional]MAILCHIMP_GET_CAMPAIGN_REPORT- Get detailed performance report for a campaign [Required]MAILCHIMP_LIST_CAMPAIGN_REPORTS- Bulk fetch reports across multiple campaigns [Optional]MAILCHIMP_LIST_CAMPAIGN_DETAILS- Get link-level click statistics [Optional]MAILCHIMP_GET_CAMPAIGN_LINK_DETAILS- Drill into specific link click data [Optional]MAILCHIMP_LIST_CLICKED_LINK_SUBSCRIBERS- See who clicked a specific link [Optional]MAILCHIMP_GET_SUBSCRIBER_EMAIL_ACTIVITY- Get per-subscriber campaign activity [Optional]MAILCHIMP_GET_CAMPAIGN_CONTENT- Retrieve campaign HTML content [Optional]
Key parameters for MAILCHIMP_LIST_CAMPAIGNS:
status: "save", "paused", "schedule", "sending", "sent"count/offset: Pagination (default 10, max 1000)since_send_time/before_send_time: ISO 8601 date range filtersort_field: "create_time" or "send_time"fields: Limit response fields for performance
Key parameters for MAILCHIMP_GET_CAMPAIGN_REPORT:
campaign_id: Campaign ID (required)- Returns: opens, clicks, bounces, unsubscribes, timeseries, industry_stats
Pitfalls:
MAILCHIMP_LIST_CAMPAIGNSonly returns high-levelreport_summary; useMAILCHIMP_GET_CAMPAIGN_REPORTfor detailed metrics- Draft/unsent campaigns lack meaningful report data
- When using
fieldsparameter on LIST_CAMPAIGNS, explicitly requestsend_timeandreport_summarysubfields - Pagination defaults are low (10 records); iterate with
countandoffsetuntiltotal_itemsis covered send_timeis ISO 8601 with timezone; parse carefully
Common Patterns
ID Resolution
Always resolve names to IDs before operations:
- Audience name -> list_id:
MAILCHIMP_GET_LISTS_INFOand match by name - Subscriber email -> subscriber_hash: Compute MD5 of lowercase email in code
- Campaign name -> campaign_id:
MAILCHIMP_SEARCH_CAMPAIGNSwith query - Segment name -> segment_id:
MAILCHIMP_LIST_SEGMENTSwith list_id
Pagination
Mailchimp uses offset-based pagination:
- Use
count(page size, max 1000) andoffset(skip N records) - Continue until collected records match
total_itemsfrom the response - Default
countis 10; always set explicitly for bulk operations - Search endpoints max at 10 pages (300 results for 30/page)
Subscriber Hash
Many endpoints require subscriber_hash (MD5 of lowercase email):
import hashlib
subscriber_hash = hashlib.md5(email.lower().encode()).hexdigest()
Known Pitfalls
ID Formats
list_id(audience ID) is a short alphanumeric string (e.g., "abc123def4")campaign_idis an alphanumeric stringsubscriber_hashis an MD5 hex string (32 characters)- Segment IDs are integers
Rate Limits
- Mailchimp enforces API rate limits; use batching for bulk subscriber operations
- High-volume use of GET_MEMBER_INFO and ADD_OR_UPDATE_LIST_MEMBER can trigger throttling
- Use
MAILCHIMP_BATCH_ADD_OR_REMOVE_MEMBERSfor bulk segment operations
Parameter Quirks
- Nested parameters use double-underscore notation:
settings__subject__line,recipients__list__id avg_open_rateandavg_click_rateare 0-1 fractions, not percentagesstatus_if_newonly applies to new contacts in upsert operationssubscriber_hashmust be MD5 of lowercase email; wrong casing creates phantom records- Campaign
typeis required for creation; most common is "regular" MAILCHIMP_SEND_CAMPAIGNreturns HTTP 204 on success (no body)
Content and Compliance
- Campaign HTML must include unsubscribe link and physical address (merge tags)
- Content must be set via
MAILCHIMP_SET_CAMPAIGN_CONTENTbefore sending - Test emails require campaign to have content already set
Quick Reference
| Task | Tool Slug | Key Params |
|---|---|---|
| List audiences | MAILCHIMP_GET_LISTS_INFO |
count, offset |
| Get audience details | MAILCHIMP_GET_LIST_INFO |
list_id |
| Create campaign | MAILCHIMP_ADD_CAMPAIGN |
type, recipients__list__id, settings__subject__line |
| Set campaign content | MAILCHIMP_SET_CAMPAIGN_CONTENT |
campaign_id, html |
| Send test email | MAILCHIMP_SEND_TEST_EMAIL |
campaign_id, test_emails |
| Send campaign | MAILCHIMP_SEND_CAMPAIGN |
campaign_id |
| Schedule campaign | MAILCHIMP_SCHEDULE_CAMPAIGN |
campaign_id, schedule_time |
| Get campaign info | MAILCHIMP_GET_CAMPAIGN_INFO |
campaign_id |
| Search campaigns | MAILCHIMP_SEARCH_CAMPAIGNS |
query |
| List campaigns | MAILCHIMP_LIST_CAMPAIGNS |
status, count, offset |
| Replicate campaign | MAILCHIMP_REPLICATE_CAMPAIGN |
campaign_id |
| List subscribers | MAILCHIMP_LIST_MEMBERS_INFO |
list_id, status, count, offset |
| Search members | MAILCHIMP_SEARCH_MEMBERS |
query, list_id |
| Get member info | MAILCHIMP_GET_MEMBER_INFO |
list_id, subscriber_hash |
| Add subscriber | MAILCHIMP_ADD_MEMBER_TO_LIST |
list_id, email_address, status |
| Upsert subscriber | MAILCHIMP_ADD_OR_UPDATE_LIST_MEMBER |
list_id, subscriber_hash, email_address, status_if_new |
| Batch members | MAILCHIMP_BATCH_ADD_OR_REMOVE_MEMBERS |
list_id, segment_id |
| List segments | MAILCHIMP_LIST_SEGMENTS |
list_id |
| Campaign report | MAILCHIMP_GET_CAMPAIGN_REPORT |
campaign_id |
| All reports | MAILCHIMP_LIST_CAMPAIGN_REPORTS |
count, offset |
| Link click details | MAILCHIMP_LIST_CAMPAIGN_DETAILS |
campaign_id, count |
| Subscriber activity | MAILCHIMP_GET_SUBSCRIBER_EMAIL_ACTIVITY |
campaign_id, subscriber_hash |
| Member recent activity | MAILCHIMP_VIEW_RECENT_ACTIVITY |
list_id, subscriber_hash |
| Campaign content | MAILCHIMP_GET_CAMPAIGN_CONTENT |
campaign_id |
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
04 同仓库更多 Skills
vercel-sandbox
Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include "Vercel Sandbox browser", "microVM Chrome", "agent-browser in sandbox", "browser automation on Vercel", or any task requiring Chrome in a Vercel Sandbox.
slack
Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include "check my Slack", "what channels have unreads", "send a message to", "search Slack for", "extract from Slack", "find who said", or any task requiring programmatic Slack interaction.
electron
Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.
dogfood
Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.
agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
shadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", "switch to --preset", and for building a design system or applying a DESIGN.md or brand spec to shadcn/ui.