Gleap AI agents can use Rootly through Composio, for teams that manage incidents in Rootly and hear from affected customers in Gleap. A custom agent can read an incident’s status for the support team, add what customers report to the incident and check the follow-up action items after it is resolved.
What a Gleap agent can do in Rootly
- Status for support: Get Incident Details returns the incident’s status, severity and summary, so the teammate on a Gleap ticket can tell the customer where things stand.
- Customer impact on the incident: Update Incident adds fields such as the number of related Gleap reports to the incident, so responders see the customer side.
- Follow-ups after the incident: List Action Items and Get Action Item Details show the post-incident tasks, for example the fix a customer is waiting for.
- Kept small on purpose: the toolkit has six actions, and the two delete actions are easy to switch off.
Example: an outage with a long tail of tickets
After an outage, forty customers have open Gleap tickets asking whether their data synced. A teammate asks the agent on one ticket to check Rootly. The agent reads the incident, sees it is resolved with an action item to backfill missing syncs and posts the status and the action item on the ticket. The support lead decides what to tell the forty customers and when.
How to connect Rootly
- In Gleap, open AI & Automation, then Agents, and select the custom agent that should use Rootly, or click Create agent.
- Under Tools, click Add tool, search for “Rootly” and select it.
- Enter your Rootly API key and any other details the form asks for, then click Connect Rootly.
- Open the Rootly tool and switch off Delete Incident and Delete Action Item, and Update Incident too if the agent should only read.
- Publish the agent and test it in chat before you turn on a trigger.
Custom agents are on the Team, Pro and Enterprise plans. Kai Support can use connected apps as tools on Team, Pro and Enterprise.
FAQ
Does Gleap integrate with Rootly?
Yes. Gleap AI agents use Rootly through Composio’s Rootly toolkit, authenticated with a Rootly API key. The agent reads and updates incidents while it runs; Rootly incidents do not appear in Gleap automatically.
What can a Gleap AI agent do in Rootly?
It can read an incident, update its fields, list and read action items, and delete incidents or action items. The toolkit has no action for listing incidents or declaring new ones, so the agent works with incidents your team gives it or that it finds through linked context.
Which Gleap plan includes the Rootly integration?
Custom agents that use Rootly are part of the Team, Pro and Enterprise plans, and Kai Support can use connected apps as tools in its customer conversations on Team, Pro and Enterprise. The Rootly API key’s permissions decide what the agent may change. AI usage is billed separately; see pricing.
How does the agent find the right incident?
Get Incident Details needs an incident ID, so include the ID or link in the ticket, a pinned note or the agent’s instructions during an incident. The agent then reads it directly instead of guessing.
