How to connect Clockify to OpenClaw
Connect Clockify to OpenClaw with ClawLink: paste your Clockify key once and 73 tools work from chat. No MCP server to run, nothing stored on your machine.
ClockifyAPI KEYMCPTrack time entries across projects, tasks, and clients. Once connected, OpenClaw can read and act on Clockify from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Clockify 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 Clockify setup: install one ClawHub skill, connect Clockify in the browser, and OpenClaw can call real Clockify 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 Clockify.
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 Clockify
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Clockify?"
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 Clockify in the ClawLink dashboard — paste your Clockify API key once.
Verify the connection by asking OpenClaw:
Use Clockify to filter workspace users 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 Clockify is connected in the dashboard, that agent calls the same 73 Clockify tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Clockify MCP for OpenClaw
Looking for a Clockify MCP server for OpenClaw? ClawLink connects Clockify to OpenClaw and exposes 73 Clockify tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Clockify integration works the same way.
What the OpenClaw Clockify integration can do
73 Clockify 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 73.
30 of 73 Clockify tools for OpenClaw
| Tool | What it does |
|---|---|
Filter workspace users clockify_filter_workspace_users | Filter users in a workspace by advanced criteria |
Find user team manager clockify_find_user_team_manager | Retrieves the list of team managers assigned to a specific user in a Clockify workspace |
Generate detailed report clockify_generate_detailed_report | Generate a detailed time entry report with filtering and pagination |
Generate expense report clockify_generate_expense_report | Generate a detailed expense report for a Clockify workspace |
Generate summary report clockify_generate_summary_report | Generate a summary report for time entries in a Clockify workspace |
Generate weekly report clockify_generate_weekly_report | Generate a weekly time entry report for a workspace with grouped data |
Get all addon webhooks clockify_get_all_addon_webhooks | List all webhooks for an addon in a workspace |
Get all my workspaces clockify_get_all_my_workspaces | List all workspaces the user belongs to |
Get all webhooks clockify_get_all_webhooks | List all webhooks in a workspace |
Get client by ID clockify_get_client_by_id | Retrieves detailed information about a specific client in a Clockify workspace |
Get clients clockify_get_clients | List clients in a workspace |
Get created entities clockify_get_created_entities | Retrieve created entities within a workspace (Experimental) |
Get currently logged in user info clockify_get_currently_logged_in_user_info | Retrieve info about the authenticated user |
Get deleted entities clockify_get_deleted_entities | Retrieve information about entities deleted within a date range (Experimental API) |
Get holidays clockify_get_holidays | Retrieve all holidays for a workspace |
Get holidays in period clockify_get_holidays_in_period | Retrieve holidays in a specific period |
Get in progress time entries clockify_get_in_progress_time_entries | Retrieve all currently running time entries in a workspace |
Get member profile clockify_get_member_profile | Get a member's profile in a workspace |
Get project clockify_get_project | Retrieve detailed information about a specific project by ID |
Get projects clockify_get_projects | List projects in a workspace with filtering and pagination |
Get shared report clockify_get_shared_report | Retrieve a shared report by ID from Clockify |
Get shared reports clockify_get_shared_reports | Retrieve all shared reports in a workspace |
Get tag clockify_get_tag | Retrieve detailed information about a specific tag by ID in a Clockify workspace |
Get tags clockify_get_tags | Find and list tags in a workspace |
Get task clockify_get_task | Retrieves detailed information about a specific task in a Clockify project |
Get tasks clockify_get_tasks | Find all tasks on a specific project in a workspace |
Get templates on workspace clockify_get_templates_on_workspace | List all templates in a workspace |
Get time entries clockify_get_time_entries | Retrieve historical time entries for a user in a workspace with filters |
Get time entry clockify_get_time_entry | Retrieve a specific time entry by ID from a workspace |
Get updated entities clockify_get_updated_entities | Retrieve entities that have been updated in a workspace (Experimental) |
Try it: find the Clockify tool you need
Browse the 30 Clockify tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use Clockify to filter workspace users and walk me through the result in plain English.
Use Clockify to find user team manager and walk me through the result in plain English.
Use Clockify to generate detailed report and walk me through the result in plain English.
Use Clockify to generate expense report and walk me through the result in plain English.
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 Clockify working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Clockify API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Clockify 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 Clockify. | 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 Clockify actions to the runtime in a format your agent can reliably use. | 73 tools for Clockify are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Clockify 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 Clockify in the browser, and the 73 tools above work from chat. There is no SDK and no config file, and the Clockify 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 Clockify skill but can't call the tools
The ClawHub skill teaches OpenClaw about Clockify, but the calls run through the ClawLink plugin and your connected account. Make sure Clockify 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 Clockify 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 Clockify tools
Clockify 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 Clockify 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.
Clockify 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 Clockify 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 Clockify integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Clockify: link your Clockify account once in the browser and OpenClaw can call the Clockify API through 73 ready-made tools — no custom code or token handling.
How do I add Clockify to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Clockify skill from ClawHub, then you click Connect in the dashboard to authorize Clockify. OpenClaw calls the tools from the next message — no config files, and the Clockify key you paste is stored server-side instead of in your environment.
How long does it take to connect Clockify to OpenClaw?
About two minutes. Sign in, click Connect next to Clockify in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Clockify 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 Clockify working from chat.
OpenClaw installed the Clockify skill but can't call the tools
The ClawHub skill teaches OpenClaw about Clockify, but the calls run through the ClawLink plugin and your connected account. Make sure Clockify 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.
