Airbrake integration

What it does

The Airbrake integration lets your agency drive a client's error-triage workflow from inside TaskJuice. Connect a client's Airbrake project once and you can list error groups for a release, fetch the details of a single group, resolve a group when a fix ships, attach triage notes (ticket links, owner assignments, rollback decisions) to the group, and list deploys to correlate errors with releases. An inbound webhook fires whenever Airbrake delivers a notice, so you can route fresh errors into the rest of your incident pipeline without polling.

Connect an Airbrake account

1. Open your workspace in TaskJuice and navigate to Connections.
2. Choose Airbrake and click Connect.
3. In Airbrake, open the user-edit page (https://airbrake.io/users/edit) and copy your user key. The key authenticates every v4 API request as a Bearer token.
4. Copy the numeric project ID from the URL of the project's dashboard (https://airbrake.io/projects/<id>) and paste it into the connection form alongside the user key.

See the Airbrake API authentication docs for the full key flow and per-project scoping.

Triggers

• airbrake/notice-received fires when Airbrake delivers a notice webhook for a new error occurrence. Configure a webhook integration under Project settings, Integrations, Webhook in Airbrake, point it at the TaskJuice ingress URL for this trigger, and paste the trigger's shared secret into the Authorization header field on the Airbrake webhook form.

Airbrake's webhook integration does not sign payloads. TaskJuice verifies inbound POSTs by comparing the static Authorization header value against the shared secret configured on the trigger, so the secret never leaves your workspace.

Actions

• airbrake/list-groups lists error groups for the connected project, with optional environment and resolution filters and page-based pagination.
• airbrake/get-group fetches a single error group by ID, including occurrence counts and aggregate context.
• airbrake/resolve-group marks an error group as resolved. Resolved groups stop alerting until they reoccur.
• airbrake/add-note posts a note to an error group. Useful for recording triage decisions or linking to follow-up work.
• airbrake/list-deploys lists deploys recorded against the project, useful for correlating regressions with releases.

Known limitations

• Airbrake's REST API enforces a per-key rate limit. When the budget is exhausted Airbrake returns a 429 status, which TaskJuice surfaces as a retryable error so downstream resilience policies can back off.
• User keys are scoped to the user, not the project. A user without project access will fail with 403 on every call. Re-issue the key from an account with project access and reconnect.
• The webhook integration ships unsigned. TaskJuice mitigates this with the shared-secret Authorization header, but rotate the secret if it ever leaks.
• The notice envelope shape varies slightly across Airbrake-Ruby, Airbrake-Node, and Airbrake-Python notifier versions. Workflows that read deep fields should defensively check for nulls before referencing them.