How to connect Instatus to OpenClaw
Connect Instatus to OpenClaw with ClawLink: paste your Instatus key once and 15 tools work from chat. No MCP server to run, nothing stored on your machine.
InstatusAPI KEYMCPInstatus is a status page and incident communication platform for managing service health, incidents, maintenance, monitors, and subscribers.. Once connected, OpenClaw can read and act on Instatus from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Instatus access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Instatus setup: install one ClawHub skill, connect Instatus in the browser, and OpenClaw can call real Instatus actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect OpenClaw to Instatus.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Instatus
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Instatus?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect Instatus in the ClawLink dashboard — paste your Instatus API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from Instatus, summarize it in plain English, and point out anything that needs attention.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Instatus is connected in the dashboard, that agent calls the same 15 Instatus tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Instatus MCP for OpenClaw
Looking for a Instatus MCP server for OpenClaw? ClawLink connects Instatus to OpenClaw and exposes 15 Instatus tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Instatus integration works the same way.
What the OpenClaw Instatus integration can do
15 Instatus tools are ready for OpenClaw once the account is connected.
All 15 Instatus tools for OpenClaw
| Tool | What it does |
|---|---|
Get component instatus_get_component | Get the current health and configuration of one component on an Instatus status page |
Get incident instatus_get_incident | Get one Instatus incident with its affected components and update history |
Get maintenance instatus_get_maintenance | Get one Instatus maintenance with its schedule, affected components, automation settings, and |
List components instatus_list_components | List components and their current health for one Instatus status page, including child |
List incidents instatus_list_incidents | List incidents for an Instatus status page, optionally including or excluding lifecycle statuses |
List maintenances instatus_list_maintenances | List scheduled and historical maintenances for an Instatus status page |
List status pages instatus_list_status_pages | List status pages available to the connected Instatus account so an agent can discover page IDs |
Create component instatus_create_component | Create a component on an Instatus status page |
Update component instatus_update_component | Change a component's health or presentation on an Instatus status page |
Add incident update instatus_add_incident_update | Post a public lifecycle update to an Instatus incident and change affected component states |
Add maintenance update instatus_add_maintenance_update | Post a public progress update to an Instatus maintenance, optionally changing its lifecycle |
Create incident instatus_create_incident | Create an incident on an Instatus status page with optional affected component states |
Create maintenance instatus_create_maintenance | Schedule or start a maintenance on an Instatus status page |
Update incident instatus_update_incident | Edit an existing Instatus incident's name, timing, lifecycle status, affected components, or |
Update maintenance instatus_update_maintenance | Fully replace an Instatus maintenance's public message, schedule, lifecycle state, affected |
Try it: find the Instatus tool you need
Browse the 15 Instatus tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from Instatus, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Instatus, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Instatus, summarize it in plain English, and point out anything that needs attention.
List the relevant items in Instatus, group them by priority, and recommend what OpenClaw should do next.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Instatus working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Instatus API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Instatus account becomes available to the agent without you building credential management. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Instatus. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right Instatus actions to the runtime in a format your agent can reliably use. | 15 tools for Instatus are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Instatus to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Instatus in the browser, and the 15 tools above work from chat. There is no SDK and no config file, and the Instatus key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Instatus skill but can't call the tools
The ClawHub skill teaches OpenClaw about Instatus, but the calls run through the ClawLink plugin and your connected account. Make sure Instatus is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect Instatus from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling Instatus tools
Instatus tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Instatus call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
Instatus returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
API key setup works but results look incomplete
Double-check that the API key for Instatus has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw Instatus integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Instatus: link your Instatus account once in the browser and OpenClaw can call the Instatus API through 15 ready-made tools — no custom code or token handling.
How do I add Instatus to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Instatus skill from ClawHub, then you click Connect in the dashboard to authorize Instatus. OpenClaw calls the tools from the next message — no config files, and the Instatus key you paste is stored server-side instead of in your environment.
How long does it take to connect Instatus to OpenClaw?
About two minutes. Sign in, click Connect next to Instatus in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Instatus up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Instatus working from chat.
OpenClaw installed the Instatus skill but can't call the tools
The ClawHub skill teaches OpenClaw about Instatus, but the calls run through the ClawLink plugin and your connected account. Make sure Instatus is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Related
OpenClaw GitHub integration
Manage repositories, issues, pull requests, and workflows
PagerDuty
Manage incidents, on-call schedules, and services
SafetyCulture
SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.