# Airbrake integrations: projects and error groups

> Create a deploy, create a notice and upload a source map in Airbrake, and start a workflow when Airbrake sends “New error occurred”.

**Canonical page:** https://tray.ai/connectors/airbrake-integrations/
**Categories:** IT
**Connects through:** HTTP Connector

## Overview

Airbrake is an error and performance monitoring service that collects exceptions from your applications, groups them, and tracks them against deploys. Tray.ai connects to Airbrake through the HTTP Connector, so your workflows can call the Airbrake API alongside the rest of your stack.

## Use cases

### Projects

Read projects in Airbrake from any Tray.ai workflow. The Airbrake API covers calls such as list projects and get a project.

- List projects
- Get a project

### Error groups

Read and delete error groups in Airbrake from any Tray.ai workflow. The Airbrake API covers calls such as list error groups and get an error group.

- List error groups
- Get an error group
- Mute an error group

### Deploys

Read and create deploys in Airbrake from any Tray.ai workflow. The Airbrake API covers calls such as create a deploy and list deploys.

- Create a deploy
- List deploys
- Get a deploy

### Notices

Read and create notices in Airbrake from any Tray.ai workflow. The Airbrake API covers calls such as create a notice and list notices.

- Create a notice
- List notices
- Get a notice status

### Source maps

Read, create, and delete source maps in Airbrake from any Tray.ai workflow. The Airbrake API covers calls such as upload a source map and list source maps.

- Upload a source map
- List source maps
- Get a source map

### Airbrake events

Start a Tray.ai workflow the moment something happens in Airbrake. Airbrake sends events such as new error occurred and resolved error reoccurred to a Tray.ai webhook trigger.

- New error occurred
- Resolved error reoccurred

## Challenges Tray.ai solves

### Keeping Airbrake credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Airbrake credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Airbrake API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Airbrake API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Airbrake?

Yes. Tray.ai connects to Airbrake through the HTTP Connector, which calls the Airbrake API directly. Any call the Airbrake API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Airbrake?

The Airbrake API uses an API key in the query string. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Airbrake connector?

Airbrake runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Airbrake connector from the Airbrake API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/