Use metric-aggregates for open rates, click rates, and revenue attribution.
Klaviyo Runner Workflows
Track email campaigns, SMS flows, and marketing automation metrics.
Runner uses Klaviyo through the Composio toolkit for campaign management, flow monitoring, and metric aggregation with JSON:API response handling.
Google SheetsWhat Runner actually does with Klaviyo
This page is tied to the real connector definition inside Runner. The highlights below describe the kinds of actions, safeguards, and workflow patterns the app page represents, not a generic integration directory blurb.
Monitor flow status and campaign performance across channels.
Apply sparse fieldsets to reduce payload and speed up queries.
Backend surface
Composio toolkit powers this connector inside Runner. Backed by the `klaviyo` toolkit in Runner's backend catalog with campaign, flow, and metric operations.
Operational notes
- All responses use JSON:API format — data lives under data[].attributes, not top-level.
- Never paginate events to compute aggregates — use the metric-aggregates endpoint.
Popular workflows with Klaviyo
Real workflow pages where Klaviyo is part of the connected stack. Each workflow shows the trigger, connectors, and outcome.
Triggers and actions
What Runner can do with Klaviyo. These are grounded in the real backend connector definitions, not generic marketing filler.
Check campaign performance
“Show me open rates and click rates for the last three email campaigns.”
Marketing metrics become part of the operating context without switching to Klaviyo.
Monitor flow status
“Which Klaviyo flows are live and which are still in draft?”
Automation status stays visible alongside the rest of the marketing stack.
Check list and segment sizes
“Show me the current size of the VIP segment and the newsletter list.”
Audience sizing becomes part of the workflow for campaign planning.
Use Klaviyo inside a real workflow
Download Runner to connect Klaviyo to the rest of your workflow instead of treating it like another isolated tab.
Runner.