Instatus for AI agents
Agents read Instatus at once. Changes and sends are held for a person's approval by default.
About Instatus
Instatus is a status page and incident communication platform for managing service health, incidents, maintenance, monitors, and subscribers.
What an agent can do in Instatus
Every Instatus action is classed by the platform as a read, a change or a send. Reads run at once. Changes and sends are held for a person by default.
Runs at once (reads)
Looks things up in Instatus without asking first. 7 actions.
- Get ComponentGet the current health and configuration of one component on an Instatus status page.
- Get IncidentGet one Instatus incident with its affected components and update history.
- Get MaintenanceGet one Instatus maintenance with its schedule, affected components, automation settings, and update history.
- List ComponentsList components and their current health for one Instatus status page, including child components where present. Pass the response's next_cursor back unchanged to fetch another page.
- List IncidentsList incidents for an Instatus status page, optionally including or excluding lifecycle statuses.
- List MaintenancesList scheduled and historical maintenances for an Instatus status page.
- List Status PagesList status pages available to the connected Instatus account so an agent can discover page IDs for component, incident, and maintenance operations.
Held for approval by default (changes and sends)
Held for a person's approval by default. The approval is recorded and the action is sent once, never twice, with 10 seconds to undo. 8 actions.
- Add Incident UpdatePost a public lifecycle update to an Instatus incident and change affected component states. This can send external notifications to page and affected-component subscribers when notify is true.
- Add Maintenance UpdatePost a public progress update to an Instatus maintenance, optionally changing its lifecycle, timing, and affected component states. This can send external notifications to page and affected-component
- Create ComponentCreate a component on an Instatus status page. This changes the page's component configuration and can make the new component and its initial health status publicly visible.
- Create IncidentCreate an incident on an Instatus status page with optional affected component states. The incident is published publicly by default; notify=true can send notifications to page and affected-component
- Create MaintenanceSchedule or start a maintenance on an Instatus status page. The required notification controls are side-effecting: notify can contact subscribers immediately, while notify_start, notify_end, and notif
- Update ComponentChange a component's health or presentation on an Instatus status page.
- Update IncidentEdit an existing Instatus incident's name, timing, lifecycle status, affected components, or component states. Setting notify to true sends notifications to page and affected-component subscribers.
- Update MaintenanceFully replace an Instatus maintenance's public message, schedule, lifecycle state, affected components and states, and automation settings. Call INSTATUS_GET_MAINTENANCE first and preserve unchanged v
Changes wait in Needs you
Changes and sends in Instatus are held for a person's approval by default. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.
Instatus questions
Can an agent change data in Instatus on its own?
Not by default. Changes and sends in Instatus are held for a person's approval. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.
What can an agent read in Instatus?
This connector lists 7 read actions. Reads run at once, without waiting for approval.
How does Instatus connect?
It connects with API key. Connectors are built and maintained by third-party developers; availability is confirmed during scoping.