← All integrations

Bugsnag

61 operations0 webhooks

Error monitoring platform for tracking application crashes and stability across releases.

Supported operations

  • DeleteDestructive

    Remove a collaborator, revoking access to every project in the organization

  • GetRead-only

    Get a single collaborator

  • Get On ProjectRead-only

    Get a collaborator in the context of a project

  • Get Project AccessRead-only

    Get how one collaborator reaches one project

  • InviteWrite

    Invite a collaborator to an organization by email address

  • ListRead-only

    List the collaborators on an organization

  • List On ProjectRead-only

    List the collaborators who can reach a project

  • List Project AccessesRead-only

    List how a collaborator reaches each project, with the granting role

  • List ProjectsRead-only

    List the projects a collaborator can reach

  • Project Access CountsRead-only

    Count how many projects each named collaborator can reach

  • Update PermissionsWrite

    Change a collaborator's project access or admin status

FAQ

Install corsair and @corsair-dev/bugsnag, add the Bugsnag plugin, and connect with an API key. Then call methods like corsair.bugsnag.api.collaborators.delete() from your app. Corsair syncs data per tenant.

Yes. Bugsnag requires an API key from your Bugsnag account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit Bugsnag, GitHub, Notion, Stripe, and the rest. Trigger Bugsnag from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for error monitoring platform for tracking application crashes and stability across releases. Common builds include sync jobs, admin tooling, and agents that call Bugsnag APIs from your backend. Local DB entities let you query synced Bugsnag records without hitting the API on every read.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Bugsnag API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/bugsnag in the open repo. When Bugsnag ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Bugsnag data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Bugsnag data on your behalf.