Skip to content
Scalekit Docs
Talk to an Engineer Dashboard

Connect AI agents to Statuspage

Scalekit connector
Open markdown

The Statuspage connector lets your AI agent act in each user's Statuspage account. Each user connects their own Statuspage API key once, and Scalekit sends it with every call, so your agent never handles credentials. It comes with 99 tools.

Tools
99
What they doRead · write · destructive
38 · 39 · 2238 read39 write22 destructive
Users sign in with

Setup

  1. Install the SDK

    Terminal window
    npm install @scalekit-sdk/node dotenv
  2. Set your credentials

    Add your Scalekit credentials to your .env file. Find values in app.scalekit.com > Developers > API Credentials.

    .env
    SCALEKIT_ENVIRONMENT_URL=<your-environment-url>
    SCALEKIT_CLIENT_ID=<your-client-id>
    SCALEKIT_CLIENT_SECRET=<your-client-secret>
  3. Create the Statuspage connection

    In AgentKit > Connections, create a Statuspage connection. The name you give it is the connection_name your code passes. See Configure connections.

  4. Authorize a user and make your first call

    quickstart.mts
    import { ScalekitClient } from '@scalekit-sdk/node'
    import 'dotenv/config'
    import { createInterface } from 'node:readline/promises'
    const scalekit = new ScalekitClient(
    process.env.SCALEKIT_ENVIRONMENT_URL,
    process.env.SCALEKIT_CLIENT_ID,
    process.env.SCALEKIT_CLIENT_SECRET,
    )
    const actions = scalekit.actions
    const connector = 'statuspage'
    const identifier = 'user_123'
    // Generate an authorization link for the user
    const { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })
    console.log('Authorize Statuspage:', link)
    const rl = createInterface({ input: process.stdin, output: process.stdout })
    await rl.question('Press Enter after authorizing...')
    rl.close()
    // Make your first call
    const result = await actions.executeTool({
    connector,
    identifier,
    toolName: 'statuspage_pages_list',
    toolInput: {},
    })
    console.log(result)
    Terminal window
    npx tsx quickstart.mts

    Each user opens the link once and enters their Statuspage credentials there. See Authorize a user for the full flow and statuses.

Tools

Pass the exact name to execute_tool
Try in PlaygroundRequest a tool
  • statuspage_component_getRetrieve details of a single component on a Statuspage page by its component ID, including name, status, description, group, and display settings.Read-only

    Get Component

    Retrieve details of a single component on a Statuspage page by its component ID, including name, status, description, group, and display settings.

    Inputs

    component_idstringrequired
    The identifier of the component to retrieve
    page_idstringrequired
    The identifier of the Statuspage page the component belongs to
  • statuspage_component_group_getRetrieve details of a single component group on a Statuspage status page by its ID, including its name and the components it contains.Read-only

    Get Component Group

    Retrieve details of a single component group on a Statuspage status page by its ID, including its name and the components it contains.

    Inputs

    idstringrequired
    The identifier of the component group to retrieve
    page_idstringrequired
    The identifier of the Statuspage page the component group belongs to
  • statuspage_component_group_uptime_getGet uptime data for a component group that has uptime showcase enabled for at least one component.Read-only

    Get Component Group Uptime

    Get uptime data for a component group that has uptime showcase enabled for at least one component. Returns aggregate uptime data over a date range (maximum six calendar months) along with related events unless skipped.

    Inputs

    idstringrequired
    The identifier of the component group to retrieve uptime data for.
    page_idstringrequired
    The identifier of the Statuspage page the component group belongs to.
    endstring
    The end date for uptime calculation, e.g. '2024-06-30', '2024-06', or '2024'. Defaults to today in the page's time zone. Maximum supported range is six calendar months, earliest supported date is 1970-01-01.
    skip_related_eventsboolean
    If true, skips supplying the related events data along with the component group uptime data.
    startstring
    The start date for uptime calculation, e.g. '2024-01-01', '2024-01', or '2024'. Defaults to the date of the earliest component start_date in the group, or 90 days ago, whichever is more recent. Maximum supported range is six calendar months, earliest supported date is 1970-01-01.
  • statuspage_component_groups_listRetrieve a list of component groups on a Statuspage status page, with optional pagination.Read-only

    List Component Groups

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

    Inputs

    page_idstringrequired
    The identifier of the Statuspage page whose component groups should be listed
    pagenumber
    The page offset of component groups to fetch. The first page is 0, the second is 1, etc.
    per_pagenumber
    The number of results to return per page. Maximum and default of 100.
  • statuspage_component_uptime_getGet uptime data for a component that has uptime showcase enabled.Read-only

    Get Component Uptime

    Get uptime data for a component that has uptime showcase enabled. Returns uptime data over a date range (maximum six calendar months) along with related events unless skipped.

    Inputs

    component_idstringrequired
    The identifier of the component to retrieve uptime data for.
    page_idstringrequired
    The identifier of the Statuspage page the component belongs to.
    endstring
    The end date for uptime calculation, e.g. '2024-06-30', '2024-06', or '2024'. Defaults to today in the page's time zone. Maximum supported range is six calendar months, earliest supported date is 1970-01-01.
    skip_related_eventsboolean
    If true, skips supplying the related events data along with the component uptime data.
    startstring
    The start date for uptime calculation, e.g. '2024-01-01', '2024-01', or '2024'. Defaults to the component's start_date field or 90 days ago, whichever is more recent. Maximum supported range is six calendar months, earliest supported date is 1970-01-01.
  • statuspage_components_listRetrieve the list of components (services/parts of your infrastructure) configured on a Statuspage page, including their name, status, group, and description.Read-only

    List Components

    Retrieve the list of components (services/parts of your infrastructure) configured on a Statuspage page, including their name, status, group, and description. Supports pagination.

    Inputs

    page_idstringrequired
    The identifier of the Statuspage page whose components should be listed
    pageinteger
    Page offset to fetch, for paginating through results. Starts at 1.
    per_pageinteger
    Number of results to return per page. Maximum and default limit is 100.
  • statuspage_incident_getRetrieve details of a single incident on a Statuspage page by its incident ID, including status, impact, affected components, incident updates, and postmortem information.Read-only

    Get Incident

    Retrieve details of a single incident on a Statuspage page by its incident ID, including status, impact, affected components, incident updates, and postmortem information.

    Inputs

    incident_idstringrequired
    The identifier of the incident to retrieve
    page_idstringrequired
    The identifier of the Statuspage page the incident belongs to
  • statuspage_incident_postmortem_getRetrieve the postmortem for a Statuspage incident, including its draft/published body content and publish status.Read-only

    Get Incident Postmortem

    Retrieve the postmortem for a Statuspage incident, including its draft/published body content and publish status.

    Inputs

    incident_idstringrequired
    The identifier of the incident whose postmortem should be retrieved
    page_idstringrequired
    The identifier of the Statuspage page that owns the incident