Statuspage connector for AI agents

Tools your on-call agent reaches for on Statuspage, scoped per tenant.

CALL ANY TOOL

Incident comms end to end: create and update incidents, flip component status, manage component groups, subscribers, and uptime metrics from one vaulted API key.

statuspage_component_groups_list

List component groups

Retrieve a list of component groups on a statuspage status page, with optional pagination.

Parameters

Name

Type

Required

Description

page_id

string

Required

The identifier of the Statuspage page whose component groups should be listed

page

number

Optional

The page offset of component groups to fetch. The first page is 0, the second is 1, etc.

per_page

number

Optional

The number of results to return per page. Maximum and default of 100.

statuspage_component_get

Get component

statuspage_component_create

Create component

statuspage_component_group_update

Update component group

statuspage_component_delete

Delete component

statuspage_component_page_access_groups_add

Add component page access groups

statuspage_component_page_access_groups_remove

Remove component page access groups

statuspage_components_list

List components

statuspage_component_group_get

Get component group

statuspage_component_group_create

Create component group

statuspage_component_update

Update component

statuspage_component_group_delete

Delete component group

statuspage_component_page_access_users_add

Add component page access users

statuspage_component_page_access_users_remove

Remove component page access users

statuspage_incident_subscribers_list

List incident subscribers

statuspage_component_group_uptime_get

Get component group uptime

statuspage_incident_create

Create incident

Create a new incident or scheduled maintenance on a statuspage page. supports realtime incidents (investigating/identified/monitoring/resolved) and scheduled maintenances (scheduled/in_progress/verifying/completed), with optional affected components, notification control, and auto-transition settings.

Parameters

Name

Type

Required

Description

name

string

Required

Incident name. Maximum length of 255 characters.

page_id

string

Required

The identifier of the Statuspage page to create the incident on

auto_transition_deliver_notifications_at_end

boolean

Optional

Whether to send a notification when the scheduled maintenance automatically transitions to completed.

auto_transition_deliver_notifications_at_start

boolean

Optional

Whether to send a notification when the scheduled maintenance automatically transitions to started.

auto_transition_to_maintenance_state

boolean

Optional

Whether to change affected components' status to under_maintenance once the scheduled maintenance is in progress.

auto_transition_to_operational_state

boolean

Optional

Whether to change affected components' status to operational once the scheduled maintenance completes.

auto_tweet_at_beginning

boolean

Optional

Whether to tweet automatically when the scheduled maintenance starts.

auto_tweet_on_completion

boolean

Optional

Whether to tweet automatically when the scheduled maintenance completes.

auto_tweet_on_creation

boolean

Optional

Whether to tweet automatically when the scheduled maintenance is created.

auto_tweet_one_hour_before

boolean

Optional

Whether to tweet automatically one hour before the scheduled maintenance starts.

backfill_date

string

Optional

Timestamp for when the incident was backfilled, in YYYY-MM-DD format.

backfilled

boolean

Optional

Whether the incident is backfilled (recorded after the fact). If true, components cannot be specified.

body

string

Optional

The initial message, created as the first incident update. Maximum length of 25000 characters.

component_ids

array

Optional

List of component IDs affected by this incident. Example: ["kctbh9vrtdwd", "lcy4z7wq3fjr"].

components

object

Optional

Map of component_id to new status to apply to affected components. Example: {"kctbh9vrtdwd": "degraded_performance"}. Valid statuses: operational, under_maintenance, degraded_performance, partial_outage, major_outage.

deliver_notifications

boolean

Optional

Whether to deliver notifications to subscribers. If false, the incident is created without notifying customers. Defaults to true.

impact_override

string

Optional

Value to override the calculated impact value. Valid values: none, maintenance, minor, major, critical.

metadata

object

Optional

Arbitrary JSON object attached to the incident. All top-level values in the object must also be objects, e.g. {"jira": {"issue_id": "ABC-123"}}.

reminder_intervals

string

Optional

Custom reminder intervals for unresolved/open incidents (not applicable to scheduled maintenance). A serialized array of strictly increasing integers 1-24 (e.g. "[1, 5, 7, 10]"), a single integer as a string for equal intervals (e.g. "4"), or "[]" to disable reminders.

scheduled_auto_completed

boolean

Optional

Whether the incident is scheduled to automatically transition to completed at its scheduled end time.

scheduled_auto_in_progress

boolean

Optional

Whether the incident is scheduled to automatically transition to in_progress at its scheduled start time.

scheduled_for

string

Optional

The ISO 8601 timestamp the scheduled incident is scheduled to start.

scheduled_remind_prior

boolean

Optional

