# Bugsnag AI integration on Definable

> Bugsnag is an error monitoring and stability management platform that helps developers identify, prioritize, and fix software bugs.

## What this connects

Bugsnag is an error monitoring and stability management platform that helps developers identify, prioritize, and fix software bugs.

Vendor: https://app.bugsnag.com/

## Tools available

**60** tools available. First 12:

- `BUGSNAG_ADD_ORGANIZATION_COLLABORATOR_TEAM_MEMBERSHIPS` — Add Collaborator to Teams — Tool to add a collaborator to a group of teams in a Bugsnag organization. Use when you need to assign a collaborator to specific teams or all teams. Requires admin permissions on the organization.
- `BUGSNAG_ADD_ORGANIZATION_TEAM_MEMBERSHIPS` — Add Collaborators to Team — Tool to add collaborators to a team in a Bugsnag organization. Use when you need to add specific collaborators or all organization collaborators to a team. Requires admin permissions on the organization.
- `BUGSNAG_BULK_UPDATE_ERRORS` — Bulk Update Errors — Bulk update multiple errors in a Bugsnag project. Applies the same operation to all specified errors. Note: The actual API implementation returns only the operation name in the response, not per-error results. This differs from the OpenAPI specification which documents detailed per-error results. A successful response indicates the bulk operation was accepted and applied to all specified errors. Use cases: - Mark multiple errors as fixed after a release - Assign errors to a team member for investigation - Snooze or ignore low-priority errors in bulk - Link multiple related errors to a single issue tracker ticket - Change severity levels across related errors Prerequisites: Obtain project_id from BUGSNAG_LIST_PROJECTS and error_ids from BUGSNAG_LIST_ERRORS_ON_PROJECT.
- `BUGSNAG_CONFIGURE_INTEGRATION` — Configure Integration — Tool to configure a new integration for a Bugsnag project. Use after selecting integration key and preparing credentials.
- `BUGSNAG_CONFIRM_PROJECT_EVENT_DATA_DELETION` — Confirm Project Event Data Deletion — Confirms a project event data deletion request in Bugsnag. Use this action after creating a deletion request to confirm and proceed with the actual deletion of event data. The deletion request must be in AWAITING_CONFIRMATION status before it can be confirmed.
- `BUGSNAG_CREATE_COLLABORATOR` — Invite Collaborator — Invites a new collaborator to a Bugsnag organization by email. Use this action to grant a user access to the organization. Optionally specify project_ids to restrict access to specific projects, or set admin=true to grant full admin privileges across all projects. Returns the collaborator details including their invitation status (pending_invitation=true until they accept). Re-inviting an existing email returns the existing collaborator data.
- `BUGSNAG_CREATE_CUSTOM_EVENT_FIELD` — Create Custom Event Field — Creates a custom event field for a Bugsnag project, enabling filtering and pivoting on custom metadata. Use this tool when you need to create a new searchable/filterable field from event metaData. Requires a project_id (get from BUGSNAG_LIST_PROJECTS), a unique display_id for the filter, and the path to the data in event metaData. Example: Create a custom field to filter by user account ID: - display_id: "custom.user.accountId" - path: "metaData.user.accountId" - filter_options: {"name": "Account ID", "match_types": ["eq", "ne"]}
- `BUGSNAG_CREATE_ORGANIZATION_PROJECT` — Create Organization Project — Tool to create a new project in a Bugsnag organization. Use when you need to set up a new project for error tracking under a specific organization. Requires organization_id, project name, and platform type. Optionally configure browser filtering for JavaScript projects.
- `BUGSNAG_CREATE_ORGANIZATION_TEAM` — Create Organization Team — Tool to create a new team in a Bugsnag organization. Use when you need to organize collaborators into teams for better access management. The team name must be unique within the organization.
- `BUGSNAG_CREATE_ORG_DATA_DELETION` — Create Organization Data Deletion Request — Tool to create an event data deletion request for GDPR/CCPA compliance. Use when you need to delete event data matching specific criteria (e.g., user email, error class, device info). Specify filters to target events - most common is filtering by user.email. The deletion processes asynchronously; check the returned status and id to track progress. Requires organization administrator permissions.
- `BUGSNAG_CREATE_ORG_DATA_REQUEST` — Create Organization Data Request — Tool to create an event data request for a Bugsnag organization (GDPR/CCPA compliance). Use when you need to export event data for a specific user or set of conditions to comply with data access requests. The request is processed asynchronously - check the status field and use the returned ID to monitor progress. Once completed, the url field provides a download link for the data export.
- `BUGSNAG_CREATE_PROJECT_DATA_DELETION` — Create Project Event Data Deletion Request — Tool to create an event data deletion request for a specific project. Use when you need to delete event data matching specific criteria (e.g., error class, severity, user email) within a project. Specify filters to target events - most common is filtering by event.class or user.email. The deletion processes asynchronously; check the returned status and id to track progress.

## Auth

Auth schemes: `API_KEY`.

## How agents use Bugsnag

Inside a Definable workflow, Bugsnag is one of the tools the **Distributor specialist** can call. Example coordination patterns:

- **Researcher → Bugsnag** — the Researcher (GPT-5.5) pulls context from Bugsnag (records, threads, documents), synthesises findings, and briefs the rest of the team.
- **Writer → Distributor → Bugsnag** — the Writer (Claude Opus 4.7) drafts copy in brand voice, the Verifier passes it, then the Distributor writes the result into Bugsnag (create record, post message, draft email).
- **Designer / Engineer → Distributor → Bugsnag** — the Designer ships an asset or the Engineer ships a code change, the Distributor delivers it via Bugsnag (attach file, open PR comment, post status).

The Verifier checks every Bugsnag call. On rate limit, schema drift, or auth refresh it self-heals and retries — the workflow completes without manual intervention.

## Categories

- developer tools — https://definable.ai/apps/category/developer-tools/
- server monitoring — https://definable.ai/apps/category/server-monitoring/

## Related

- HTML page: https://definable.ai/apps/bugsnag/
- Same category (developer tools): https://definable.ai/apps/category/developer-tools/
- All integrations: https://definable.ai/apps/
- Workflow (multi-agent loop): https://definable.ai/workflow/
- Apps llms.txt index: https://definable.ai/llms-apps.txt