Klaviyo Automation

# 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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds

2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `klaviyo`

3. If connection is not ACTIVE, follow the returned auth link to complete Klaviyo authentication

4. 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**:

1. `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**:

1. `KLAVIYO_GET_CAMPAIGNS` - Find campaign to get its ID [Prerequisite]

2. `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**:

1. `KLAVIYO_GET_CAMPAIGN` - Find campaign and its message IDs [Prerequisite]

2. `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**:

1. `KLAVIYO_GET_CAMPAIGN_RELATIONSHIPS_TAGS` - Get tag IDs for a camp