Gleap AI agents can send data to Honeybadger through Composio, for teams that track errors and uptime in Honeybadger and receive bug reports from customers in Gleap. The toolkit only reports to Honeybadger, so a custom agent can log customer reports as events or exceptions and send check-ins, but it cannot look up the errors Honeybadger already has.
What a Gleap agent can do in Honeybadger
- Customer reports next to your errors: Report Event sends a structured event to Honeybadger Insights for a Gleap bug report, so you can chart customer reports next to the errors your app sends.
- A report as an exception: Report Exception files a notice in Honeybadger with the context from a Gleap bug report, when your team wants the report in the same error list.
- Watching your scheduled agents: Report Check-In pings a Honeybadger check-in after a scheduled Gleap agent finishes its run, so Honeybadger alerts you if the runs stop.
- Deployments on the timeline: Report Deployment records a deployment in Honeybadger, for example when your team wants a hotfix marked there.
Example: charting customer reports
A team wants to see whether customer bug reports rise after releases. A custom agent runs every hour on a schedule, finds the new Gleap bug reports with the Gleap tool and sends an Insights event for each with the page, browser and app area. In Honeybadger, the team charts those events next to exceptions and deployments. After a release, an engineer sees reports about the editor rise within an hour and decides to look at the latest change.
How to connect Honeybadger
- In Gleap, open AI & Automation, then Agents, and select the custom agent that should use Honeybadger, or click Create agent.
- Under Tools, click Add tool, search for “Honeybadger” and select it.
- Enter your Honeybadger API key and any other details the form asks for, then click Connect Honeybadger.
- Open the Honeybadger tool and switch off the actions the agent does not need, such as Upload Source Map and Upload File to S3.
- Publish the agent and test it in chat before you turn on a trigger.
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 Honeybadger?
Yes, in one direction. Gleap AI agents use Composio’s Honeybadger toolkit to send events, exceptions, check-ins, deployments and source maps to Honeybadger with your API key. The toolkit has no actions that read errors back.
What can a Gleap AI agent do in Honeybadger?
It can report check-ins with or without a payload, deployments, Insights events and exceptions, and upload source maps and files. Because every action writes, test the agent with a Honeybadger project you do not mind cluttering first.
Which Gleap plan includes the Honeybadger integration?
Custom agents that use Honeybadger are part of the Team, Pro and Enterprise plans. Kai Code can use it on Team, Pro and Enterprise, and Kai Support can use connected apps as tools on the same plans. The API key decides which Honeybadger project receives the data. AI usage is billed separately; see pricing.
Can Kai Code read Honeybadger errors while fixing a bug?
Not through this toolkit, which cannot read errors. If your team runs an MCP server that can read Honeybadger data, connect it in Kai Code’s settings as a custom server instead.
