How to connect Northflank to OpenClaw
Connect Northflank to OpenClaw with ClawLink: paste your Northflank key once and 20 tools work from chat. No MCP server to run, nothing stored on your machine.
NorthflankAPI KEYMCPThe self-service developer platform that automates and unifies deployment of any workload, on any cloud, at any scale.. Once connected, OpenClaw can read and act on Northflank from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Northflank 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 Northflank setup: install one ClawHub skill, connect Northflank in the browser, and OpenClaw can call real Northflank 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 Northflank.
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 Northflank
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Northflank?"
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 Northflank in the ClawLink dashboard — paste your Northflank API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from Northflank, 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 Northflank is connected in the dashboard, that agent calls the same 20 Northflank tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Northflank MCP for OpenClaw
Looking for a Northflank MCP server for OpenClaw? ClawLink connects Northflank to OpenClaw and exposes 20 Northflank tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Northflank integration works the same way.
What the OpenClaw Northflank integration can do
20 Northflank tools are ready for OpenClaw once the account is connected. The 19 below are the ones people reach for most; your agent can call all 20.
19 of 20 Northflank tools for OpenClaw
| Tool | What it does |
|---|---|
Get dns ID northflank_get_dns_id | Retrieve the DNS identifier for the authenticated account |
Get project northflank_get_project | Retrieve detailed information about a specific Northflank project |
Get secret northflank_get_secret | Retrieve a secret from a Northflank project including its contents |
Get secret details northflank_get_secret_details | View a secret with details about its linked addons from a Northflank project |
List addon types northflank_list_addon_types | Retrieve information about available addon types in Northflank |
List cloud provider node types northflank_list_cloud_provider_node_types | Retrieve supported cloud provider node types available on Northflank |
List cloud provider regions northflank_list_cloud_provider_regions | Retrieve supported cloud provider regions available on Northflank |
List pipelines northflank_list_pipelines | List all pipelines for a Northflank project |
List plans northflank_list_plans | Retrieve available billing/resource plans in Northflank |
List projects northflank_list_projects | List all projects in your Northflank team with pagination support |
List regions northflank_list_regions | Retrieve available project regions in Northflank |
List secrets northflank_list_secrets | List all secrets belonging to a Northflank project |
List services northflank_list_services | List all services belonging to a Northflank project |
Create or update project northflank_create_or_update_project | Create a new project or update an existing project in Northflank (upsert operation) |
Create or update secret northflank_create_or_update_secret | Create or update a secret group in a Northflank project |
Create secret northflank_create_secret | Create a secret group in a Northflank project |
Patch secret northflank_patch_secret | Partially update a secret group in a Northflank project |
Update project northflank_update_project | Update a project in Northflank |
Update secret northflank_update_secret | Update a secret in a Northflank project |
Try it: find the Northflank tool you need
Browse the 19 Northflank 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 Northflank, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Northflank, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Northflank, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Northflank, 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 Northflank working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Northflank API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Northflank 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 Northflank. | 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 Northflank actions to the runtime in a format your agent can reliably use. | 20 tools for Northflank are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Northflank 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 Northflank in the browser, and the 20 tools above work from chat. There is no SDK and no config file, and the Northflank 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 Northflank skill but can't call the tools
The ClawHub skill teaches OpenClaw about Northflank, but the calls run through the ClawLink plugin and your connected account. Make sure Northflank 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 Northflank 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 Northflank tools
Northflank 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 Northflank 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.
Northflank 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 Northflank 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 Northflank integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Northflank: link your Northflank account once in the browser and OpenClaw can call the Northflank API through 20 ready-made tools — no custom code or token handling.
How do I add Northflank to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Northflank skill from ClawHub, then you click Connect in the dashboard to authorize Northflank. OpenClaw calls the tools from the next message — no config files, and the Northflank key you paste is stored server-side instead of in your environment.
How long does it take to connect Northflank to OpenClaw?
About two minutes. Sign in, click Connect next to Northflank in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Northflank 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 Northflank working from chat.
OpenClaw installed the Northflank skill but can't call the tools
The ClawHub skill teaches OpenClaw about Northflank, but the calls run through the ClawLink plugin and your connected account. Make sure Northflank 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 tools
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.