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

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

Classroom's permission model is per-course and role-based, and that is almost always what this is. The connected account has to hold a role on the specific course for the action attempted: reading a course roster or student submissions requires being a teacher on it, and an account that is a teacher on some courses and not others will succeed and fail in exactly this pattern. That is Classroom enforcing course boundaries rather than a scope problem, and no reconnection changes it — the fix is the account's role on that course. Two other causes are worth ruling out. On a managed Workspace domain, an admin policy may block third-party app authorization entirely, which shows up at connect time rather than per course. And a course id copied from documentation fails as a permission error rather than a not-found, so have the agent list courses and use a real id.

Ask the agent to diagnose it:

Run google_classroom_courses_list and tell me exactly which courses this connection can see and what role the account holds on each. Do not retry the failed call yet.

Usually the account, sometimes the identifier. Teachers and students routinely hold a personal Google account and a school one, and the courses the agent sees belong to whichever account approved the grant — a connection made with the wrong one looks healthy and finds nothing. The identifier cause is that courses can be addressed by id or by an alias, and an alias that was never created does not resolve. Have the agent run google_classroom_courses_list first and work from the ids it returns; google_classroom_courses_aliases_list shows which aliases exist if you rely on them.

Ask the agent to diagnose it:

Tell me which Google account this connection is acting as, then run google_classroom_courses_list and show me every course with its id and your role on it.

Two boundaries produce an empty list rather than an error. The first is role: only a teacher on that course can list other people's submissions, so a student account sees only its own, and a connection made with the wrong account returns nothing without complaining. The second is scope of the query — google_classroom_course_work_student_submissions_list is per coursework item, so it needs the course id and the coursework id, and an agent that has only the course id will not find submissions by guessing. Ask it to list coursework with google_classroom_course_work_list first and then pull submissions for the specific item.

Ask the agent to diagnose it:

Run google_classroom_course_work_list for the course and show me each coursework item with its id. Then list submissions for the one I name, and tell me what role you hold on that course.

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

Not built in, which is why the question has an unhelpful answer almost everywhere. Hermes Agent ships without Classroom tools, so the integration has to come from somewhere, and the usual suggestions are a self-hosted MCP server with a Google Cloud project behind it, or a service account with domain-wide delegation arranged by your Workspace admin. Connecting through ClawLink is the one-step version: you approve Classroom on Google's consent screen and the tools are available in the next message, with no Cloud project and no config file.

No, and this is where the open-source options set a misleading expectation. Several community Classroom servers are read-only by design, so summaries of the space describe agent access to Classroom as reading courses and rosters. This toolset covers creating and reading coursework, posting course materials and announcements, listing and reclaiming student submissions, managing topics and aliases, reading rosters of students and teachers, listing guardians, and reading rubrics and grading-period settings. What it can actually do in your Classroom is then bounded by your role, not by the tool list.

Your Classroom role decides what the agent can do, because the agent acts as you. A teacher on a course can create coursework and read submissions for it; a student sees their own work; someone with no role on a course sees nothing, which is Classroom working correctly rather than a broken connection. Separately, some Workspace domains restrict which third-party apps users may authorize at all, so on a managed school or district account an admin may need to allow the connection before the consent screen will complete. That is a Workspace policy question rather than anything configurable in ClawLink.

The connection uses Google's OAuth consent flow, so you approve it on Google's screen, no password is handled, and disconnecting from the ClawLink dashboard ends access. Classroom deserves more care than most integrations for a reason that is not technical: the data includes student names, submissions, and guardian contacts, so the sensible defaults are to connect the account whose role you intend the agent to have, to keep a human in the loop before anything is posted to a course, and to be deliberate about asking an agent to summarize or move student work at all. Student data protection rules that apply to your institution apply to the agent's use of it too.

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.