How to connect Nango to OpenClaw
Connect Nango to OpenClaw with ClawLink: paste your Nango key once and 24 tools work from chat. No MCP server to run, nothing stored on your machine.
NangoAPI KEYMCPNango provides a unified API to integrate with over 250 external APIs, offering pre-built and customizable integrations for various categories such as CRM, HR, and accounting systems.. Once connected, OpenClaw can read and act on Nango from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Nango 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 Nango setup: install one ClawHub skill, connect Nango in the browser, and OpenClaw can call real Nango 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 Nango.
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 Nango
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Nango?"
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 Nango in the ClawLink dashboard — paste your Nango API key once.
Verify the connection by asking OpenClaw:
Use Nango to connection get and walk me through the result in plain English.
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 Nango is connected in the dashboard, that agent calls the same 24 Nango tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Nango MCP for OpenClaw
Looking for a Nango MCP server for OpenClaw? ClawLink connects Nango to OpenClaw and exposes 24 Nango tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Nango integration works the same way.
What the OpenClaw Nango integration can do
24 Nango tools are ready for OpenClaw once the account is connected. The 22 below are the ones people reach for most; your agent can call all 24.
22 of 24 Nango tools for OpenClaw
| Tool | What it does |
|---|---|
Connection get nango_connection_get | List all Nango connections without credentials |
Get connection nango_get_connection | Retrieve a specific connection with its credentials |
Get environment variables nango_get_environment_variables | Retrieve environment variables from the Nango dashboard |
Get integration nango_get_integration | Retrieve detailed configuration for a specific Nango integration by its unique key |
Get proxy nango_get_proxy | Make a GET request with Nango's Proxy to forward requests to external APIs while managing |
Get sync status nango_get_sync_status | Get the status of specified sync(s) for a connection or all connections |
List connections nango_list_connections | List all connections without credentials |
List integrations nango_list_integrations | Retrieve a list of all configured integrations |
Providers get get nango_providers_get_get | Retrieve detailed configuration for a specific Nango provider by its unique key |
Providers list get nango_providers_list_get | Retrieve a list of all available providers |
Scripts config get nango_scripts_config_get | Retrieve all integration functions configuration from Nango |
Action trigger post nango_action_trigger_post | Trigger a Nango action to execute a workflow or operation |
Add connection nango_add_connection | Add a connection with existing credentials to Nango |
Create connect session nango_create_connect_session | Create a new connect session with a 30-minute lifespan for enabling connection creation via |
Create integration nango_create_integration | Create a new integration in Nango |
Edit connection nango_edit_connection | Edit a connection's tags and metadata |
Put proxy nango_put_proxy | Make a PUT request with the Nango Proxy to forward requests to external APIs while managing |
Reconnect session post nango_reconnect_session_post | Create a new connect session to reconnect to a specific integration |
Set connection metadata nango_set_connection_metadata | Set custom metadata for one or more Nango connections |
Sync trigger post nango_sync_trigger_post | Trigger sync process(es) manually |
Update connection metadata nango_update_connection_metadata | Edit custom metadata for one or multiple connections |
Update integration nango_update_integration | Update an existing integration's configuration |
Try it: find the Nango tool you need
Browse the 22 Nango tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use Nango to connection get and walk me through the result in plain English.
Pull the relevant data from Nango, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Nango, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Nango, 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 Nango working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Nango API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Nango 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 Nango. | 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 Nango actions to the runtime in a format your agent can reliably use. | 24 tools for Nango are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Nango 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 Nango in the browser, and the 24 tools above work from chat. There is no SDK and no config file, and the Nango 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 Nango skill but can't call the tools
The ClawHub skill teaches OpenClaw about Nango, but the calls run through the ClawLink plugin and your connected account. Make sure Nango 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 Nango 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 Nango tools
Nango 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 Nango 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.
Nango 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 Nango 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 Nango integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Nango: link your Nango account once in the browser and OpenClaw can call the Nango API through 24 ready-made tools — no custom code or token handling.
How do I add Nango to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Nango skill from ClawHub, then you click Connect in the dashboard to authorize Nango. OpenClaw calls the tools from the next message — no config files, and the Nango key you paste is stored server-side instead of in your environment.
How long does it take to connect Nango to OpenClaw?
About two minutes. Sign in, click Connect next to Nango in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Nango 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 Nango working from chat.
OpenClaw installed the Nango skill but can't call the tools
The ClawHub skill teaches OpenClaw about Nango, but the calls run through the ClawLink plugin and your connected account. Make sure Nango 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.