
Connectors / IT · HTTP Connector
Automate Statuspage with Tray.ai
Create an incident, create a component and create a subscriber in Statuspage, and start a workflow when Statuspage sends “Incident created”.
What can you do with Statuspage on Tray.ai?
Statuspage is Atlassian's hosted status page service for publishing component status, incidents and scheduled maintenance to customers and notifying subscribers. Tray.ai connects to Statuspage through the HTTP Connector, so your workflows can call the Statuspage API alongside the rest of your stack.
- Create an incident on Statuspage when the on-call engineer declares an outage.
- When Statuspage sends “Incident created”, alert your customer support team in your team chat.
- Post a note to affected accounts in your CRM when Statuspage sends “Component status changed”.
- Add metric data points from your monitoring tool so customers see live response times.
- Connects through
- HTTP Connector
- Authentication
- An API key in a request header or an API key in the query string
- Base URL
- https://api.statuspage.io/v1
Set it up
Connect Statuspage to Tray.ai
Each step uses Statuspage's own API details, from its documentation.
Step 1
Save Statuspage's API key
Save the key as a Tray.ai authentication. The HTTP Client puts it in the request header, read from $.auth. The key 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.statuspage.io/v1 as the base URL. Or paste a cURL example from Statuspage's API docs, and Tray.ai fills in the method, URL, and headers.
Step 3
Start with “List incidents”
It's one of 19 documented actions, under Incidents. The response comes back as data the next step can map into your other apps.
Step 4
Start workflows from Statuspage events
Give Statuspage the URL of a Tray.ai webhook trigger. “Incident created” can then start a workflow, and so can 2 other events.
Workflows to build with Statuspage
Each one uses actions and events from Statuspage's own API documentation.
Notify support in Slack when a Statuspage incident opens
When
Incident created
Then
- List components to show which services are affected
- Post the incident name and status to the support channel in Slack
With Slack
Post Statuspage incidents from critical Datadog alerts
When
A critical monitor triggers in Datadog
Then
- Create an incident on the status page
- Update a component to show degraded performance
With Datadog
Flag Zendesk tickets when a Statuspage component changes
When
Component status changed
Then
- List unresolved incidents to link the current incident
- Create an internal note on open tickets for that service in Zendesk
With Zendesk
Apps you can build on Statuspage data
Internal tools your team can build with an AI assistant, each one using Statuspage calls from its API documentation.
Open incident console
Lists unresolved incidents with component status and lets on-call post an update or change a component.
Status change log
Records incident and component status changes as they happen so support can see a timeline.
Give your AI agents Statuspage tools
Build an MCP server on Statuspage 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 components
- List subscribers
- List metrics
- List pages
- Create an incident
- Update an incident
- Delete an incident
What the Statuspage API covers
5 resources and 19 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
- Delete an incident
- List unresolved incidents
Components
- List components
- Create a component
- Update a component
- Delete a component
Subscribers
- List subscribers
- Create a subscriber
- Update a subscriber
- Unsubscribe a subscriber
Metrics
- List metrics
- Add metric data points
- Delete a metric
Pages
- List pages
- Get a page
- Update a page
Events Statuspage can send to a Tray.ai webhook trigger
- Incident created
- Incident updated
- Component status changed
Checked against Statuspage's own documentation on 2026-10-22
How Tray.ai makes this work
Statuspage plugs into the whole Tray.ai platform
Intelligent Integration
Integrate and automate across 12,000+ apps, databases, APIs, and services with visual workflows, error handling, and observability.
Learn more →Agent Builder
Build AI agents that read, write, and take action in Statuspage — with guardrails, audit, and human-in-the-loop.
Learn more →Agent Gateway for MCP
Expose Statuspage actions as governed MCP tools — observable, rate-limited, authenticated.
Learn more →Tray Helix
Build apps on Statuspage data with your AI assistant, then deploy, run, and govern them on Tray.ai.
Learn more →More it apps on Tray.ai
Dedicated connectors and other apps Tray.ai reaches in the same category. See every it connector →
Frequently asked questions
What can a Tray.ai workflow do in Statuspage?
+
The Statuspage API documents 19 actions across 5 resources (Incidents, Components, Subscribers, Metrics, Pages). For example: List incidents; List components; List subscribers. A workflow can make any documented call through the HTTP Connector.
How does Tray.ai authenticate with Statuspage?
+
The Statuspage API uses an API key in a request header and 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 Statuspage events can start a Tray.ai workflow?
+
Statuspage sends 3 events to a webhook URL, for example: Incident created; Incident updated; Component status changed. A Tray.ai webhook trigger receives them and starts a workflow.
See Statuspage working against your stack.
We'll walk through a tailored demo with your systems plugged in.
Thanks — someone from our team will be in touch soon.