Add Incident Update
Post 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.
Instatus is a status page and incident communication platform for managing service health, incidents, maintenance, monitors, and subscribers.
Post 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.
Post 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 subscribers when notify is true.
Create 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 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 subscribers.
Schedule 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 notify_early schedule later subscriber notifications.
Get the current health and configuration of one component on an Instatus status page.
Get one Instatus incident with its affected components and update history.
Get one Instatus maintenance with its schedule, affected components, automation settings, and update history.
List 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 incidents for an Instatus status page, optionally including or excluding lifecycle statuses.
List scheduled and historical maintenances for an Instatus status page.
List status pages available to the connected Instatus account so an agent can discover page IDs for component, incident, and maintenance operations.
Change a component's health or presentation on an Instatus status page.
Edit 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.
Fully 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 values; setting notify to true sends subscriber notifications.
The Instatus integration connects your Dench AI CRM directly to Instatus, so agents can read and act on your Instatus data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
15 actions are available for agents to invoke on your behalf. Every call runs through Instatus's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find Instatus and click Connect — you'll authorize access through Instatus's own sign-in flow. No API keys or code required.
Ask an agent to use Instatus in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench Instatus integration connects your AI CRM to Instatus, so AI agents can work with your Instatus data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
The Instatus integration currently exposes 15 actions, including Add Incident Update, Add Maintenance Update, Create Component, Create Incident, Create Maintenance, and Get Component. Agents invoke them on your behalf from chat or from automations.
No. You connect Instatus from your Dench workspace using Instatus's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through Instatus's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the Instatus connection from your workspace settings at any time.