FlowRunner
PricingContact
Theme
Start Free

Klaviyo

Email Marketing

Run Klaviyo email and SMS marketing from your workflows. Agents upsert profiles and manage consent, lists, and segments, track custom events, query time-bucketed metric aggregates for revenue reporting, send campaigns, and handle suppression and data privacy requests.

43 actions API key available
Klaviyo website ↗ Platform Documentation ↗ Capability data verified 2026-07-22
The quarterly winback push begins on schedule
Get Segment Profiles pulls the lapsed-customer segment as it stands today
Get Campaign inspects the draft winback campaign's audiences and send strategy
Get Campaign Recipient Estimation returns the audience size Klaviyo computed
The estimate is compared against the segment's expected size, because a filter typo sends to the wrong thousands
The lifecycle marketer confirms the audience and the offer, and gives the go
Send Campaign triggers the send job to the configured audiences
The send confirmation posts to the marketing channel, and a follow-up flow reports revenue from Query Metric Aggregates

What This Integration Enables

Klaviyo works on a simple loop: events come in, segments update, messages go out, revenue gets attributed. Most teams run that loop half-manually and feel it in stale segments and unreported revenue. This connector puts the whole loop under agent control. FlowRunner agents upsert profiles and manage the full consent surface, subscribe, unsubscribe, suppress, unsuppress, as explicit operations. They track custom events that trigger flows and power segments, query time-bucketed metric aggregates for revenue reporting, send campaigns, render templates, flip automation flows between Draft and Live, and execute irreversible privacy deletions when the law requires it. The consent operations deserve the emphasis Klaviyo's API gives them. Adding a profile to a list and recording SUBSCRIBED consent are different acts with different legal weight, and this connector keeps them distinct, so your automation is precise about the thing regulators are precise about. The acts that cannot be taken back route through FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) gates.

Without FlowRunner

Profiles updated by import Customer data reaches Klaviyo through periodic CSVs, so flows fire on stale state
Consent handled by folklore Who is suppressed, who unsubscribed, and who double opted in lives in tribal memory
Revenue reporting by screenshot Attribution numbers leave Klaviyo when someone remembers to copy them

With FlowRunner

Profiles upserted as events happen Orders and signups update profiles and fire events within minutes, no import step
Consent as recorded state Subscribes, unsubscribes, and suppressions are explicit operations with an audit trail in the flow
Metrics queried like a database Time-bucketed aggregates flow into weekly reports and dashboards automatically

Use Case Scenarios

The order stream that feeds everything

Every [Shopify](/integrations/shopify) order fires Create or Update Profile for the customer and Create Event for Placed Order with value and items. Those events trigger Klaviyo flows, refresh segments, and accumulate into the metrics behind revenue attribution. Contact exports from [Google Sheets](/integrations/google-sheets) sync through the same upsert path, with Subscribe Profiles recording proper consent, honoring double opt-in where lists require it. One pipeline, and every downstream Klaviyo feature runs on live data.

The revenue report that writes itself

Weekly, Query Metric Aggregates runs against Placed Order: revenue and unique buyers by day, grouped by message, so campaign and flow attribution comes back as data instead of dashboard archaeology. The agent writes the series to the reporting sheet, diffs against the prior period, and posts the digest to [Slack](/integrations/slack) with anomalies flagged. The Monday meeting starts from numbers pulled that morning.

Suppression hygiene and privacy requests, handled precisely

Bounce complaints and internal do-not-contact requests run through Suppress Profiles, which stops email without touching consent records; a later win-back approval reverses it with Unsuppress Profiles. When a verified GDPR erasure request arrives, the agent locates the profile with Get Profile by Email, stages the request, and, after the privacy owner confirms the identity match, submits Request Profile Deletion. Three different "stop emailing me" situations, three different operations, no blunt instruments.

Human-in-Loop Highlight

Update Flow Status is the quietest dangerous operation in this connector. Setting a flow to Live does not send one campaign; it switches on an automation that messages every profile entering it, indefinitely, until someone notices the wrong discount code or the broken link and turns it off. So flow launches in FlowRunner end with a person: the agent verifies the flow's trigger and status with Get Flow, renders the templates involved with Render Template for review, and the lifecycle marketer flips the switch knowingly. Request Profile Deletion sits behind the same discipline for the opposite reason: once processed, the profile, its events, and its consent history are permanently and irreversibly gone, so the identity confirmation belongs to the privacy owner, not to a string match.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via preferred channel
Human decides
Agent resumes with decision

