Klaviyo Automation via Rube MCP
Automate Klaviyo email and SMS marketing operations through Composio's Klaviyo toolkit via Rube MCP.
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Klaviyo connection via
RUBE_MANAGE_CONNECTIONS with toolkit klaviyo
- 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.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLS responds
- Call
RUBE_MANAGE_CONNECTIONS with toolkit klaviyo
- If connection is not ACTIVE, follow the returned auth link to complete Klaviyo authentication
- Confirm connection status shows ACTIVE before running any workflows
Core Workflows
1. List and Filter Campaigns
When to use: User wants to browse, search, or filter marketing campaigns
Tool sequence:
KLAVIYO_GET_CAMPAIGNS - List campaigns with channel and status filters [Required]
Key parameters:
channel: Campaign channel - 'email' or 'sms' (required by Klaviyo API)
filter: Additional filter string (e.g., equals(status,"draft"))
sort: Sort field with optional - prefix for descending (e.g., '-created_at', 'name')
page_cursor: Pagination cursor for next page
include_archived: Include archived campaigns (default: false)
Pitfalls:
channel is required; omitting it can produce incomplete or unexpected results
- Pagination is mandatory for full coverage; a single call returns only one page (default ~10)
- Follow
page_cursor until exhausted to get all campaigns
- Status filtering via
filter (e.g., equals(status,"draft")) can return mixed statuses; always validate data[].attributes.status client-side
- Status strings are case-sensitive and can be compound (e.g., 'Cancelled: No Recipients')
- Response shape is nested:
response.data.data with status at data[].attributes.status
2. Get Campaign Details
When to use: User wants detailed information about a specific campaign
Tool sequence:
KLAVIYO_GET_CAMPAIGNS - Find campaign to get its ID [Prerequisite]
KLAVIYO_GET_CAMPAIGN - Retrieve full campaign details [Required]
Key parameters:
campaign_id: Campaign ID string (e.g., '01GDDKASAP8TKDDA2GRZDSVP4H')
include_messages: Include campaign messages in response
include_tags: Include tags in response
Pitfalls:
- Campaign IDs are alphanumeric strings, not numeric
include_messages and include_tags add related data to the response via Klaviyo's include mechanism
- Campaign details include audiences, send strategy, tracking options, and scheduling info
3. Inspect Campaign Messages
When to use: User wants to view the email/SMS content of a campaign
Tool sequence:
KLAVIYO_GET_CAMPAIGN - Find campaign and its message IDs [Prerequisite]
KLAVIYO_GET_CAMPAIGN_MESSAGE - Get message content details [Required]
Key parameters:
id: Message ID string
fields__campaign__message: Sparse fieldset for message attributes (e.g., 'content.subject', 'content.from_email', 'content.body')
fields__campaign: Sparse fieldset for campaign attributes
fields__template: Sparse fieldset for template attributes
include: Related resources to include ('campaign', 'template')
Pitfalls:
- Message IDs are separate from campaign IDs; extract from campaign response
- Sparse fieldset syntax uses dot notation for nested fields: 'content.subject', 'content.from_email'
- Email messages have content fields: subject, preview_text, from_email, from_label, reply_to_email
- SMS messages have content fields: body
- Including 'template' provides the HTML/text content of the email
4. Manage Campaign Tags
When to use: User wants to view tags associated with campaigns for organization
Tool sequence:
KLAVIYO_GET_CAMPAIGN_RELATIONSHIPS_TAGS - Get tag IDs for a campaign [Required]
Key parameters:
Pitfalls:
- Returns only tag IDs, not tag names/details
- Tag IDs can be used with Klaviyo's tag endpoints for full details
- Rate limit: 3/s burst, 60/m steady (stricter than other endpoints)
5. Monitor Campaign Send Jobs
When to use: User wants to check the status of a campaign send operation
Tool sequence:
KLAVIYO_GET_CAMPAIGN_SEND_JOB - Check send job status [Required]
Key parameters:
Pitfalls:
- Send job IDs are returned when a campaign send is initiated
- Job statuses indicate whether the send is queued, in progress, complete, or failed
- Rate limit: 10/s burst, 150/m steady
Common Patterns
Campaign Discovery Pattern
1. Call KLAVIYO_GET_CAMPAIGNS with channel='email'
2. Paginate through all results via page_cursor
3. Filter by status client-side for accuracy
4. Extract campaign IDs for detailed inspection
Sparse Fieldset Pattern
Klaviyo supports sparse fieldsets to reduce response size:
fields__campaign__message=['content.subject', 'content.from_email', 'send_times']
fields__campaign=['name', 'status', 'send_time']
fields__template=['name', 'html', 'text']
Pagination
- Klaviyo uses cursor-based pagination
- Check response for
page_cursor in the pagination metadata
- Pass cursor as
page_cursor in next request
- Default page size is ~10 campaigns
- Continue until no more cursor is returned
Filter Syntax
- equals(status,"draft") - Campaigns in draft status
- equals(name,"Newsletter") - Campaign named "Newsletter"
- greater-than(created_at,"2024-01-01T00:00:00Z") - Created after date
Known Pitfalls
API Version:
- Klaviyo API uses versioned endpoints (e.g., v2024-07-15)
- Response schemas may change between API versions
- Tool responses follow the version configured in the Composio integration
Response Nesting:
- Data is nested:
response.data.data[].attributes
- Campaign status at
data[].attributes.status
- Mis-parsing the nesting yields empty or incorrect results
- Always navigate through the full path defensively
Rate Limits:
- Burst: 10/s (3/s for tag endpoints)
- Steady: 150/m (60/m for tag endpoints)
- Required scope: campaigns:read
- Implement backoff on 429 responses
Status Values:
- Status strings are case-sensitive
- Compound statuses exist (e.g., 'Cancelled: No Recipients')
- Server-side filtering may return mixed statuses; always validate client-side
Quick Reference
| Task |
Tool Slug |
Key Params |
| List campaigns |
KLAVIYO_GET_CAMPAIGNS |
channel, filter, sort, page_cursor |
| Get campaign details |
KLAVIYO_GET_CAMPAIGN |
campaign_id, include_messages, include_tags |
| Get campaign message |
KLAVIYO_GET_CAMPAIGN_MESSAGE |
id, fields__campaign__message |
| Get campaign tags |
KLAVIYO_GET_CAMPAIGN_RELATIONSHIPS_TAGS |
id |
| Get send job status |
KLAVIYO_GET_CAMPAIGN_SEND_JOB |
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.
Source: sickn33/agentic-awesome-skills → skills/klaviyo-automation/SKILL.md
Also appears in: sickn33/agentic-awesome-skills/plugins/agentic-awesome-skills/skills/klaviyo-automation/SKILL.md, sickn33/agentic-awesome-skills/plugins/agentic-awesome-skills-claude/skills/klaviyo-automation/SKILL.md
1---2name: klaviyo-automation3description: "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."4category: mcp-and-integrations5source_repo: sickn33/agentic-awesome-skills6source_path: "skills/klaviyo-automation/SKILL.md"7source_url: https://github.com/sickn33/agentic-awesome-skills/blob/HEAD/skills/klaviyo-automation/SKILL.md8metadata:9 source: https://skillmd.com/skills/sickn33/klaviyo-automation10---111213# Klaviyo Automation via Rube MCP1415Automate Klaviyo email and SMS marketing operations through Composio's Klaviyo toolkit via Rube MCP.1617## Prerequisites1819- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)20- Active Klaviyo connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `klaviyo`21- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas2223## Setup2425**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.2627281. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds292. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `klaviyo`303. If connection is not ACTIVE, follow the returned auth link to complete Klaviyo authentication314. Confirm connection status shows ACTIVE before running any workflows3233## Core Workflows3435### 1. List and Filter Campaigns3637**When to use**: User wants to browse, search, or filter marketing campaigns3839**Tool sequence**:401. `KLAVIYO_GET_CAMPAIGNS` - List campaigns with channel and status filters [Required]4142**Key parameters**:43- `channel`: Campaign channel - 'email' or 'sms' (required by Klaviyo API)44- `filter`: Additional filter string (e.g., `equals(status,"draft")`)45- `sort`: Sort field with optional `-` prefix for descending (e.g., '-created_at', 'name')46- `page_cursor`: Pagination cursor for next page47- `include_archived`: Include archived campaigns (default: false)4849**Pitfalls**:50- `channel` is required; omitting it can produce incomplete or unexpected results51- Pagination is mandatory for full coverage; a single call returns only one page (default ~10)52- Follow `page_cursor` until exhausted to get all campaigns53- Status filtering via `filter` (e.g., `equals(status,"draft")`) can return mixed statuses; always validate `data[].attributes.status` client-side54- Status strings are case-sensitive and can be compound (e.g., 'Cancelled: No Recipients')55- Response shape is nested: `response.data.data` with status at `data[].attributes.status`5657### 2. Get Campaign Details5859**When to use**: User wants detailed information about a specific campaign6061**Tool sequence**:621. `KLAVIYO_GET_CAMPAIGNS` - Find campaign to get its ID [Prerequisite]632. `KLAVIYO_GET_CAMPAIGN` - Retrieve full campaign details [Required]6465**Key parameters**:66- `campaign_id`: Campaign ID string (e.g., '01GDDKASAP8TKDDA2GRZDSVP4H')67- `include_messages`: Include campaign messages in response68- `include_tags`: Include tags in response6970**Pitfalls**:71- Campaign IDs are alphanumeric strings, not numeric72- `include_messages` and `include_tags` add related data to the response via Klaviyo's include mechanism73- Campaign details include audiences, send strategy, tracking options, and scheduling info7475### 3. Inspect Campaign Messages7677**When to use**: User wants to view the email/SMS content of a campaign7879**Tool sequence**:801. `KLAVIYO_GET_CAMPAIGN` - Find campaign and its message IDs [Prerequisite]812. `KLAVIYO_GET_CAMPAIGN_MESSAGE` - Get message content details [Required]8283**Key parameters**:84- `id`: Message ID string85- `fields__campaign__message`: Sparse fieldset for message attributes (e.g., 'content.subject', 'content.from_email', 'content.body')86- `fields__campaign`: Sparse fieldset for campaign attributes87- `fields__template`: Sparse fieldset for template attributes88- `include`: Related resources to include ('campaign', 'template')8990**Pitfalls**:91- Message IDs are separate from campaign IDs; extract from campaign response92- Sparse fieldset syntax uses dot notation for nested fields: 'content.subject', 'content.from_email'93- Email messages have content fields: subject, preview_text, from_email, from_label, reply_to_email94- SMS messages have content fields: body95- Including 'template' provides the HTML/text content of the email9697### 4. Manage Campaign Tags9899**When to use**: User wants to view tags associated with campaigns for organization100101**Tool sequence**:1021. `KLAVIYO_GET_CAMPAIGN_RELATIONSHIPS_TAGS` - Get tag IDs for a campaign [Required]103104**Key parameters**:105- `id`: Campaign ID string106107**Pitfalls**:108- Returns only tag IDs, not tag names/details109- Tag IDs can be used with Klaviyo's tag endpoints for full details110- Rate limit: 3/s burst, 60/m steady (stricter than other endpoints)111112### 5. Monitor Campaign Send Jobs113114**When to use**: User wants to check the status of a campaign send operation115116**Tool sequence**:1171. `KLAVIYO_GET_CAMPAIGN_SEND_JOB` - Check send job status [Required]118119**Key parameters**:120- `id`: Send job ID121122**Pitfalls**:123- Send job IDs are returned when a campaign send is initiated124- Job statuses indicate whether the send is queued, in progress, complete, or failed125- Rate limit: 10/s burst, 150/m steady126127## Common Patterns128129### Campaign Discovery Pattern130131```1321. Call KLAVIYO_GET_CAMPAIGNS with channel='email'1332. Paginate through all results via page_cursor1343. Filter by status client-side for accuracy1354. Extract campaign IDs for detailed inspection136```137138### Sparse Fieldset Pattern139140Klaviyo supports sparse fieldsets to reduce response size:141```142fields__campaign__message=['content.subject', 'content.from_email', 'send_times']143fields__campaign=['name', 'status', 'send_time']144fields__template=['name', 'html', 'text']145```146147### Pagination148149- Klaviyo uses cursor-based pagination150- Check response for `page_cursor` in the pagination metadata151- Pass cursor as `page_cursor` in next request152- Default page size is ~10 campaigns153- Continue until no more cursor is returned154155### Filter Syntax156157```158- equals(status,"draft") - Campaigns in draft status159- equals(name,"Newsletter") - Campaign named "Newsletter"160- greater-than(created_at,"2024-01-01T00:00:00Z") - Created after date161```162163## Known Pitfalls164165**API Version**:166- Klaviyo API uses versioned endpoints (e.g., v2024-07-15)167- Response schemas may change between API versions168- Tool responses follow the version configured in the Composio integration169170**Response Nesting**:171- Data is nested: `response.data.data[].attributes`172- Campaign status at `data[].attributes.status`173- Mis-parsing the nesting yields empty or incorrect results174- Always navigate through the full path defensively175176**Rate Limits**:177- Burst: 10/s (3/s for tag endpoints)178- Steady: 150/m (60/m for tag endpoints)179- Required scope: campaigns:read180- Implement backoff on 429 responses181182**Status Values**:183- Status strings are case-sensitive184- Compound statuses exist (e.g., 'Cancelled: No Recipients')185- Server-side filtering may return mixed statuses; always validate client-side186187## Quick Reference188189| Task | Tool Slug | Key Params |190|------|-----------|------------|191| List campaigns | KLAVIYO_GET_CAMPAIGNS | channel, filter, sort, page_cursor |192| Get campaign details | KLAVIYO_GET_CAMPAIGN | campaign_id, include_messages, include_tags |193| Get campaign message | KLAVIYO_GET_CAMPAIGN_MESSAGE | id, fields__campaign__message |194| Get campaign tags | KLAVIYO_GET_CAMPAIGN_RELATIONSHIPS_TAGS | id |195| Get send job status | KLAVIYO_GET_CAMPAIGN_SEND_JOB | id |196197## When to Use198This skill is applicable to execute the workflow or actions described in the overview.199200## Limitations201- Use this skill only when the task clearly matches the scope described above.202- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.203- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.204205---206207**Source:** [`sickn33/agentic-awesome-skills`](https://github.com/sickn33/agentic-awesome-skills) → `skills/klaviyo-automation/SKILL.md`208209**Also appears in:** `sickn33/agentic-awesome-skills/plugins/agentic-awesome-skills/skills/klaviyo-automation/SKILL.md`, `sickn33/agentic-awesome-skills/plugins/agentic-awesome-skills-claude/skills/klaviyo-automation/SKILL.md`