Whether to remind subscribers prior to the scheduled incident starting.

scheduled_until

string

Optional

The ISO 8601 timestamp the scheduled incident is scheduled to end.

status

string

Optional

The incident status. For realtime incidents, valid values are investigating, identified, monitoring, and resolved. For scheduled incidents, valid values are scheduled, in_progress, verifying, and completed.

statuspage_incident_update

Update incident

Update an existing incident or scheduled maintenance on a statuspage page, such as changing its status, posting a new update body, adjusting affected components, or modifying scheduling/notification settings.

Parameters

Name

Type

Required

Description

incident_id

string

Required

The identifier of the incident to update

page_id

string

Required

The identifier of the Statuspage page the incident belongs to

auto_transition_deliver_notifications_at_end

boolean

Optional

Whether to send a notification when the scheduled maintenance automatically transitions to completed.

auto_transition_deliver_notifications_at_start

boolean

Optional

Whether to send a notification when the scheduled maintenance automatically transitions to started.

auto_transition_to_maintenance_state

boolean

Optional

Whether to change affected components' status to under_maintenance once the scheduled maintenance is in progress.

auto_transition_to_operational_state

boolean

Optional

Whether to change affected components' status to operational once the scheduled maintenance completes.

auto_tweet_at_beginning

boolean

Optional

Whether to tweet automatically when the scheduled maintenance starts.

auto_tweet_on_completion

boolean

Optional

Whether to tweet automatically when the scheduled maintenance completes.

auto_tweet_on_creation

boolean

Optional

Whether to tweet automatically when the scheduled maintenance is created.

auto_tweet_one_hour_before

boolean

Optional

Whether to tweet automatically one hour before the scheduled maintenance starts.

backfill_date

string

Optional

Timestamp for when the incident was backfilled, in YYYY-MM-DD format.

backfilled

boolean

Optional

Whether the incident is backfilled (recorded after the fact). If true, components cannot be specified.

body

string

Optional

The initial message, created as the first incident update. Maximum length of 25000 characters.

component_ids

array

Optional

List of component IDs affected by this incident. Example: ["kctbh9vrtdwd", "lcy4z7wq3fjr"].

components

object

Optional

deliver_notifications

boolean

Optional

Whether to deliver notifications to subscribers. If false, the incident is created without notifying customers. Defaults to true.

impact_override

string

Optional

Value to override the calculated impact value. Valid values: none, maintenance, minor, major, critical.

metadata

object

Optional

Arbitrary JSON object attached to the incident. All top-level values in the object must also be objects, e.g. {"jira": {"issue_id": "ABC-123"}}.

name

string

Optional

Incident name. Maximum length of 255 characters.

reminder_intervals

string

Optional

scheduled_auto_completed

boolean

Optional

Whether the incident is scheduled to automatically transition to completed at its scheduled end time.

scheduled_auto_in_progress

boolean

Optional

Whether the incident is scheduled to automatically transition to in_progress at its scheduled start time.

scheduled_auto_transition

boolean

Optional

Same as scheduled_auto_in_progress. Controls whether the incident is scheduled to automatically change to in_progress.

scheduled_for

string

Optional

The ISO 8601 timestamp the scheduled incident is scheduled to start.

scheduled_remind_prior

boolean

Optional

Whether to remind subscribers prior to the scheduled incident starting.

scheduled_until

string

Optional

The ISO 8601 timestamp the scheduled incident is scheduled to end.

status

string

Optional

statuspage_incident_delete

Delete incident

statuspage_metric_data_add

Add metric data

statuspage_page_access_group_component_remove

Remove page access group component

statuspage_incidents_list

List incidents

statuspage_component_uptime_get

Get component uptime

statuspage_incident_postmortem_create

Create incident postmortem

statuspage_incident_update_edit

Incident update edit

statuspage_incident_postmortem_delete

Delete incident postmortem

statuspage_metrics_data_add_batch

Batch metrics data add

statuspage_page_access_user_component_remove

Remove page access user component

statuspage_incidents_list_active_maintenance

Incidents list active maintenance

statuspage_incident_get

Get incident

For more tools, view docs.

Build your Agent

Drop the toolkit in, point it at the tenant, and your agent can open an incident and post updates from the first run.

import { ScalekitClient } from "@scalekit-sdk/node";
import { DynamicStructuredTool } from "@langchain/core/tools";
import { createReactAgent } from "@langchain/langgraph/prebuilt";
import { z } from "zod";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["statuspage"], toolNames: ["statuspage_incidents_list", "statuspage_incident_create", "statuspage_component_update"] },
  pageSize: 100,
});