Agent Capabilities

43 actions

Profiles

6
  • List Profiles Pages through profiles with JSON:API filters and sorting. The bulk read for audits and syncs.
  • Get Profile Retrieves a profile by ID, optionally with subscriptions and predictive analytics like CLV and churn risk.
  • Get Profile by Email Finds a profile by exact email, or null when absent. The lookup step before targeted operations.
  • Create Profile Creates a profile from at least one identifier. Fails on duplicates; syncs use the upsert instead.
  • Update Profile Changes provided fields on a profile, merging custom properties.
  • Create or Update Profile Upserts by identifier. The default write for every external sync.

Consent and Suppression

4
  • Suppress Profiles Blocks email sends to the given addresses without changing consent. The do-not-contact instrument.
  • Unsuppress Profiles Removes suppressions so sends resume; recorded unsubscribes stay untouched.
  • Subscribe Profiles Records explicit SUBSCRIBED consent for email or SMS, honoring double opt-in, optionally adding to a list.
  • Unsubscribe Profiles Records UNSUBSCRIBED consent for email or SMS, optionally scoped to a list.

Lists

8
  • List Lists Pages through the account's lists with filters.
  • Get List Retrieves a list with its opt-in process and optional profile count.
  • Create List Creates a list for use with subscriptions and memberships.
  • Update List Renames a list; membership is managed by the dedicated operations.
  • Delete List Permanently deletes a list and its memberships, not its profiles. Cannot be undone.
  • Add Profiles to List Adds up to 1000 profiles by ID without recording consent. For internal grouping, not marketing opt-in.
  • Remove Profiles from List Removes up to 1000 profiles from a list, leaving profiles and consent intact.
  • Get List Profiles Pages through a list's members with profile-level filters.

Segments

3
  • List Segments Pages through segments with filters on activity and name.
  • Get Segment Retrieves a segment with optional live profile count.
  • Get Segment Profiles Pages through a segment's current members. The audience read behind targeted pushes.

Events

3
  • Create Event Tracks a custom event for a profile, auto-creating the metric or profile if new. The trigger fuel for flows and segments.
  • List Events Pages through events, filterable by metric and profile, with related resources.
  • Get Event Retrieves one event with its timestamp and properties.

Metrics

3
  • List Metrics Pages through the account's event types, including integration-created metrics.
  • Get Metric Retrieves a metric's details and source integration.
  • Query Metric Aggregates Runs time-bucketed aggregate queries: counts, revenue, unique profiles, grouped by dimensions. The reporting engine of this page.

Campaigns

5
  • List Campaigns Pages through campaigns per channel with status filters.
  • Get Campaign Retrieves a campaign's audiences, send strategy, and tracking options.
  • Delete Campaign Permanently deletes a campaign; analytics may go with it. Archive in the UI when reporting must survive.
  • Send Campaign Triggers the send job for a configured draft. The step a person releases.
  • Get Campaign Recipient Estimation Returns the computed audience size. The sanity check before every send.

Templates

4
  • List Templates Pages through email templates with name filters.
  • Get Template Retrieves a template's HTML and text content.
  • Create Template Creates a code-editor template with variable placeholders.
  • Render Template Resolves a template against context variables into final HTML and text. The preview step before launches.

Flows

3
  • List Flows Pages through automation flows with status and trigger filters.
  • Get Flow Retrieves a flow's status, trigger type, and archived state.
  • Update Flow Status Switches a flow between Live, Draft, and Manual. Live starts real sends, which is why a person flips it.

Tags

3
  • List Tags Pages through organizational tags.
  • Create Tag Creates a tag for organizing lists, segments, campaigns, and flows.
  • Delete Tag Permanently deletes a tag from the account and every tagged resource.

Data Privacy

1
  • Request Profile Deletion Submits an irreversible GDPR or CCPA deletion of a profile and all its data. Suppression exists for everything short of this.

Frequently Asked Questions

What can FlowRunner do with Klaviyo?

FlowRunner agents can run List Profiles, Get Profile, and Get Profile by Email in Klaviyo, plus 40 more actions.

Does connecting Klaviyo to FlowRunner require OAuth?

No. Klaviyo connects to FlowRunner with an API key, no OAuth flow required.

Can Klaviyo trigger a FlowRunner workflow automatically?

Klaviyo doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Klaviyo

$100 in credits. No card required. Connect in minutes.