# How to connect incident.io to OpenClaw (paste one key, 86 tools) > Connect incident.io to OpenClaw with ClawLink: paste your incident.io key once and 86 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/incident-io The usual route to incident.io 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 incident.io setup: install one ClawHub skill, connect incident.io in the browser, and OpenClaw can call real incident.io 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 incident.io. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect incident.io** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect incident-io # connect incident.io (browser OAuth) npx -y @useclawlink/cli actions incident-io # list available actions npx -y @useclawlink/cli run incident-io --input '' # execute (add --confirm for writes) ``` ### 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: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then 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 incident.io in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your incident.io API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from incident.io, 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: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once incident.io is connected in the dashboard, that agent calls the same 86 incident.io tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## incident.io MCP for OpenClaw Looking for a incident.io MCP server for OpenClaw? ClawLink connects incident.io to OpenClaw and exposes 86 incident.io tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes incident.io integration](https://claw-link.dev/hermes/incident-io) works the same way. ## What the OpenClaw incident.io integration can do 86 incident.io tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 86. ### 30 of 86 incident.io tools for OpenClaw | Tool | What it does | |---|---| | **Get alert attributes v2** `incident_io_get_alert_attributes_v2` | Retrieve a specific alert attribute by its ID from incident.io | | **Get alert routes v2** `incident_io_get_alert_routes_v2` | Retrieve a specific alert route configuration by its ID from incident.io | | **Get alert sources v2** `incident_io_get_alert_sources_v2` | Retrieve a specific alert source by its ID from incident.io | | **Get catalog entry v3** `incident_io_get_catalog_entry_v3` | Retrieve a specific catalog entry by ID from incident.io | | **Get catalog types v3** `incident_io_get_catalog_types_v3` | Retrieve a specific catalog type by ID from incident.io V3 API | | **Get custom field options v1** `incident_io_get_custom_field_options_v1` | Retrieve a specific custom field option by its ID | | **Get custom field v1** `incident_io_get_custom_field_v1` | Retrieve details of a specific custom field by ID in incident.io | | **Get custom field v2** `incident_io_get_custom_field_v2` | Retrieve details of a specific custom field by ID using the V2 API in incident.io | | **Get escalations v2** `incident_io_get_escalations_v2` | Retrieve a specific escalation by ID from incident.io | | **Get incident roles v2** `incident_io_get_incident_roles_v2` | Retrieve a specific incident role by ID using V2 API | | **Get incident status** `incident_io_get_incident_status` | Retrieve details of a specific incident status by ID | | **Get incident timestamps v2** `incident_io_get_incident_timestamps_v2` | Retrieve a specific incident timestamp by ID using V2 API | | **Get incident type** `incident_io_get_incident_type` | Retrieve detailed information about a specific incident type by ID | | **Get incident v2** `incident_io_get_incident_v2` | Retrieve a specific incident by ID using V2 API | | **Get schedules v2** `incident_io_get_schedules_v2` | Retrieve a specific schedule by ID from incident.io using V2 API | | **Get severities v1** `incident_io_get_severities_v1` | Retrieve a specific severity by ID from incident.io | | **Get users v2** `incident_io_get_users_v2` | Retrieve a specific user by ID from incident.io using V2 API | | **Get workflows v2** `incident_io_get_workflows_v2` | Retrieve a specific workflow by ID from incident.io | | **List actions v1** `incident_io_list_actions_v1` | List actions from incidents | | **List actions v2** `incident_io_list_actions_v2` | Retrieve a list of actions from incident.io | | **List alert attributes v2** `incident_io_list_alert_attributes_v2` | List all available alert attributes | | **List alert routes v2** `incident_io_list_alert_routes_v2` | List alert routes from incident.io | | **List alert sources v2** `incident_io_list_alert_sources_v2` | List all configured alert sources in incident.io | | **List alerts v2** `incident_io_list_alerts_v2` | List alerts from incident.io | | **List catalog entries v3** `incident_io_list_catalog_entries_v3` | List entries from a catalog type in incident.io | | **List catalog resources v3** `incident_io_list_catalog_resources_v3` | Retrieve all available catalog resource types from the V3 API | | **List catalog types v3** `incident_io_list_catalog_types_v3` | Retrieve all catalog types configured for an organization using V3 API | | **List escalation paths v2** `incident_io_list_escalation_paths_v2` | List escalation paths from incident.io | | **List escalations v2** `incident_io_list_escalations_v2` | List escalations from incident.io | | **List follow ups v2** `incident_io_list_follow_ups_v2` | Retrieve a list of follow-ups from incident.io | ## Example prompts **Get Alert Attributes V2** > Pull the relevant data from incident.io, summarize it in plain English, and point out anything that needs attention. **Get Alert Routes V2** > Pull the relevant data from incident.io, summarize it in plain English, and point out anything that needs attention. **Get Alert Sources V2** > Pull the relevant data from incident.io, summarize it in plain English, and point out anything that needs attention. **Get Catalog Entry V3** > Pull the relevant data from incident.io, summarize it in plain English, and point out anything that needs attention. ## 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 incident.io working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the incident.io API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected incident.io 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 incident.io. | 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 incident.io actions to the runtime in a format your agent can reliably use. | 86 tools for incident.io are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes incident.io 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 incident.io in the browser, and the 86 tools above work from chat. There is no SDK and no config file, and the incident.io key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the incident.io skill but can't call the tools The ClawHub skill teaches OpenClaw about incident.io, but the calls run through the ClawLink plugin and your connected account. Make sure incident.io 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 incident.io 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 incident.io tools incident.io 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 incident.io 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. ### incident.io 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 incident.io has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw incident.io integration? Yes. ClawLink is the fastest way to connect OpenClaw to incident.io: link your incident.io account once in the browser and OpenClaw can call the incident.io API through 86 ready-made tools — no custom code or token handling. ### How do I add incident.io to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink incident.io skill from ClawHub, then you click Connect in the dashboard to authorize incident.io. OpenClaw calls the tools from the next message — no config files, and the incident.io key you paste is stored server-side instead of in your environment. ### How long does it take to connect incident.io to OpenClaw? About two minutes. Sign in, click Connect next to incident.io in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring incident.io 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 incident.io working from chat. ### OpenClaw installed the incident.io skill but can't call the tools The ClawHub skill teaches OpenClaw about incident.io, but the calls run through the ClawLink plugin and your connected account. Make sure incident.io 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](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [OpenClaw PagerDuty integration](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [SafetyCulture](https://claw-link.dev/openclaw/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.