# Rootly integrations: incidents and alerts > Create an incident, create an alert and create an action item in Rootly, and start a workflow when Rootly sends “Incident created”. **Canonical page:** https://tray.ai/connectors/rootly-integrations/ **Categories:** IT **Connects through:** HTTP Connector ## Overview 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. ## Use cases ### Incidents Read, create, and update incidents in Rootly from any Tray.ai workflow. The Rootly API covers calls such as list incidents and create an incident. - List incidents - Create an incident - Update an incident ### Alerts Read and create alerts in Rootly from any Tray.ai workflow. The Rootly API covers calls such as list alerts and create an alert. - List alerts - Create an alert - Acknowledge an alert ### Action items Read, create, update, and delete action items in Rootly from any Tray.ai workflow. The Rootly API covers calls such as list action items and create an action item. - List action items - Create an action item - Update an action item ### Schedules Read, create, and update schedules in Rootly from any Tray.ai workflow. The Rootly API covers calls such as list schedules and create a schedule. - List schedules - Create a schedule - Update a schedule ### Escalation policies Read, create, update, and delete escalation policies in Rootly from any Tray.ai workflow. The Rootly API covers calls such as list escalation policies and create an escalation policy. - List escalation policies - Create an escalation policy - Update an escalation policy ### Services Read, create, update, and delete services in Rootly from any Tray.ai workflow. The Rootly API covers calls such as list services and create a service. - List services - Create a service - Update a service ## Challenges Tray.ai solves ### Keeping Rootly 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 Rootly 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 Rootly 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 Rootly 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 Rootly? Yes. Tray.ai connects to Rootly through the HTTP Connector, which calls the Rootly API directly. Any call the Rootly API documents can run as a step in a Tray.ai workflow. ### 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. ### Can I get a dedicated Rootly connector? Rootly runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Rootly connector from the Rootly 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/