# How to connect iLert to OpenClaw (paste one key, 8 tools) > Connect iLert to OpenClaw with ClawLink: paste your iLert key once and 8 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/ilert The usual route to iLert 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 iLert setup: install one ClawHub skill, connect iLert in the browser, and OpenClaw can call real iLert 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 iLert. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect iLert** — 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 ilert # connect iLert (browser OAuth) npx -y @useclawlink/cli actions ilert # list available actions npx -y @useclawlink/cli run ilert --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 iLert in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your iLert API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from iLert, 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 iLert is connected in the dashboard, that agent calls the same 8 iLert 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). ## iLert MCP for OpenClaw Looking for a iLert MCP server for OpenClaw? ClawLink connects iLert to OpenClaw and exposes 8 iLert 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 iLert integration](https://claw-link.dev/hermes/ilert) works the same way. ## What the OpenClaw iLert integration can do 8 iLert tools are ready for OpenClaw once the account is connected. ### All 8 iLert tools for OpenClaw | Tool | What it does | |---|---| | **Get alert** `ilert_get_alert` | Get one iLert alert by its numeric ID, optionally expanding escalation rules, the next | | **Get current user** `ilert_get_current_user` | Return the authenticated iLert user, including identity, role, timezone, and active team context | | **Get incident** `ilert_get_incident` | Get one iLert status incident by numeric ID, optionally including subscription state, affected | | **List alerts** `ilert_list_alerts` | List iLert alerts with optional state, source, escalation-policy, responder, and report-time | | **List incidents** `ilert_list_incidents` | List iLert status incidents with optional lifecycle-state, affected-service, and report-time | | **List on calls** `ilert_list_on_calls` | Find who is on call for selected escalation policies, schedules, users, and a time window of at | | **List resources** `ilert_list_resources` | List one incident-response resource catalog: services, teams, escalation policies, or | | **List schedules** `ilert_list_schedules` | List iLert on-call schedules, optionally expanding current or next shifts and schedule | ## Example prompts **Get Alert** > Pull the relevant data from iLert, summarize it in plain English, and point out anything that needs attention. **Get Current User** > Pull the relevant data from iLert, summarize it in plain English, and point out anything that needs attention. **Get Incident** > Pull the relevant data from iLert, summarize it in plain English, and point out anything that needs attention. **List Alerts** > List the relevant items in iLert, 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 iLert working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the iLert API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected iLert 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 iLert. | 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 iLert actions to the runtime in a format your agent can reliably use. | 8 tools for iLert are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes iLert 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 iLert in the browser, and the 8 tools above work from chat. There is no SDK and no config file, and the iLert 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 iLert skill but can't call the tools The ClawHub skill teaches OpenClaw about iLert, but the calls run through the ClawLink plugin and your connected account. Make sure iLert 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 iLert 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 iLert tools iLert 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 iLert 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. ### iLert 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 iLert has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw iLert integration? Yes. ClawLink is the fastest way to connect OpenClaw to iLert: link your iLert account once in the browser and OpenClaw can call the iLert API through 8 ready-made tools — no custom code or token handling. ### How do I add iLert to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink iLert skill from ClawHub, then you click Connect in the dashboard to authorize iLert. OpenClaw calls the tools from the next message — no config files, and the iLert key you paste is stored server-side instead of in your environment. ### How long does it take to connect iLert to OpenClaw? About two minutes. Sign in, click Connect next to iLert in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring iLert 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 iLert working from chat. ### OpenClaw installed the iLert skill but can't call the tools The ClawHub skill teaches OpenClaw about iLert, but the calls run through the ClawLink plugin and your connected account. Make sure iLert 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 - [Connect GitHub](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [PagerDuty tools](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [SafetyCulture tools](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.