Skip to content
Rootly logo

Connectors / IT · HTTP Connector

Automate Rootly with Tray.ai

Create an incident, create an alert and create an action item in Rootly, and start a workflow when Rootly sends “Incident created”.

What can you do with Rootly on Tray.ai?

Rootly is an incident management and on-call platform that tracks incidents and alerts, runs schedules and escalation policies, and records follow-up action items. Tray.ai connects to Rootly through the HTTP Connector, so your workflows can call the Rootly API alongside the rest of your stack.

  • When Rootly sends “Incident created”, post the details to your leadership channel in your team chat.
  • Create an incident in Rootly when your monitoring system detects a service outage.
  • When Rootly sends “Incident resolved”, update the status page and notify affected customers through your help desk.
  • Create an action item in Rootly for each follow up ticket raised in your issue tracker after a postmortem.
Connects through
HTTP Connector
Authentication
A bearer token or OAuth 2.0
Base URL
https://api.rootly.com/v1

Set it up

Connect Rootly to Tray.ai

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

Step 1

Save Rootly's API token

Save the token Rootly issues as a Tray.ai authentication. The HTTP Client sends it as a bearer token on every call. The token stays out of the workflow and out of the logs.

Step 2

Point the HTTP Client at the API

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

Step 3

Start with “List incidents”

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

Step 4

Start workflows from Rootly events

Give Rootly the URL of a Tray.ai webhook trigger. “Incident created” can then start a workflow, and so can 7 other events.

Workflows to build with Rootly

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

Open a Rootly incident from critical Datadog alerts

When

A critical monitor triggers in Datadog

Then

  1. Create an incident with the monitor details
  2. Post the incident link to the on-call channel in Slack

With Datadog and Slack

Create Jira issues for Rootly incident follow-ups

When

Incident resolved

Then

  1. List action items for the incident
  2. Create an issue for each action item in Jira

With Jira

Update the ServiceNow record when a Rootly incident is mitigated

When

Incident mitigated

Then

  1. Read the incident title and mitigation time from Rootly
  2. Update the matching incident in ServiceNow with the mitigation time

With ServiceNow

Apps you can build on Rootly data

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

Incident follow-up tracker

Lists action items from resolved incidents and lets owners update or close each one.

Alert triage board

Lists open alerts by service and lets an on-call engineer acknowledge, escalate or resolve each one.

On-call cover request

Lists schedules and lets an engineer request an override shift when they need cover.

Give your AI agents Rootly tools

Build an MCP server on Rootly 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 incidents
  • List alerts
  • List action items
  • List schedules
  • List escalation policies
  • List services
  • Create an incident
  • Update an incident

What the Rootly API covers

6 resources and 26 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.

Incidents

  • List incidents
  • Create an incident
  • Update an incident
  • Resolve an incident
  • Mitigate an incident

Alerts

  • List alerts
  • Create an alert
  • Acknowledge an alert
  • Resolve an alert
  • Escalate an alert

Action items

  • List action items
  • Create an action item
  • Update an action item
  • Delete an action item

Schedules

  • List schedules
  • Create a schedule
  • Update a schedule
  • Create an override shift

Escalation policies

  • List escalation policies
  • Create an escalation policy
  • Update an escalation policy
  • Delete an escalation policy

Services

  • List services
  • Create a service
  • Update a service
  • Delete a service

Events Rootly can send to a Tray.ai webhook trigger

  • Incident created
  • Incident updated
  • Incident mitigated
  • Incident resolved
  • Alert created
  • Alert updated
  • Workflow run completed
  • Workflow run failed

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

docs.rootly.com/api-reference/overview

Frequently asked questions

What can a Tray.ai workflow do in Rootly?

+

The Rootly API documents 26 actions across 6 resources (Incidents, Alerts, Action items, Schedules, Escalation policies, Services). For example: List incidents; List alerts; List action items. A workflow can make any documented call through the HTTP Connector.

How does Tray.ai authenticate with Rootly?

+

The Rootly API uses a bearer token and OAuth 2.0. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

Which Rootly events can start a Tray.ai workflow?

+

Rootly sends 8 events to a webhook URL, for example: Incident created; Incident updated; Incident mitigated; Incident resolved; Alert created; Alert updated; Workflow run completed; Workflow run failed. A Tray.ai webhook trigger receives them and starts a workflow.

See Rootly 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.