A Gleap custom agent can identify people, track events and read messages, segments and broadcasts in Customer.io through Composio. It helps product-led teams that run lifecycle messaging in Customer.io and support in Gleap.
What a Gleap agent can do in Customer.io
- Send support context to journeys: Track Event records an event such as a reported bug, so campaigns can react to it.
- Update the profile: Identify Person sets attributes such as support tier or company plan on the person.
- Check what was sent: Get Messages lists messages sent from the workspace in a time window, useful when a customer says an email never arrived.
- Check segment membership: Get Segment Membership shows who is in a segment, for example the onboarding segment a confused customer belongs to.
Example: A welcome email that never arrived
A new customer tells Gleap support they never got the welcome email with their setup link. The teammate asks the agent to check. The agent looks up recent messages in Customer.io for the customer’s signup window and reports whether a welcome email was sent and delivered. The teammate resends the link from the product or escalates a delivery problem to the lifecycle team.
How to connect Customer.io
- In Gleap, open AI & Automation > Agents and select a custom agent, or create one.
- In its Tools section, click Add tool and search for “Customer.io”.
- Pick Customer.io under More integrations and click Connect Customer.io.
- Enter the Customer.io API credentials Gleap asks for and connect.
- Open the new Customer.io tool and switch off every action the agent does not need, such as Suppress Customer Profile or Trigger Broadcast.
- Tell the agent in its instructions when to use Customer.io, then test it in chat.
Custom agents are included in the Team, Pro and Enterprise plans. Kai Support can use connected apps as tools on Team, Pro and Enterprise. Kai Code, also on those plans, can use Customer.io in coding sessions once you add it under Settings > MCP in Kai Code.
FAQ
Does Gleap integrate with Customer.io?
Yes, through Composio. A Gleap custom agent can identify people, track events, page and screen views, read messages, segments, newsletters and triggers and handle unsubscribes. It acts only during an agent run.
What can a Gleap AI agent do in Customer.io?
It feeds support events and attributes into Customer.io and answers delivery questions with message data. Lifecycle messaging itself stays with your team in Customer.io.
Which Gleap plan includes the Customer.io integration?
Kai Support and Kai Code can use the Customer.io toolkit on Team, Pro and Enterprise; custom agents that use it are on Team, Pro and Enterprise. Kai Support answers customers, so switch on only actions that are safe in a customer conversation. Some actions need Customer.io’s Track API credentials and others its App API key, so have both at hand. AI usage is billed separately; see pricing.
Why switch off Suppress Customer Profile and Trigger Broadcast?
Suppress Customer Profile deletes the person and blocks them from being added again, and Trigger Broadcast sends messages to an audience. Both are hard to undo, so keep them with a person.
