Bugsnag integration

What it does

The Bugsnag integration (now SmartBear Insight Hub) lets your agency turn client error reports into structured response workflows. Connect a Bugsnag personal auth token once and your workflows can discover the client's organizations and projects, page through open errors, post triage comments back onto an error, change an error's status to fixed, snoozed, or ignored, and react in real time when Bugsnag forwards a new exception via its Data Forwarding webhook.

Connect a Bugsnag account

1. Open your workspace in TaskJuice and navigate to Connections.
2. Choose Bugsnag and click Connect.
3. In a new tab, sign in to app.bugsnag.com as the client.
4. Open My Account Settings, go to Personal auth tokens, and generate a new token. Give it a name that identifies TaskJuice so revocation stays scoped.
5. Copy the token and paste it into TaskJuice, then save the connection.

To rotate or revoke the token later, return to the same Personal auth tokens screen in Bugsnag, generate a replacement, update the TaskJuice connection, and delete the old token.

Triggers

• bugsnag/error-created fires when Bugsnag forwards a new error or a notable event on an existing error via the Data Forwarding webhook. The payload includes the account, project, trigger reason (firstException, errorEventFrequency, projectSpiking, etc.), the error metadata, and the most recent event details.

The webhook delivers one event per POST. Configure the webhook in the Bugsnag UI under Data Forwarding with a custom Authorization header value matching the shared secret you supply when subscribing the trigger. TaskJuice verifies the header on every inbound POST and rejects unsigned traffic.

Actions

• bugsnag/list-organizations lists the Bugsnag organizations the connected user belongs to, with paging via the offset token returned in the Link header.
• bugsnag/list-projects lists projects in a given organization, with an optional search query and the same offset paging.
• bugsnag/list-errors pages through errors on a project with optional filters for status, severity, release stage, sort key, direction, and a since timestamp.
• bugsnag/create-error-comment posts a comment (Markdown supported) to an error, attributed to the connected user.
• bugsnag/update-error-status updates an error with one of the documented operations (fix, open, snooze, ignore, override_severity), with optional reopen rules for snooze and severity for override.

Known limitations

• The integration calls the Bugsnag Data Access API v2 with a personal auth token. Per-token request limits, project visibility, and operation permissions are governed by the connected user's Bugsnag role, not by TaskJuice. When Bugsnag returns a 422 with a validation error, TaskJuice surfaces it as a non-retryable validation failure; 429 responses are surfaced as retryable rate limits.
• A personal auth token inherits every project the connected user can see in Bugsnag. Connect each client account with a dedicated user so revocation, project visibility, and audit trails stay isolated.
• Bugsnag does not sign webhook payloads with HMAC. Inbound authentication relies on a static shared secret carried in the Authorization header you set under Data Forwarding. Treat the secret like an API key, store it in TaskJuice, and rotate it in Bugsnag when staff rotate.
• Bugsnag's Data Forwarding webhook fires on configurable triggers (first exception, regression, project spiking, frequency thresholds, etc.). The trigger.type field on the payload tells the workflow which condition fired so branches can fan out by reason.