Integration · Developer
AI agents for BugSnag
List and read BugSnag errors and their events, mark errors fixed, ignored or snoozed, assign them, and see releases and error trends, through the BugSnag Data Access API with a personal auth token.
- Actions
- 10
- Read
- 9
- Write
- 1
Actions
What your agents can do in BugSnag
10 actions. Each one is a tool your agents can call and a step your workflows can run.
Read 9
Look things up. Nothing changes.
List organizations
Lists the BugSnag organizations the token's user belongs to, as result: each with its id, name, slug, creator and when it was created.
List projects
Lists an organization's projects, optionally by name, as result.
List errors
Lists a project's errors (grouped exceptions), most recently seen first by default, filtered by status (open, fixed, snoozed, ignored), release stage (like production) and how recent.
Get an error
Reads one error: error_class, message, context, severity (original and overridden), status, event and user counts.
List an error's events
Lists an error's events (individual occurrences), newest first, up to 30 a page, as result.
Get an error's latest event
Reads the most recent event of an error in full: exceptions (class, message and stack trace frames with file, line and method), breadcrumbs, request, app.
Get an event
Reads one event in full by its ID (from "List an error's events"): the exceptions with stack traces, breadcrumbs, request, app, device, user, metadata, severity and when it was received.
List releases
Lists a project's releases, newest first, optionally in one release stage, as result.
Get an error's trend
Counts an error's events over time in up to 50 buckets, optionally only recent ones (since, like 7d) or in one release stage.
Write 1
Create, change or send.
Fix, ignore, snooze or assign an error
Changes an error's workflow state: fix (mark fixed), open (reopen), ignore (keep collecting events, stop notifying), snooze (for snooze_seconds, then reopen if it occurs again), assign.
A person can approve first
Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything.
Connection
How it connects
Connect it once in the console, then give it to the agents and workflows that need it.
Paste an API key from your BugSnag account.
What you enter
- Personal auth token
Kept safe
- Credentials are stored encrypted with your organization's own keys.
- They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
- Calls go only to the tool's own servers.
Ideas
Ideas to start with
Starting points made only from the actions above. Mix them with any other tool your agents can use.
- 01
Ask about your BugSnag data
Ask a question in plain words. The agent can list organizations, list projects or list errors in BugSnag, then answers with what it found.
- 02
Share what it finds in Slack
Give one agent BugSnag and Slack: it can list organizations in BugSnag and post a summary to a Slack channel in the same run.
- 03
Run it as a workflow step
Add "Fix, ignore, snooze or assign an error" to a workflow, and it runs in BugSnag the same way every time, with or without an agent.
FAQ
BugSnag and MyDeepAgents
Can MyDeepAgents connect to BugSnag?
Yes. The BugSnag connector has 10 actions: 9 read and 1 makes changes. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect BugSnag?
Paste an API key from your BugSnag account. You'll need: Personal auth token. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.
Can an agent change data in BugSnag without asking?
Only if you let it. Its one action that changes data can be set to wait for a person's approval before it runs.
Can I use BugSnag in workflows as well as agents?
Yes. Every BugSnag action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put BugSnag to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.