OneDrive

Files and knowledge

OneDrive for AI agents. Managed auth, ready-made tools.

Search, read, upload and share OneDrive files, including Word, Excel and PowerPoint documents, on behalf of each of your users.

About OneDrive

With the OneDrive connector, your agent works with the files each of your users keeps in OneDrive: it finds a document, reads it, uploads new files, keeps folders in order and creates sharing links. Each user connects their own Microsoft account through managed OAuth, and your agent acts only within that account and the operations your project allows.

OneDrive is Microsoft’s cloud file storage, where people keep their files, including Word, Excel and PowerPoint documents.

Tools

What your agent can do in OneDrive.

Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own OneDrive connection.

  • Search files

    Read
    onedrive_search_files

    Find files and folders by name or content.

  • List a folder

    Read
    onedrive_list_folder

    List the files and folders inside a folder.

  • Get a file

    Read
    onedrive_get_file

    Read a file's details and download its content.

  • Upload a file

    Write
    onedrive_upload_file

    Create a file in a folder, or replace an existing one.

  • Create a folder

    Write
    onedrive_create_folder

    Create a new folder inside a folder.

  • Move or rename

    Write
    onedrive_move_item

    Move a file or folder, or give it a new name.

  • Create a sharing link

    Write
    onedrive_create_sharing_link

    Create a view or edit link for a file or folder.

  • Delete an item

    Write
    onedrive_delete_item

    Move a file or folder to the recycle bin.

Control

Limits you can set.

You decide what your agent may do in OneDrive, and Agent200 runs every call within those limits.

  • Turn single tools on or off

    Keep search and reading on, and switch off onedrive_delete_item or every write tool if your agent only needs to read files.

  • Restrict what the agent reaches

    Choose the endpoints and scopes a project may use. A call outside them is refused.

Get started

Connect OneDrive
in three steps.

  1. 1

    Set up the SDK

    Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.

    agent.js
    Conceptual example
    Set up the SDK with the Agent200 API key
    // One Agent200 API key covers every connector enabled for the project.
    const agent200 = new Agent200({
      apiKey: process.env.AGENT200_API_KEY,
    });
  2. 2

    Let your user connect OneDrive

    Each end user authorizes their own OneDrive account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.

    connect.js
    Conceptual example
    Let an end user connect their account (managed OAuth)
    // Each end user authorizes their own OneDrive account, once.
    const connection = await agent200
      .user("user_123")
      .connect("onedrive");
    
    if (connection.authorizationUrl) {
      // Show this link to your user; Agent200 handles the rest.
      console.log(connection.authorizationUrl);
    }
  3. 3

    Run with the OneDrive tools

    Name the user, the model and the tools. The model decides which OneDrive tools to call, and Agent200 executes them with that user's connection.

    run.js
    Conceptual example
    Run a request with the connector's tools
    const result = await agent200
      .user("user_123")
      .run({
        model: "openai/gpt-5.6-sol",
        input: "Find the latest version of the Q4 budget spreadsheet",
        tools: ["onedrive"],
      });
    
    console.log(result.output);

Access

Sign-in and permissions.

  • Who signs in

    Each of your users, once, on Microsoft's own sign-in page, with a personal or a work or school account. You never see or store their Microsoft password.

  • What access is requested

    Permission to read, or to read and write, the user's files, shown on Microsoft's consent screen. In a work or school account, the organization's admin may need to approve it first.

For agents

Instructions for AI agents.

Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the OneDrive connector and how to use it.

Agent brief
Connector: OneDrive, through Agent200. In code: "onedrive".
What it does: Search, read, upload and share OneDrive files, including Word, Excel and PowerPoint documents, on behalf of each of your users.
Page: https://www.agent200.com/tools/onedrive/

1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs.
2. Sign-in is managed OAuth. Each end user approves access once, on OneDrive's own page, through the authorization link Agent200 returns. Never ask a user for a OneDrive password or token in chat.
3. Give every request a stable id for the end user. Agent200 uses only that user's own connection.
4. Read tools: onedrive_search_files, onedrive_list_folder, onedrive_get_file. Write tools: onedrive_upload_file, onedrive_create_folder, onedrive_move_item, onedrive_create_sharing_link, onedrive_delete_item. Name "onedrive" in the tools of a request; the model decides which tool to call.
5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it.
6. Before a write, confirm with the user, unless they asked for that exact change.
7. For setup with a specific framework, follow its guide:
   https://www.agent200.com/tools/onedrive/framework/claude/
   https://www.agent200.com/tools/onedrive/framework/chatgpt/
   https://www.agent200.com/tools/onedrive/framework/claude-code/
   https://www.agent200.com/tools/onedrive/framework/muse/
   https://www.agent200.com/tools/onedrive/framework/grok-bot/
   https://www.agent200.com/tools/onedrive/framework/openai-dots/
   https://www.agent200.com/tools/onedrive/framework/claude-duet/
   https://www.agent200.com/tools/onedrive/framework/hermes-agent/
   https://www.agent200.com/tools/onedrive/framework/openclaw/

The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/

This page is also available as Markdown, for agents and LLMs: /tools/onedrive.md

Guides

Use OneDrive with the AI you build on.

Step-by-step setup for OneDrive with a specific model, assistant or agent framework.

FAQ

OneDrive and Agent200, answered.

Who handles the OneDrive OAuth flow and the tokens?

Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for OneDrive.

Does my agent act as the end user?

Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's OneDrive connection, never another user's. It cannot reach anything the user or OneDrive has not authorized.

Can I limit what my agent can do in OneDrive?

Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.

  • Google Drive

    Google Drive

    Find, read and organize the files in each user's Drive.

    Managed OAuth Files and knowledge
  • Dropbox

    Dropbox

    Search, read, upload and organize Dropbox files, and create shared links, on behalf of each of your users.

    Managed OAuth Files and knowledge
  • Notion

    Notion

    Search, read and write Notion pages and databases on behalf of each of your users.

    Managed OAuth Files and knowledge
  • Confluence

    Confluence

    Search, read and write Confluence pages and comments on behalf of each of your users, within the spaces they can access.

    Managed OAuth Files and knowledge
200 OK

Start with OneDrive.
Your agent does the rest.

Your users connect their own OneDrive accounts. Agent200 handles the OAuth, the tokens and every tool call.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)