How to connect Todoist to Hermes Agent

Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.

Reconnect Todoist from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.

Todoist 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 Todoist 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.

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.

The standard advice for this phrase is to check your Authorization: Bearer header, delete and regenerate your API token, and make sure you are not calling a deprecated endpoint. None of it applies here, because there is no token in your possession and no header you control. What this means on a hosted connection is that the stored authorization is no longer valid on Todoist's side, and there are only a few ways that happens: you revoked the connection in Todoist's integrations settings, you changed your Todoist password in a way that invalidated existing sessions, or the account itself changed. The fix is to reconnect Todoist from the ClawLink dashboard, which replaces the authorization. If it fails again immediately after reconnecting, the problem is on the Todoist account rather than the connection, and signing in to Todoist directly in a browser will usually show what it is.

Ask the agent to diagnose it:

Run todoist_get_user and tell me exactly which Todoist account is connected, or report the exact error body if it fails. Do not retry the other Todoist calls.

Two causes, and they are easy to separate. The first is a placeholder id: Todoist project and task ids are numeric strings, and an agent that has not listed anything yet will invent one that is structurally valid enough to reach the API, so the answer comes back as forbidden or missing rather than as a bad argument. Run todoist_get_all_projects or todoist_filter_tasks first, then retry with a real id. The second is scope of the account: a project owned by someone else and not shared with you is not visible, and a task in an archived project is not where the agent is looking. todoist_list_archived_projects is the tool for the second case.

Ask the agent to diagnose it:

Run todoist_get_all_projects and show me the project ids and names you can see. Then tell me which one you were trying to use. Do not retry the failing call yet.

If the name looks ordinary, the tool catalog had not loaded when the first call went out; schemas load on demand and retrying once usually clears it. The confusing case is version suffixes, which are real: several tools in this integration genuinely end in a digit, including todoist_get_task2, todoist_create_project2, todoist_reopen_task2, and todoist_update_section2. Those are correct names rather than typos, so an agent that strips the digit to make the name look tidier will get a not-found error. The failures most search results describe for this phrase, involving absolute paths in claude_desktop_config.json and missing environment variables, belong to locally run MCP servers and do not apply here.

Ask the agent to diagnose it:

List the Todoist tools you actually have available that match what I asked for, including any trailing digits, and use the exact name.

Try reconnecting Todoist and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete.

Yes. ClawLink is the fastest way to connect Hermes to Todoist: link your Todoist account once in the browser and Hermes Agent can call the Todoist API through 76 ready-made tools — no custom code or token handling.

Install the plugin with hermes plugins install ClawLink-HQ/hermes-plugin --enable, then pair once: run hermes clawlink begin, approve the link in your browser, and run hermes clawlink finish. Connect Todoist in the dashboard and Hermes can use it from the next message — no config files or API keys to manage.

About two minutes. Sign in, click Connect next to Todoist in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.

The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Todoist working from chat.

No. A Todoist API token is a single string that grants full access to your account, does not expire on its own, and has to be stored somewhere your agent can read it. That is why so much troubleshooting advice ends with regenerating it: when it stops working, the fix is to replace it everywhere you put it. This connection uses OAuth instead, so there is no string for you to hold, and revoking access is a button in Todoist rather than a hunt through config files.

Yes for the core task, project, label, comment, and section tools. Some of the 76 tools reach features that Todoist itself gates by plan, including workspace management, project collaborators, activity logs, and backups. Those tools exist in the catalog and will return an error from Todoist rather than from ClawLink if your plan does not include the feature, which is worth knowing so you can tell a plan limit from a broken connection.

Yes, through todoist_quick_add_task, which accepts Todoist's own quick-add syntax. That means "Pay invoice tomorrow at 5pm #Finance p1" is parsed by Todoist for the date, project, and priority rather than by the agent guessing at fields. For anything where you want explicit control over due dates, labels, or parent tasks, todoist_create_task takes them as separate arguments instead.

It sees what your Todoist account sees, so shared projects you are a collaborator on are included. todoist_get_all_projects lists everything reachable, and todoist_list_project_collaborators shows who else is on a given project. Bear in mind that a task the agent creates or completes in a shared project is visible to your collaborators and attributed to you, so a bulk change is a change other people will notice.

Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.