# How to connect Toggl to OpenClaw (paste one key, 56 tools) > Connect Toggl to OpenClaw with ClawLink: paste your Toggl key once and 56 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/toggl The usual route to Toggl 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 Toggl setup: install one ClawHub skill, connect Toggl in the browser, and OpenClaw can call real Toggl 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 Toggl. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Toggl** — 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 toggl # connect Toggl (browser OAuth) npx -y @useclawlink/cli actions toggl # list available actions npx -y @useclawlink/cli run toggl --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 Toggl in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Toggl API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Toggl, 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 Toggl is connected in the dashboard, that agent calls the same 56 Toggl 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). ## Toggl MCP for OpenClaw Looking for a Toggl MCP server for OpenClaw? ClawLink connects Toggl to OpenClaw and exposes 56 Toggl 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 Toggl integration](https://claw-link.dev/hermes/toggl) works the same way. ## What the OpenClaw Toggl integration can do 56 Toggl 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 56. ### 30 of 56 Toggl tools for OpenClaw | Tool | What it does | |---|---| | **Get all plans** `toggl_get_all_plans` | Retrieve all available Toggl subscription plans and their features | | **Get client details** `toggl_get_client_details` | Retrieves detailed information about a specific client in Toggl Track by its client ID and | | **Get countries** `toggl_get_countries` | Retrieve all countries supported by Toggl | | **Get country subdivisions** `toggl_get_country_subdivisions` | Retrieve all subdivisions (states, provinces, regions) for a specific country in Toggl Track | | **Get currencies** `toggl_get_currencies` | Retrieve the list of all currencies supported by Toggl Track | | **Get current time entry** `toggl_get_current_time_entry` | Retrieves the currently running time entry for the authenticated user | | **Get event filters** `toggl_get_event_filters` | Retrieve the list of supported event filters for Toggl webhooks | | **Get keys** `toggl_get_keys` | Retrieves the current JWKS (JSON Web Key Set) keyset used to sign JWT tokens | | **Get list clients** `toggl_get_list_clients` | Retrieve a list of clients from a Toggl Track workspace with optional filtering by status and | | **Get my location** `toggl_get_my_location` | Retrieves the authenticated user's last known location information including city, state | | **Get my quota** `toggl_get_my_quota` | Retrieve API rate limit quota for the authenticated user | | **Get organization details** `toggl_get_organization_details` | Retrieves detailed information about a specific Toggl organization including subscription plan | | **Get organization groups** `toggl_get_organization_groups` | Retrieves all groups within a Toggl organization, including group members and workspace | | **Get organization users** `toggl_get_organization_users` | Retrieves a list of users belonging to a Toggl organization | | **Get project details** `toggl_get_project_details` | Retrieve details of a specific project | | **Get projects** `toggl_get_projects` | Retrieve a list of projects from a Toggl workspace | | **Get public subscription plans** `toggl_get_public_subscription_plans` | Retrieve all publicly available subscription plans from Toggl | | **Get status** `toggl_get_status` | Retrieve the Toggl Webhooks server status | | **Get tags** `toggl_get_tags` | Retrieve all tags in a Toggl workspace | | **Get tasks** `toggl_get_tasks` | List tasks in a workspace or within a specific project | | **Get time entries** `toggl_get_time_entries` | Retrieve time entries for the authenticated user with flexible filtering options | | **Get time entry** `toggl_get_time_entry` | Retrieve a specific time entry by its ID | | **Get timezone offsets** `toggl_get_timezone_offsets` | Retrieve all available timezone offsets from Toggl | | **Get timezones** `toggl_get_timezones` | Retrieve all available timezones supported by Toggl Track | | **Get user clients** `toggl_get_user_clients` | Retrieves all clients accessible to the authenticated user across all their workspaces | | **Get user preferences** `toggl_get_user_preferences` | Retrieves the authenticated user's preferences including timezone, date/time formats | | **Get user projects** `toggl_get_user_projects` | Retrieve all projects for the authenticated user | | **Get user tags** `toggl_get_user_tags` | Retrieve tags associated with the current user | | **Get user tasks** `toggl_get_user_tasks` | Retrieve all tasks across all workspaces accessible to the authenticated user | | **Get user workspaces** `toggl_get_user_workspaces` | Retrieve all workspaces the authenticated user belongs to | ## Example prompts **Get All Plans** > Pull the relevant data from Toggl, summarize it in plain English, and point out anything that needs attention. **Get Client Details** > Pull the relevant data from Toggl, summarize it in plain English, and point out anything that needs attention. **Get Countries** > Pull the relevant data from Toggl, summarize it in plain English, and point out anything that needs attention. **Get Country Subdivisions** > Pull the relevant data from Toggl, 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 Toggl working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Toggl API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Toggl 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 Toggl. | 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 Toggl actions to the runtime in a format your agent can reliably use. | 56 tools for Toggl are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Toggl 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 Toggl in the browser, and the 56 tools above work from chat. There is no SDK and no config file, and the Toggl 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 Toggl skill but can't call the tools The ClawHub skill teaches OpenClaw about Toggl, but the calls run through the ClawLink plugin and your connected account. Make sure Toggl 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 Toggl 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 Toggl tools Toggl 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 Toggl 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. ### Toggl 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 Toggl has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Toggl integration? Yes. ClawLink is the fastest way to connect OpenClaw to Toggl: link your Toggl account once in the browser and OpenClaw can call the Toggl API through 56 ready-made tools — no custom code or token handling. ### How do I add Toggl to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Toggl skill from ClawHub, then you click Connect in the dashboard to authorize Toggl. OpenClaw calls the tools from the next message — no config files, and the Toggl key you paste is stored server-side instead of in your environment. ### How long does it take to connect Toggl to OpenClaw? About two minutes. Sign in, click Connect next to Toggl in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Toggl 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 Toggl working from chat. ### OpenClaw installed the Toggl skill but can't call the tools The ClawHub skill teaches OpenClaw about Toggl, but the calls run through the ClawLink plugin and your connected account. Make sure Toggl 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 - [OpenClaw Moco integration](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