How to connect Ticktick to OpenClaw
Connect Ticktick to OpenClaw with ClawLink in one click — 13 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup.


Manage tasks, habits, calendars, and to-do lists. Once connected, OpenClaw can read and act on Ticktick from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Ticktick 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 Ticktick setup: install one ClawHub skill, connect Ticktick in the browser, and OpenClaw can call real Ticktick actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into OpenClaw, or open the Ticktick skill on ClawHub.
Before installing anything, inspect the ClawHub skill metadata and setup requirements.
If the skill asks you to install a third-party package or CLI, verify its source, maintainer, and package contents before running the install command.
Install the skill "Ticktick" (hith3sh/ticktick) from ClawHub only after those checks pass.
Skill page: https://clawhub.ai/hith3sh/ticktick
Keep the work scoped to this skill only.
After install, help me finish setup from verified skill metadata.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.Setup
It takes three steps to connect OpenClaw to Ticktick.
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 Ticktick
One-click OAuth in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Ticktick?"
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 Ticktick in the ClawLink dashboard — a one-click OAuth approval, no API keys.
Verify the connection by asking OpenClaw:
Pull the relevant data from Ticktick, 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 Ticktick is connected in the dashboard, that agent calls the same 13 Ticktick tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Ticktick MCP for OpenClaw
Looking for a Ticktick MCP server for OpenClaw? ClawLink connects Ticktick to OpenClaw and exposes 13 Ticktick tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Ticktick integration works the same way.
What the OpenClaw Ticktick integration can do
13 Ticktick tools are ready for OpenClaw once the account is connected. The 11 below are the ones people reach for most; your agent can call all 13.
11 of 13 Ticktick tools for OpenClaw
| Tool | What it does |
|---|---|
Get project by ID ticktick_get_project_by_id | Retrieve a specific TickTick project by its unique ID |
Get project with data ticktick_get_project_with_data | Retrieve a project's associated data (incomplete tasks, columns) |
Get task by project and ID ticktick_get_task_by_project_and_id | Retrieve a specific TickTick task by project ID and task ID |
Get user project ticktick_get_user_project | Retrieves all projects accessible to the authenticated user, including personal and shared |
List all tasks ticktick_list_all_tasks | List all open/undone tasks across all user projects in one call |
Oauth2 authorization step1 ticktick_oauth2_authorization_step1 | Generate the TickTick OAuth2 authorization URL |
Complete task ticktick_complete_task | Marks a TickTick task as complete |
Create project ticktick_create_project | Create a new project (list) in TickTick |
Create task ticktick_create_task | Create a new task in TickTick |
Update project ticktick_update_project | Update an existing project |
Update task ticktick_update_task | Update an existing task |
Try it: find the Ticktick tool you need
Browse the 11 Ticktick 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 Ticktick, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Ticktick, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Ticktick, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Ticktick, summarize it in plain English, and point out anything that needs attention.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual OAuth app 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 Ticktick working from chat.
| Manual | ClawLink | |
|---|---|---|
| Connection flow | Register a Ticktick app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Ticktick through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Ticktick. | 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 Ticktick actions to the runtime in a format your agent can reliably use. | 13 tools for Ticktick are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Ticktick 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 Ticktick in the browser, and the 13 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Ticktick skill but can't call the tools
The ClawHub skill teaches OpenClaw about Ticktick, but the calls run through the ClawLink plugin and your connected account. Make sure Ticktick 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 Ticktick 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 Ticktick tools
Ticktick 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 Ticktick 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.
Ticktick 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.
OAuth finished in the browser but the account is still missing
Try reconnecting Ticktick and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete.
FAQ
Is there a OpenClaw Ticktick integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Ticktick: link your Ticktick account once in the browser and OpenClaw can call the Ticktick API through 13 ready-made tools — no custom code or token handling.
How do I add Ticktick to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Ticktick skill from ClawHub, then you click Connect in the dashboard to authorize Ticktick. OpenClaw calls the tools from the next message — no config files or API keys to manage.
How long does it take to connect Ticktick to OpenClaw?
About two minutes. Sign in, click Connect next to Ticktick in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Ticktick up myself?
The alternative to ClawLink is usually manual OAuth app 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 Ticktick working from chat.
OpenClaw installed the Ticktick skill but can't call the tools
The ClawHub skill teaches OpenClaw about Ticktick, but the calls run through the ClawLink plugin and your connected account. Make sure Ticktick 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.