OpenClaw / clawdbot integration
This guide shows how to connect OpenClaw (aka clawdbot) to 4todo so the agent can create and manage tasks for you using the Eisenhower Matrix.
What you can do
- List your 4todo workspaces
- Create tasks in a specific quadrant (urgent vs important)
- Complete tasks
- Reorder / move tasks between quadrants
- Create and manage recurring tasks
Requirements
- A 4todo account
- A 4todo API token
- An OpenClaw Gateway that can run skills (any OS)
curlavailable in the runtime where OpenClaw executes skills- The 4todo OpenClaw skill installed (ClawHub or manual)
If you run OpenClaw in a sandboxed Docker environment, ensure curl exists inside the container as well.
1) Create a 4todo API token
- Open 4todo settings
- Create an API token
- Copy it immediately (it is shown only once)
Security note: do not paste your token into chat messages. Store it in OpenClaw config instead.
2) Install the 4todo skill into your OpenClaw workspace
OpenClaw loads workspace skills from:
<workspace>/skills
Choose one install method:
Option A (recommended): Install with ClawHub
This is the easiest path if your OpenClaw environment can run the clawhub CLI and has network access.
A1) Install with ClawHub via chat (agent does it)
Ask OpenClaw / clawdbot something like:
Install the 4todo skill using ClawHub, then tell me what folder it created under <workspace>/skills.
OpenClaw will typically run the same CLI commands shown below.
A2) Install with ClawHub via terminal (you do it)
- Install the ClawHub CLI (pick one):
npm i -g clawhub
pnpm add -g clawhub
- From your OpenClaw workspace root, search and install:
clawhub search "4todo"
clawhub install <slug>
- Start a new OpenClaw session so it picks up the skill.
Human-friendly tip: if you don’t know the slug, use the clawhub search results to find the right one.
After install, you should have:
<workspace>/
skills/
4todo/
SKILL.md
references/
api_v0.md
Option B: Manual install (copy the folder)
Install the 4todo skill as a folder named 4todo:
<workspace>/
skills/
4todo/
SKILL.md
references/
api_v0.md
3) Store the token in OpenClaw config (recommended)
Edit ~/.openclaw/openclaw.json and inject the token for the 4todo skill:
{
skills: {
entries: {
"4todo": {
enabled: true,
env: {
FOURTODO_API_TOKEN: "YOUR_4TODO_API_TOKEN"
}
}
}
}
}
Notes:
- If your Gateway has config hot reload disabled (
gateway.reload.mode: "off"), restart the Gateway after changing the config. - OpenClaw watches
~/.openclaw/openclaw.jsonand hot-reloadsskillsconfig by default. In most setups, you do not need to restart the Gateway. The new token is picked up on the next agent run. - OpenClaw does not override existing env values. If
FOURTODO_API_TOKENis already set (and wrong) in the process env, updatingskills.entrieswon’t replace it. Unset/fix the process env and restart the Gateway.
If you run OpenClaw sessions in a sandboxed Docker environment, set the token in Docker env instead:
{
agents: {
defaults: {
sandbox: {
docker: {
env: {
FOURTODO_API_TOKEN: "YOUR_4TODO_API_TOKEN"
}
}
}
}
}
}
4) Verify the connection
Ask OpenClaw / clawdbot:
List my 4todo workspaces
You should see a list of workspaces.
Then try a real command:
Add Test task from OpenClaw to the important (not urgent) quadrant in my Life workspace (or your default workspace)
Open 4todo and confirm it appears in the correct quadrant.
5) What to say to OpenClaw / clawdbot (human examples)
Write naturally. Mention the quadrant and workspace when it matters.
I’m swamped. Add the most urgent project tasks to 4todo (Project workspace).
Add today’s tasks to my Life workspace: buy groceries, call dentist, pay rent.
Move Reply to vendor email to important (not urgent).
Put Fix checkout bug above Unblock QA in urgent & important.
Set a recurring Weekly review every Friday in important (not urgent).
Agent runbook (read this if you are an agent)
Safety & secrets
- Never ask the user to paste their token into chat.
- If auth is missing/invalid, instruct the user to set
FOURTODO_API_TOKENvia OpenClaw config. - Do not show internal IDs (
ws_...,todo_...,rec_todo_...) unless the user asks. Refer to workspaces and tasks by name.
Execution checklist
Use this exact order unless the user explicitly requests otherwise:
- List workspaces (pick the target workspace by name).
- List todos for that workspace.
- Perform the requested mutation (create / complete / reorder / recurring).
- Re-fetch to verify the change and summarize what changed.
Capability mapping (what the skill can do)
- Workspaces: list workspaces.
- Todos: list, create, complete, move/reorder.
- Recurring tasks: list, create, get, update, delete recurring todos.
Troubleshooting
- 401 (
invalid_token,token_expired,token_paused): create a new token in 4todo and update OpenClaw config. - 402 (
WORKSPACE_RESTRICTED): that workspace is read-only; choose another workspace or upgrade. - 429 (
rate_limited): slow down and retry later. - 400 (
Invalid quadrant type): describe the quadrant using urgent/important (or let the agent pick the right quadrant). - Skill not loaded: ensure the skill exists under
<workspace>/skillsand start a new OpenClaw session.
Related links
- Integration landing page:
/integrations/openclaw - API reference:
/docs - Eisenhower Matrix guide:
/eisenhower-matrix