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

Microsoft OneDrive 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 Microsoft OneDrive 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.

Search results answer this by sending you to the Azure Portal to add Files.ReadWrite.All, grant admin consent, and inspect your token at jwt.ms. None of that applies here, because the permissions were fixed at sign-in and there is no token for you to decode. Two causes account for it instead. The first is real access: the connection acts as you, so a file or folder you cannot open in the OneDrive web app is not reachable from chat either, and files shared with you can have their sharing revoked without warning. The second is a placeholder argument: item ids in OneDrive are opaque strings, and an agent that has not listed anything yet will invent one, which reaches Microsoft and returns a permissions-shaped error rather than a bad-argument error. Ask for one_drive_list_folder_children or one_drive_search_items first, then retry with a real id.

Ask the agent to diagnose it:

Run one_drive_get_drive and tell me which account and drive you are connected to. Then run one_drive_list_folder_children on the root and show me what you can see. Do not retry the failing call until both have returned.

These look similar in chat and mean different things. A 507 is storage: the drive is full, and OneDrive counts items in the online recycle bin against your quota, so emptying it in the web app frees space that deleting files alone did not. A 429 is throttling: Microsoft Graph is rate-limiting the requests and the response carries a Retry-After value telling you how long to wait. Retrying a 429 immediately makes it worse, and reconnecting does nothing for either. If an agent is walking a large folder tree, the practical fix is to narrow the work: search for what you need with one_drive_search_items instead of enumerating everything with repeated one_drive_list_folder_children calls.

Ask the agent to diagnose it:

Report the exact status code and any Retry-After header from the failed OneDrive call. Do not retry it.

Tool schemas load on demand, so the first OneDrive call in a fresh session can arrive before the catalog is available. Retry once. If the same name fails twice, the name is wrong rather than missing, and the error lists the closest real tools. Note that several tools in this integration carry a doubled prefix by design, including one_drive_onedrive_upload_file and one_drive_onedrive_create_folder, so a name that looks like a mistake may be correct. The failures described in most search results, where an MCP server fails to initialize or an IDE needs restarting, do not apply here; there is no local server and no config JSON.

Ask the agent to diagnose it:

List the OneDrive tools you actually have available and tell me which one uploads a file. Use that exact name.

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

Yes. The registration step belongs to building the integration yourself: create an application in Entra ID, add Microsoft Graph permissions, get consent, then rotate a secret before it expires. ClawLink connects through an application that is already registered, so your part is a Microsoft sign-in. The access is delegated rather than application-level, which means the agent acts as you and inherits your permissions instead of holding tenant-wide reach of its own. If your organization routes new applications through an approval queue, an administrator approves it once and everyone in the tenant is covered.

Microsoft's agents run inside Microsoft 365 and are configured there, which is the right answer when the work starts and ends in OneDrive and everyone involved has the relevant Copilot licensing. This connection puts OneDrive tools into Hermes, so a single prompt can pull a spreadsheet from OneDrive, cross-reference something from another connected service, and write a summary somewhere else. The practical question is whether your workflow is OneDrive-shaped or agent-shaped. If the agent only ever touches OneDrive, Microsoft's own tooling is worth a look first.

Both, because the connection acts as your account and your account sees both. one_drive_get_shared_items lists what other people have shared with you, and one_drive_get_drive_item_by_sharing_url opens a specific file from a sharing link someone sent you. Anything nobody shared with you stays out of reach, which is the same boundary you experience in the OneDrive web app.

Yes, and this is the group of tools worth being deliberate about. one_drive_create_link generates a sharing link, one_drive_invite_user_to_item sends an invitation, and one_drive_grant_share_permission and one_drive_update_drive_items_permissions change who can reach what. A sharing link created without thought is a file handed to whoever holds the URL, so keep an approval step in the prompt before the agent shares anything, and use one_drive_list_share_permissions to review what already exists.

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.