# How to connect Inistate to OpenClaw (paste one key, 12 tools) > Connect Inistate to OpenClaw with ClawLink: paste your Inistate key once and 12 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/inistate The usual route to Inistate 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 Inistate setup: install one ClawHub skill, connect Inistate in the browser, and OpenClaw can call real Inistate 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 Inistate. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Inistate** — 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 inistate # connect Inistate (browser OAuth) npx -y @useclawlink/cli actions inistate # list available actions npx -y @useclawlink/cli run inistate --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 Inistate in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Inistate API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Inistate, 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 Inistate is connected in the dashboard, that agent calls the same 12 Inistate 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). ## Inistate MCP for OpenClaw Looking for a Inistate MCP server for OpenClaw? ClawLink connects Inistate to OpenClaw and exposes 12 Inistate 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 Inistate integration](https://claw-link.dev/hermes/inistate) works the same way. ## What the OpenClaw Inistate integration can do 12 Inistate tools are ready for OpenClaw once the account is connected. ### All 12 Inistate tools for OpenClaw | Tool | What it does | |---|---| | **Get activity form** `inistate_get_activity_form` | Get the required fields, current values, options, defaults, and confidence threshold for a | | **Get entry** `inistate_get_entry` | Get one module record by ID, including its current values, state, audit metadata, and available | | **Get entry history** `inistate_get_entry_history` | Return one chronological 50-item page of a record's audit trail, comments, field changes, and | | **Get module schema** `inistate_get_module_schema` | Get a module's fields and states, optionally including its activities and flows, before | | **List entries** `inistate_list_entries` | Return one page of records from a module using a saved listing, field filters, search, sorting | | **List modules** `inistate_list_modules` | List modules available in a workspace so their exact names can be used in schema and record | | **List workspaces** `inistate_list_workspaces` | List workspaces accessible to the connected API key, optionally filtering by workspace name | | **Bulk change entry states** `inistate_bulk_change_entry_states` | Request state transitions for 1-100 entries in one module | | **Bulk update entries** `inistate_bulk_update_entries` | Update fields on 1-100 entries in one module | | **Change entry state** `inistate_change_entry_state` | Request a state transition for one module record; low confidence can flag the result and | | **Create entry** `inistate_create_entry` | Create one record in a module through its create activity and return whether low confidence | | **Update entry** `inistate_update_entry` | Update fields on one existing module record through its edit activity and return whether low | ## Example prompts **Get Activity Form** > Pull the relevant data from Inistate, summarize it in plain English, and point out anything that needs attention. **Get Entry** > Pull the relevant data from Inistate, summarize it in plain English, and point out anything that needs attention. **Get Entry History** > Pull the relevant data from Inistate, summarize it in plain English, and point out anything that needs attention. **Get Module Schema** > Pull the relevant data from Inistate, 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 Inistate working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Inistate API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Inistate 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 Inistate. | 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 Inistate actions to the runtime in a format your agent can reliably use. | 12 tools for Inistate are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Inistate 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 Inistate in the browser, and the 12 tools above work from chat. There is no SDK and no config file, and the Inistate 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 Inistate skill but can't call the tools The ClawHub skill teaches OpenClaw about Inistate, but the calls run through the ClawLink plugin and your connected account. Make sure Inistate 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 Inistate 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 Inistate tools Inistate 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 Inistate 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. ### Inistate 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 Inistate has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Inistate integration? Yes. ClawLink is the fastest way to connect OpenClaw to Inistate: link your Inistate account once in the browser and OpenClaw can call the Inistate API through 12 ready-made tools — no custom code or token handling. ### How do I add Inistate to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Inistate skill from ClawHub, then you click Connect in the dashboard to authorize Inistate. OpenClaw calls the tools from the next message — no config files, and the Inistate key you paste is stored server-side instead of in your environment. ### How long does it take to connect Inistate to OpenClaw? About two minutes. Sign in, click Connect next to Inistate in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Inistate 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 Inistate working from chat. ### OpenClaw installed the Inistate skill but can't call the tools The ClawHub skill teaches OpenClaw about Inistate, but the calls run through the ClawLink plugin and your connected account. Make sure Inistate 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 - [Trello](https://claw-link.dev/openclaw/trello) — Manage boards, lists, and cards - [Moco](https://claw-link.dev/openclaw/moco) — MOCO is a business management software offering project management, time tracking, and invoicing solutions. - [ClickUp](https://claw-link.dev/openclaw/clickup) — Manage tasks, docs, goals, and sprints