Gleap AI agents can use PagerDuty through Composio, for engineering teams that run incident response in PagerDuty while customers report problems through Gleap. A custom agent can tell support whether an incident is already open, name who is on call and add what customers report to the incident, and Kai Code can read incident details while it works on a fix.
What a Gleap agent can do in PagerDuty
- Is there an incident already: Fetch incident list shows open incidents for a service, so support can tell customers the team knows about the problem.
- Customer impact on the incident: Post incident note using id adds a note with how many Gleap reports arrived and what customers see, so responders work from current numbers.
- Who to talk to: Retrieve oncall list names the engineer on call for the affected service, for the teammate on the Gleap ticket.
- Opening an incident on request: Create incident record opens a PagerDuty incident when a teammate decides that customer reports point to an outage.
Example: a login outage reported by customers first
On a Sunday morning, customers start reporting through the Gleap widget that they cannot log in. A teammate asks the agent on one of the tickets to check PagerDuty. The agent finds no open incident for the auth service, names the on-call engineer and summarizes eight similar Gleap reports. The teammate asks the agent to open an incident with that summary, and the on-call engineer takes it from there.
How to connect PagerDuty
- In Gleap, open AI & Automation, then Agents, and select the custom agent that should use PagerDuty, or click Create agent.
- Under Tools, click Add tool, search for “PagerDuty” and select it.
- Click Connect PagerDuty and follow the authorization Gleap shows: approve access in the PagerDuty sign-in window, or enter a PagerDuty API key if the form asks for one.
- Open the PagerDuty tool and switch off every action the agent should not use, such as the delete actions, service and escalation policy changes and incident workflow edits.
- Publish the agent and test it in chat before you turn on a trigger. For Kai Code, add PagerDuty under Settings, MCP instead.
Kai Code is on Team, Pro and Enterprise, and Kai Support can use connected apps as tools on the same plans. Custom agents are on the Team, Pro and Enterprise plans.
FAQ
Does Gleap integrate with PagerDuty?
Yes. Custom agents, Kai Support and Kai Code use PagerDuty through Composio’s PagerDuty toolkit, which supports OAuth and API keys. They call PagerDuty while they run; Gleap does not receive PagerDuty alerts or page anyone on its own.
What can a Gleap AI agent do in PagerDuty?
It can list and read incidents, alerts, notes, on-call schedules, services and analytics, create incidents, notes and status updates, and manage services, rules, workflows and escalation policies. Creating incidents pages people, so keep that step with a teammate’s decision.
Which Gleap plan includes the PagerDuty integration?
Kai Code and Kai Support’s investigations can use PagerDuty on Team, Pro and Enterprise, and Kai Support can use connected apps as tools in its customer conversations on the same plans. Custom agents that use PagerDuty are part of the Team, Pro and Enterprise plans. The PagerDuty user or key you connect decides which services and incidents the agents see. AI usage is billed separately; see pricing.
Can the agent post status updates for customers?
Post incident status update publishes an update on the incident in PagerDuty, which can notify its subscribers. Keep customer-facing wording with your incident lead, and let the agent draft it on the Gleap ticket for review first.
