How to connect Nozbe Teams to OpenClaw
Connect Nozbe Teams to OpenClaw with ClawLink: paste your Nozbe Teams key once and 48 tools work from chat. No MCP server to run, nothing stored on your machine.
Nozbe TeamsAPI KEYMCPCloud-based task management tool helping individuals and teams get organized.. Once connected, OpenClaw can read and act on Nozbe Teams from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Nozbe Teams 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 Nozbe Teams setup: install one ClawHub skill, connect Nozbe Teams in the browser, and OpenClaw can call real Nozbe Teams 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 Nozbe Teams.
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 Nozbe Teams
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Nozbe Teams?"
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 Nozbe Teams in the ClawLink dashboard — paste your Nozbe Teams API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from Nozbe Teams, 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 Nozbe Teams is connected in the dashboard, that agent calls the same 48 Nozbe Teams tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Nozbe Teams MCP for OpenClaw
Looking for a Nozbe Teams MCP server for OpenClaw? ClawLink connects Nozbe Teams to OpenClaw and exposes 48 Nozbe Teams tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Nozbe Teams integration works the same way.
What the OpenClaw Nozbe Teams integration can do
48 Nozbe Teams 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 48.
30 of 48 Nozbe Teams tools for OpenClaw
| Tool | What it does |
|---|---|
Get attachment nozbe_teams_get_attachment | Get attachment metadata by its ID |
Get comment nozbe_teams_get_comment | Retrieve a comment by its ID from Nozbe Teams |
Get project nozbe_teams_get_project | Retrieve a project by its ID from Nozbe Teams |
Get project access nozbe_teams_get_project_access | Retrieve project access details by ID |
Get project section nozbe_teams_get_project_section | Retrieve a project section by ID from Nozbe Teams |
Get reminder nozbe_teams_get_reminder | Get a reminder by ID from Nozbe Teams |
Get tag nozbe_teams_get_tag | Get a tag by ID from Nozbe Teams |
Get tag assignment nozbe_teams_get_tag_assignment | Retrieve a tag assignment by its ID |
Get task nozbe_teams_get_task | Retrieve a task by its ID from Nozbe Teams |
Get task event nozbe_teams_get_task_event | Get a task event by ID |
Get team nozbe_teams_get_team | Retrieve a team by its ID from Nozbe Teams |
Get team member nozbe_teams_get_team_member | Retrieve a team member by ID from Nozbe Teams |
Get user nozbe_teams_get_user | Retrieve a user by their ID from Nozbe Teams |
List attachments nozbe_teams_list_attachments | Get all attachments related to a specific comment in Nozbe Teams |
List comments nozbe_teams_list_comments | Get accessible comments with optional filtering by task_id and pagination support |
List group assignments nozbe_teams_list_group_assignments | Get accessible group assignments from Nozbe Teams |
List project accesses nozbe_teams_list_project_accesses | Get accessible project accesses in Nozbe Teams |
List project groups nozbe_teams_list_project_groups | Get accessible project groups from Nozbe Teams |
List project sections nozbe_teams_list_project_sections | Retrieve accessible project sections with optional filtering |
List projects nozbe_teams_list_projects | Retrieve accessible projects with optional filtering |
List reminders nozbe_teams_list_reminders | Get accessible reminders from Nozbe Teams |
List tag assignments nozbe_teams_list_tag_assignments | Get accessible tag assignments with optional filtering by tag_id or task_id |
List tags nozbe_teams_list_tags | Get accessible tags from Nozbe Teams |
List task events nozbe_teams_list_task_events | Get accessible task events from Nozbe Teams |
List tasks nozbe_teams_list_tasks | Retrieve accessible tasks from Nozbe Teams |
List users nozbe_teams_list_users | Retrieve accessible users from Nozbe Teams |
Poll new tasks nozbe_teams_poll_new_tasks | Poll for new tasks created since the last call |
Poll updated tasks nozbe_teams_poll_updated_tasks | Poll for tasks that have been updated since the last call |
Create attachment nozbe_teams_create_attachment | Add attachment metadata to a comment |
Create comment nozbe_teams_create_comment | Add a comment to a task in Nozbe Teams |
Try it: find the Nozbe Teams tool you need
Browse the 30 Nozbe Teams 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 Nozbe Teams, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Nozbe Teams, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Nozbe Teams, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Nozbe Teams, 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 Nozbe Teams working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Nozbe Teams API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Nozbe Teams 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 Nozbe Teams. | 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 Nozbe Teams actions to the runtime in a format your agent can reliably use. | 48 tools for Nozbe Teams are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Nozbe Teams 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 Nozbe Teams in the browser, and the 48 tools above work from chat. There is no SDK and no config file, and the Nozbe Teams 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 Nozbe Teams skill but can't call the tools
The ClawHub skill teaches OpenClaw about Nozbe Teams, but the calls run through the ClawLink plugin and your connected account. Make sure Nozbe Teams 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 Nozbe Teams 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 Nozbe Teams tools
Nozbe Teams 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 Nozbe Teams 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.
Nozbe Teams 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 Nozbe Teams 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 Nozbe Teams integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Nozbe Teams: link your Nozbe Teams account once in the browser and OpenClaw can call the Nozbe Teams API through 48 ready-made tools — no custom code or token handling.
How do I add Nozbe Teams to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Nozbe Teams skill from ClawHub, then you click Connect in the dashboard to authorize Nozbe Teams. OpenClaw calls the tools from the next message — no config files, and the Nozbe Teams key you paste is stored server-side instead of in your environment.
How long does it take to connect Nozbe Teams to OpenClaw?
About two minutes. Sign in, click Connect next to Nozbe Teams in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Nozbe Teams 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 Nozbe Teams working from chat.
OpenClaw installed the Nozbe Teams skill but can't call the tools
The ClawHub skill teaches OpenClaw about Nozbe Teams, but the calls run through the ClawLink plugin and your connected account. Make sure Nozbe Teams 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.
