Statuspage
Turn incidents and requests into Statuspage work items, and keep status in step across your tools.
26 ways to read, 12 ways to write, each write switched on by you.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with Statuspage, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- Create component groupApproval by rule
- Create componentApproval by rule
- List component groupsRead
Example flow
- Statuspage · List component groupsDone
- Statuspage · Create component groupNeeds approval
- Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Statuspage.
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to Statuspage
- Statuspage's reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect a Atlassian test account before you go live.
For developers
Technical detail
Read Statuspage pages, components, incidents, templates, postmortems, subscribers, metrics and audiences; update status, publish incidents and maintenance, and submit metric data.
Atlassian API docs- Source actions
- 26
- Destination actions
- 12
- Data types
- 20
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
Component group uptime1
- Get component group uptimeSource
Uptime percentage, outage durations and related incidents for a component group.
Component groups4
- Create component groupDestinationNot retried automaticallyApproval before production
Creates a group from existing components.
- Get component groupSource
One component group.
- List component groupsSource
Component groups with their member components.
- Update component groupDestinationProvider duplicate protectionApproval before production
Renames a group or replaces its components.
Component uptime1
- Get component uptimeSource
Uptime percentage and outage durations for a showcased component.
Components4
- Create componentDestinationNot retried automaticallyApproval before production
Adds a component to a page, optionally inside a group.
- Get componentSource
One component and its status.
- List componentsSource
Components on a page with their current status.
- Update component statusDestinationProvider duplicate protectionApproval before production
Sets a component's status or changes its name, description or group.
Incident subscribers1
- List incident subscribersSource
Subscribers following one incident (read-only).
Incident templates2
- Create incident templateDestinationNot retried automaticallyApproval before production
Saves an incident template. Creating a template does not post or notify anything.
- List incident templatesSource
Saved incident templates with their title, body, status and components.
Incident updates1
- Edit incident updateDestinationProvider duplicate protectionApproval before production
Corrects the text or display time of an existing incident update. Subscribers are notified only when Notify subscribers is true.
Incidents4
- Create incidentDestinationNot retried automaticallyApproval before production
Opens a realtime incident with affected components. Subscribers are notified only when Notify subscribers is true.
- Get incidentSource
One incident or maintenance with its updates and affected components.
- List incidentsSource
Incidents and maintenances on a page: all, unresolved, scheduled, upcoming or active maintenance.
- Update incidentDestinationProvider duplicate protectionApproval before production
Posts an update, changes status or component impact, or edits a maintenance window. Subscribers are notified only when Notify subscribers is true.
Maintenances1
- Schedule maintenanceDestinationNot retried automaticallyApproval before production
Schedules a maintenance window with optional automatic transitions. Subscribers are notified only when Notify subscribers is true.
Metric data1
- Submit metric data pointDestinationNot retried automaticallyApproval before production
Adds one data point to a self-reported (custom) system metric.
Metrics providers2
- Get metrics providerSource
One connected metrics provider.
- List metrics providersSource
Connected metrics providers such as Datadog, New Relic or Pingdom.
Metrics2
- Get metricSource
One system metric with its display settings and latest data time.
- List metricsSource
System metrics shown on a page with their provider and latest data time.
Organization users1
- List team membersSource
Statuspage team members in an organization.
Page access groups2
- Get page access groupSource
One audience group.
- List page access groupsSource
Audience groups of an audience-specific page with their components and users.
Page access users2
- Get page access userSource
One viewer of an audience-specific page.
- List page access usersSource
Viewers of an audience-specific (private) page, optionally by email.
Pages3
- Get pageSource
One status page with its settings.
- List pagesSource
Status pages the API key can access.
- Update page settingsDestinationProvider duplicate protectionApproval before production
Changes a page's name, URLs, time zone, search visibility and subscriber options.
Postmortems2
- Get postmortemSource
The published and draft postmortem of an incident.
- Save postmortem draftDestinationProvider duplicate protectionApproval before production
Saves the draft postmortem text for an incident. Publishing (which can notify subscribers) is not done here.
Provider metrics1
- List provider metricsSource
Metrics that come from one metrics provider.
Subscriber counts1
- Count subscribersSource
Subscriber counts by type, optionally filtered by type and state.
Subscribers2
- Get subscriberSource
One page subscriber (read-only).
- List subscribersSource
Page subscribers by type and state (read-only).
Access and limits
- Authentication
- API key
- Plans and access
- All Statuspage plans, including Free; private pages and some subscriber types depend on the plan. API keys belong to a user and act with that user's page access.
- Test environment
- A free Statuspage page works for testing.
- Rate limits
- 1 request per second per API token (bursts of up to 5); HTTP 420 or 429 when exceeded.
- Pagination
- page and per_page (or limit) parameters; Nexra advances while a page is full.
- Provider events
- Webhook subscribers receive incident and component updates. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.
Before you build a flow
- Incident and maintenance writes never notify subscribers or post to Twitter unless Notify subscribers is explicitly true for that call.
- Statuspage returns HTTP 420 for some rate-limit responses; Nexra classifies it as a rate limit.
- Creating or updating an incident or maintenance is visible on the status page immediately. Subscriber notifications are a separate opt-in per call (Notify subscribers), and every write must be enabled on the connection first.
- Incident templates are created with tweeting off and notifications off unless the template sets Notify subscribers when used. Incident update edits never post to Twitter.
- Postmortems: drafts can be read and saved; publishing, reverting and deleting postmortems are not implemented because publishing can notify subscribers.
- Metric data is submitted one point at a time to self-reported metrics; the bulk metrics/data endpoint and deleting metric data are not implemented. Statuspage accepts points up to 28 days old.
- Page access users and groups (audience-specific pages) are read-only; adding or removing viewers is not implemented.
- Team members are read per organization ID; inviting and removing users and changing permissions are not implemented.
- Subscribers are read-only and one page at a time; creating, unsubscribing, reactivating, resending confirmations and any bulk subscriber action are intentionally excluded.
- Deleting components, groups, incidents, metrics, providers and page access users is intentionally excluded.
- Creates have no idempotency key; uncertain writes are not repeated automatically.
Developer reference
- Create the Atlassian credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose Statuspage, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/statuspage and the Connections API.