Connect Customer.io to Your AI Agent

Turn supplied customer data into a precise profile update or event submission.

7 tools Custom credential

Try a Customer.io Task

Copy a prompt into your agent with the oo Skill installed. Add your page links and source notes before running it.

oo Skill Customer.io

Apply supplied customer attributes

Identify or update a customer using explicit profile values.

/oo Customer.io: Identify Customer.io customer [identifier] with these final attributes [attributes]. Check the supplied identifier and attribute names for consistency, then submit only these values and report the acknowledgment.

Record a chosen lifecycle event

Submit an event with clear identity, timing and data.

/oo Customer.io: Record Customer.io event [event name] for [customer identifier or anonymous ID], with data [data], timestamp [timestamp] and event ID [event ID, if used]. Use the matching customer or anonymous event operation and report acceptance without claiming a downstream campaign completed.

Start Working with Customer.io

Install OOMOL

Set up oo CLI and the oo Skill in your agent.
Install OOMOL →
Connect Customer.io

Connect with your Customer.io Track site ID and API key.
Connect Customer.io →
Give Your Agent a Task

Use /oo with the pages to read, the changes to make, and where to save the result.
Connection Guide →

Choose Your Agent

Codex Claude Code Cursor Hermes

Use the credentials for the intended workspace and confirm customer identifiers and attribute names.
Profile and event submissions can activate existing Customer.io workflows. Confirm the intended event and profile effects.
Suppression deletes the customer profile and prevents that identifier from being recreated until unsuppressed. Merging retains the primary profile and deletes the secondary.

Customer.io Tools

Identify customers and submit customer or anonymous events through Customer.io Track. The connection also supports explicit suppression and merge operations; it does not read profiles, campaign analytics or message history.

Customer identity and state

Submit attributes, delete and suppress a customer identifier, or merge profiles while retaining the primary.

Lifecycle events

Record events for known or anonymous identities.

7 tools

Identify Customer

Add or update a Customer.io person through the Track API.

customerio.identify_customer

Track Customer Event

Track an event associated with an identified Customer.io person.

customerio.track_customer_event

Track Anonymous Event

Track an event for an anonymous person in Customer.io.

customerio.track_anonymous_event

Delete Customer

Delete a Customer.io person and their information through the Track API.

customerio.delete_customer

Suppress Customer

Delete and suppress a Customer.io person identifier so it cannot be re-added until unsuppressed.

customerio.suppress_customer

Unsuppress Customer

Unsuppress a Customer.io person identifier so a new profile can be created later.

customerio.unsuppress_customer

Merge Customers

Merge two Customer.io people, keeping the primary profile and deleting the secondary profile.

customerio.merge_customers

Frequently Asked Questions

Which identifier should I supply?

Use the customer identifier convention already used in your workspace. Anonymous events require an anonymous ID rather than a customer identifier.

Can I record an event that occurred earlier?

Yes, supply the event timestamp and data explicitly. Use your intended event ID when your workflow relies on one.

Can I check the customer profile afterward?

The included Track operations return acknowledgments and do not read profiles. Verify the resulting profile or workflow in Customer.io.