How to connect Google Tasks 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 Google Tasks from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.

Google Tasks 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 Google Tasks 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.

On a self-built integration this means your OAuth client did not request the Tasks scope, and the fix is a console trip. On a hosted connection the causes are different and easier. The most common is a partial approval: Google's consent screen lets you untick permissions, and dropping the write permission leaves a connection that lists tasks fine and fails on every create or update. Reconnect from the dashboard and accept the full set. The second is the account — if you are signed into a personal and a work Google account, the task lists the agent sees belong to whichever one approved the grant, so a connection that looks healthy but finds nothing is usually pointed at the other account.

Ask the agent to diagnose it:

Run googletasks_list_task_lists and tell me exactly which task lists you can see and which Google account this connection is acting as. Do not retry the failed call yet.

This is specific to how the tools are delivered and it is not an error in your setup. Tool schemas are fetched on demand rather than shipped with the plugin, so the first Google Tasks call in a fresh session can arrive before the catalog has loaded. Wait a couple of seconds and retry and it resolves. Only if every call fails in a brand-new chat does the connection itself need attention, in which case reconnect from the dashboard. Search results for this phrase mostly describe a local MCP server missing from a client config file, which is a different setup — there is no local server here and no file to edit.

Tasks always belong to a list, and if the prompt did not name one the agent picked a default. googletasks_list_task_lists returns the real list ids, and passing that id is what makes placement deterministic. The related surprise is hierarchy: googletasks_move_task changes a task's parent and position, so a task can be a subtask of another rather than missing. If something seems to have vanished, have the agent run googletasks_list_all_tasks before concluding it was never created.

Ask the agent to diagnose it:

Run googletasks_list_task_lists, show me every list with its id, then run googletasks_list_all_tasks and tell me which list the task you created actually landed in.

Try reconnecting Google Tasks 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 Google Tasks: link your Google Tasks account once in the browser and Hermes Agent can call the Google Tasks API through 16 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 Google Tasks 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 Google Tasks 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 Google Tasks working from chat.

No. Doing it yourself means creating a project, enabling the Tasks API, building an OAuth consent screen, and living with the fact that an app left in testing status issues refresh tokens that expire after seven days. ClawLink connects through an app that is already registered, so you approve access on Google's own consent screen and that is the whole authorization step. Your account's own access is unchanged — the agent sees the task lists you see.

Yes. Google Tasks is one service surfaced in several places, so a task the agent creates appears in the Tasks panel in Gmail and Calendar, in the Tasks mobile app, and anywhere else you use it. That is worth knowing because it makes the agent's writes immediately visible to you, which is the fastest way to sanity-check what it did. It also means task lists, not calendars, are the unit of organisation here — due dates on tasks are dates rather than timed events.

Both. It can create task lists and tasks, patch individual fields, replace a task wholesale, move tasks between positions and parents, mark them complete, and clear completed tasks from a list. The one to be deliberate about is clearing: googletasks_clear_tasks removes completed tasks from a list in a way you cannot undo from the agent, so it is worth asking to see what will be cleared before it happens.

The connection uses Google's OAuth consent screen, so you approve it there, the agent never handles your password, and disconnecting from the ClawLink dashboard stops further calls. The reach is genuinely narrow compared with most integrations — Tasks holds task lists and their contents, not your mail or files — so the blast radius of a mistake is small. The judgement worth keeping is on the destructive end: completing and clearing tasks are writes you may not notice immediately, so ask the agent to show you what it plans to change before it changes it.

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.