const lcTools = tools.map((t) => new DynamicStructuredTool({
  name: t.tool.definition.name,
  description: t.tool.definition.description,
  schema: z.object({}).passthrough(),
  func: async (args) => {
    const { data } = await sk.tools.executeTool({
      toolName: t.tool.definition.name,
      identifier: "user_123",
      params: args,
    });
    return JSON.stringify(data);
  },
}));

const agent = createReactAgent({ llm, tools: lcTools });

import { ScalekitClient } from "@scalekit-sdk/node";
import OpenAI from "openai";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["statuspage"], toolNames: ["statuspage_incidents_list", "statuspage_incident_create", "statuspage_component_update"] },
  pageSize: 100,
});

const llmTools = tools.map((t) => ({
  type: "function",
  function: {
    name: t.tool.definition.name,
    description: t.tool.definition.description,
    parameters: t.tool.definition.input_schema,
  },
}));

const resp = await openai.responses.create({
  model: "gpt-4o", input: prompt, tools: llmTools,
});

import { ScalekitClient } from "@scalekit-sdk/node";
import Anthropic from "@anthropic-ai/sdk";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["statuspage"], toolNames: ["statuspage_incidents_list", "statuspage_incident_create", "statuspage_component_update"] },
  pageSize: 100,
});

const llmTools = tools.map((t) => ({
  name: t.tool.definition.name,
  description: t.tool.definition.description,
  input_schema: t.tool.definition.input_schema,
}));

const msg = await anthropic.messages.create({
  model: "claude-sonnet-4-6", max_tokens: 1024,
  tools: llmTools,
  messages: [{ role: "user", content: prompt }],
});

import { Agent } from "@google/adk/agents";
import {
  MCPToolset, StreamableHTTPConnectionParams,
} from "@google/adk/tools/mcp";

const toolset = new MCPToolset({
  connectionParams: new StreamableHTTPConnectionParams({
    url: "https://mcp.scalekit.com/statuspage",
    headers: { Authorization: `Bearer ${userScopedToken}` },
  }),
});

const agent = new Agent({
  name: "agent", model: "gemini-2.0-flash",
  tools: await toolset.getTools(),
});

Try these prompts

Paste any prompt into your agent to start running Statuspage incident comms from your workflows.

Incident response

Copy the prompt

Copied

Open a partial outage on [component] and post an investigating update.

Copy the prompt

Copied

Move incident [inc_id] to identified and add the root cause we found.

Copy the prompt

Copied

Resolve [inc_id] and post the final summary.

Status hygiene

Copy the prompt

Copied

List components whose status is not operational right now.

Copy the prompt

Copied

Show uptime for [component_group] over the last 30 days.

Copy the prompt

Copied

Which components are missing from every component group?

Subscribers

Copy the prompt

Copied

How many subscribers are on [page_id] and by which channel?

Copy the prompt

Copied

List subscribers who signed up in the last 7 days.

Copy the prompt

Copied

Remove unconfirmed email subscribers older than 90 days.

SEE HOW AUTH WORKS

Your users connect once. Their Statuspage credentials stay vaulted, every call is scope-checked, and every action is logged.

Authorize

Your user connects

Statuspage

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

Store

Their

Statuspage

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

Resolve

When your agent calls a

Statuspage

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

Audit

Every

Statuspage

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

See the same per-user auth pattern across other connectors.

ENGINEERING

DevOps assistant agent

Poll GitHub for failing checks and stale pull requests, open Linear issues for the ones that need work, and digest to Slack.

ENGINEERING

Engineering standup agent

Pull commits from GitHub and GitLab, track Jira issue movement, and post a per-engineer standup brief to Slack.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

Other connector libraries treat auth as a demo afterthought. Scalekit starts with user identity, scope enforcement, and audit.

01.

Shared tokens break per-user analytics

A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential so attribution, audit, and scope stay accurate.

// shared token
audit → bot_service_account
user_filter → broken

// scalekit
audit → user_abc
scope → enforced ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

Statuspage today. Others tomorrow.

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does the agent access Statuspage as the user or as a shared key?

As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.

Where is the Statuspage API key stored?

In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.

Can I limit what the agent is allowed to do in Statuspage?

Yes. Pass a tool name filter to listScopedTools so the on-call agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Statuspage.

What happens when a user revokes Statuspage access?

The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Can the agent publish to our public status page by accident?

Not unless you expose the write tools. Incident create, update, and component status live in separate tools from the list and get tools, so a reporting agent stays read only. Every publish is scope-checked before the Statuspage call and logged with the acting user.

On this page

Tool and actions Framework Compatibility Starter Prompt Auth Lifecycle Try Other Agents Why Scalekit