Skip to content
Airbrake logo

Connectors / IT · HTTP Connector

Automate Airbrake with Tray.ai

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

What can you do with Airbrake on Tray.ai?

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.

  • When Airbrake sends “New error occurred”, create a ticket in your engineering tracker with the stack trace.
  • On “Resolved error reoccurred”, page the on-call engineer and reopen the original ticket.
  • Create a deploy each time your CI pipeline ships, so errors line up with the release that caused them.
Connects through
HTTP Connector
Authentication
An API key in the query string
Base URL
https://api.airbrake.io

Set it up

Connect Airbrake to Tray.ai

Each step uses Airbrake's own API details, from its documentation.

Step 1

Save Airbrake's API key

Save the key as a Tray.ai authentication and add it to the query string from $.auth, so it never sits in the workflow itself.

Step 2

Point the HTTP Client at the API

Add an HTTP Client step and use https://api.airbrake.io as the base URL. Or paste a cURL example from Airbrake's API docs, and Tray.ai fills in the method, URL, and headers.

Step 3

Start with “List projects”

It's one of 17 documented actions, under Projects. The response comes back as data the next step can map into your other apps.

Step 4

Start workflows from Airbrake events

Give Airbrake the URL of a Tray.ai webhook trigger. “New error occurred” can then start a workflow, and so can 1 other event.

Workflows to build with Airbrake

Each one uses actions and events from Airbrake's own API documentation.

Open a Jira bug when Airbrake catches a new error

When

New error occurred

Then

  1. Get an error group for the new error
  2. Create a bug in Jira with the error details
  3. Post the Jira link to the engineering channel in Slack

With Jira and Slack

Record GitHub releases as deploys in Airbrake

When

A release is published in GitHub

Then

  1. Create a deploy with the release version and revision
  2. Post the deploy details to the release channel in Microsoft Teams

With GitHub and Microsoft Teams

Reopen the GitLab issue when a fixed error comes back

When

Resolved error reoccurred

Then

  1. Get an error group for the returning error
  2. Reopen the linked issue in GitLab with the new occurrence

With GitLab

Apps you can build on Airbrake data

Internal tools your team can build with an AI assistant, each one using Airbrake calls from its API documentation.

Error triage queue

Lists error groups by project and lets an engineer mute, unmute or delete each one.

Deploy impact report

Shows each deploy next to new and reoccurring errors so a team can see which release caused a problem.

Give your AI agents Airbrake tools

Build an MCP server on Airbrake in Agent Gateway and choose which actions your agents can call. Every call runs with access control and an audit trail. How Agent Gateway works

  • List projects
  • List error groups
  • Create a deploy
  • Create a notice
  • Upload a source map
  • Get a project
  • Get an error group
  • Mute an error group

What the Airbrake API covers

5 resources and 17 documented actions, each one a call the HTTP Connector can make from a Tray.ai workflow. Connecting it takes a few clicks: here's how.

Projects

  • List projects
  • Get a project

Error groups

  • List error groups
  • Get an error group
  • Mute an error group
  • Unmute an error group
  • Delete an error group

Deploys

  • Create a deploy
  • List deploys
  • Get a deploy

Notices

  • Create a notice
  • List notices
  • Get a notice status

Source maps

  • Upload a source map
  • List source maps
  • Get a source map
  • Delete a source map

Events Airbrake can send to a Tray.ai webhook trigger

  • New error occurred
  • Resolved error reoccurred

Checked against Airbrake's own documentation on 2026-10-22

docs.airbrake.io/docs/devops-tools/api

Frequently asked questions

What can a Tray.ai workflow do in Airbrake?

+

The Airbrake API documents 17 actions across 5 resources (Projects, Error groups, Deploys, Notices, Source maps). For example: List projects; List error groups; Create a deploy. A workflow can make any documented call through the HTTP Connector.

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.

Which Airbrake events can start a Tray.ai workflow?

+

Airbrake sends 2 events to a webhook URL, for example: New error occurred; Resolved error reoccurred. A Tray.ai webhook trigger receives them and starts a workflow.

See Airbrake working against your stack.

We'll walk through a tailored demo with your systems plugged in.

Great — a couple more details

This helps us connect you with the right person. Optional, and you can skip it.