FlowRunner
Pricing
Theme

Customer.io

Email Marketing

Connect AI agents to Customer.io. Agents identify people, track behavioral events, curate manual segments, send transactional email, trigger broadcasts, and pull customer attributes and campaign metrics.

17 actions available
A customer completes an action in another system
Agent upserts the profile with Identify Person
Agent records the behavior with Track Event
Agent reads Get Customer Attributes to confirm the profile is current
Agent enrolls the person with Add To Manual Segment
Marketing channel gets a daily campaign summary
A data-removal request routes for confirmation before Suppress Person runs

What This Integration Enables

An agent can identify a person to create or update their profile, track named events that trigger campaigns and update segments, and track anonymous events for visitors who are not yet known. It curates manual segment membership in bulk, adds up to 1000 people per call, and lists the segments available. This is the core loop Customer.io is built on: keep the profile current, fire the event, let the campaign react. Beyond the loop, the agent sends transactional email from a defined template, triggers API-triggered broadcasts, and reads deeply into the workspace: search people by attribute, return a person's full attribute set, walk their activity timeline, list campaigns, and pull time-series campaign metrics. It also handles hard opt-outs with suppress and unsuppress. Customer.io exposes no event triggers in this integration, so flows start from the systems feeding it: a store, a signup, or a scheduled sweep. The agent is the bridge between the systems where behavior happens and the messaging that responds to it.

Without FlowRunner

Profiles go stale Attributes are set once and never updated as behavior changes
Events untracked Behavior lives in the source system and never reaches messaging
Opt-outs handled loosely Removal requests are processed by hand with no consistent record

With FlowRunner

Profiles upserted Identify Person keeps each profile current on every relevant action
Behavior tracked Track Event fires the signals that drive event-triggered campaigns
Opt-outs enforced Suppress Person deletes the profile and blocks re-adding on request

Use Case Scenarios

Purchase Drives a Campaign

A store fires a new-order event. The agent calls Identify Person to upsert the buyer's profile, then Track Event to record the purchase so an event-triggered campaign can react to it. The profile and the behavior land together, and the campaign starts without a marketer touching it.

New Signup Into Onboarding

A [Google Sheets](/integrations/google-sheets) On New Row detects a new signup. The agent calls Identify Person to add them and Add To Manual Segment to enroll them in an onboarding audience. The new signup is in the right segment the moment the row appears.

Daily Campaign Recap

After Get Campaign Metrics returns performance data, the agent posts a daily campaign summary to the marketing channel with [Slack](/integrations/slack) Send Message To Channel. The team reads sends, opens, and clicks in Slack instead of opening the dashboard.

Human-in-Loop Highlight

Suppress Person is deliberately irreversible in spirit: it deletes the profile and blocks Customer.io from ever re-adding or messaging that identifier again until it is unsuppressed. That is exactly what a data-removal request needs, and exactly why it should not run on a loose match. When the agent is about to suppress a person, it treats the deletion as a [human-in-the-loop](/concepts/human-in-the-loop/) step. It pauses, shows the identifier, the profile it will delete, and the request that prompted it, and routes the decision to a privacy or ops owner through Slack or email. The owner confirms, and the agent suppresses. The owner holds, and the profile stays. The agent handles routine identify and track work; the call that erases a customer gets a human.

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

Agent Capabilities

17 actions

People

4
  • Identify Person Creates a new person or updates an existing one (upsert), identified by email or your internal ID, setting any profile attributes.
  • Delete Person Permanently deletes a person and their profile data. This does not prevent re-adding them later; use Suppress Person for a hard opt-out.
  • Suppress Person Deletes a person's profile and prevents Customer.io from ever re-adding or messaging that identifier until it is unsuppressed. Use for hard opt-outs and data-removal requests.
  • Unsuppress Person Removes the suppression from an identifier, allowing Customer.io to identify and message that person again.

Events

2
  • Track Event Sends a named event for a known person. Events can trigger campaigns, update segments, and appear on the person's activity timeline.
  • Track Anonymous Event Sends a named event not associated with a known person, for anonymous-invite and similar flows.

Segments

3
  • Add To Manual Segment Adds up to 1000 people to a manual segment by their IDs.
  • Remove From Manual Segment Removes up to 1000 people from a manual segment by their IDs.
  • List Segments Lists all segments in the workspace with their ID, name, description, type, and state.

Messaging

3
  • Send Transactional Email Sends a transactional email using a defined template, personalized with message data, identifying the recipient by ID or email.
  • Trigger Broadcast Triggers an API-triggered broadcast campaign to its configured audience or specified recipients.
  • List Transactional Messages Lists the transactional message templates defined in the workspace.

Reporting

5
  • Search Customers Searches people by attribute, with a simple name-value pair or a raw filter object for advanced queries.
  • Get Customer Attributes Returns a person's full attribute set, the last-updated timestamp per attribute, and their devices and unsubscribe state.
  • List Customer Activities Returns a person's activity timeline: events, attribute changes, page views, and messages sent, opened, or clicked.
  • List Campaigns Lists all campaigns with their metadata, including type, state, and tags.
  • Get Campaign Metrics Returns time-series performance metrics for a campaign: sent, delivered, opened, clicked, converted, bounced, and unsubscribed.

Start building with Customer.io

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