Skip to main content

OneDrive

Browse, search, read, write and share the files in a connected account's own OneDrive.

Connect a Microsoft work, school or personal account to work with the files in its OneDrive: list a folder, search by name or by what an indexed document says, read a file out as an attachment on the session, write one in from the workspace (chunked when it is large), create folders, move and rename, delete to the recycle bin, and mint a sharing link. Reaches the signed-in account's OWN OneDrive only - a SharePoint library, a team's shared drive, or a file someone else shared with the account is deliberately out of reach.

Connect

Sign in with Microsoft. Sign in with Microsoft to browse, read, write and share the files in your own OneDrive. An organization admin configures the OAuth app once under Integrations → OAuth apps; after that, connecting is a consent screen.

  • Connecting signs in as YOU - every tool reaches exactly the files in YOUR OneDrive, and a file it writes or deletes is written or deleted by you.

  • This connection reaches your own OneDrive ONLY. A SharePoint document library, a team's shared drive, or a file a colleague shared with you is out of reach: the Microsoft permission that would cover those ('Files.ReadWrite.All') also reaches every site your account can see, and this connection deliberately does not ask for it.

  • Both permissions can be granted by you without an admin - unlike the Teams connection, nothing here waits on an Entra admin's approval.

  • Delete moves an item to your OneDrive recycle bin, where you can restore it.

  • For scheduled or triggered automations, connect a dedicated licensed Microsoft account and put the files it should reach in ITS OneDrive: automations cannot run as a person, so they need a service connection.

Tools

ToolAccessWhat it does
Get drive (yekar.onedrive.get-drive)ReadRead the connected account's OneDrive: who owns it, whether it is a personal or work drive, and how much space is left. Use it to confirm WHICH account this connection acts as before writing anything - every tool here acts as that account, and a connection made in the wrong tenant looks identical until a call 404s.
List folder (yekar.onedrive.list-children)ReadList what is directly inside a folder in the connected account's OneDrive. Omit both itemId and path for the drive root. Returns ids and paths the other tools take. Paginated - Graph reports no total for a drive collection, so what comes back is a page, not a count of what is there.
Search files (yekar.onedrive.search)ReadFind files and folders in the connected account's OneDrive by name, or by what an indexed document says. Optionally restricted to one folder's subtree. Returns ids and paths the other tools take. Paginated - Graph reports no total for a drive search, so what comes back is a page, not a count of the matches that exist.
Get file or folder (yekar.onedrive.get-item)ReadRead one item's details: its id, size, type, and when and by whom it last changed. Use it to confirm a path exists and is what you think it is before downloading or overwriting it. For a folder, sizeBytes is the total of everything inside, not the folder's own size.
Download file (yekar.onedrive.download-file)ReadFetch a file's contents from the connected account's OneDrive and save it as an attachment on this session, rather than returning the bytes inline. Works for any file type. Files over 250 MB are refused in one call. A folder cannot be downloaded.
Upload file (yekar.onedrive.upload-file)WriteWrite a file into a folder in the connected account's OneDrive, from this run's workspace or an https URL. Files up to 4 MB go in one request; larger ones (to 250 MB) are sent in chunks through a OneDrive upload session. By default a name that is already taken FAILS rather than overwriting.
Create folder (yekar.onedrive.create-folder)WriteCreate a folder inside another folder in the connected account's OneDrive. Omit both parent fields to create it at the drive root. By default a name that is already taken FAILS rather than being silently reused - a folder that already exists is a different folder from the one you meant to create.
Move or rename (yekar.onedrive.move-item)WriteMove a file or folder into another folder, rename it, or both. Give a destination folder to move, a newName to rename, or both together. Moving a folder moves everything inside it.
Delete file or folder (yekar.onedrive.delete-item)WriteMove a file or folder to the connected account's OneDrive recycle bin, where the owner can restore it. Deleting a folder deletes everything inside it. Returns no details of what was deleted - OneDrive answers a delete with an empty response, so read the item first if you need a record of it.
Create share link (yekar.onedrive.create-share-link)WriteMint a sharing link for a file or folder and return its URL. Check scope on the result before treating a link as public: a Microsoft 365 tenant can be configured to refuse anonymous links, and OneDrive will hand back an organization-only link instead of failing. Calling this twice for the same item and settings returns the same link rather than a second one.

Notes

  • Sign in with Microsoft to connect - every tool acts as YOUR account, and a file it writes or deletes is written or deleted by you.
  • This connection reaches your own OneDrive ONLY. Files in a SharePoint site, a team's shared drive, or shared with you by a colleague are out of reach: the permission covering those also reaches every site your account can see, and it is deliberately not requested.
  • Both permissions can be granted by you without an Entra admin - nothing here waits on an organization-wide approval.
  • Every item can be named by its itemId or by its path, but never both at once. Prefer the id for anything spanning more than one call: an id survives a rename, a path does not.
  • Upload and Create folder refuse a name that is already taken unless you ask for 'replace' or 'rename' - the default never overwrites.
  • Delete moves an item to your recycle bin, where you can restore it. Nothing here deletes permanently.
  • Check the scope on a share link before telling anyone it is public: a Microsoft 365 tenant can refuse anonymous links and hand back an organization-only one instead of failing.
  • For a schedule or a trigger, bind this as a service connection owned by a dedicated licensed account whose own OneDrive holds the files - an automation cannot run as whoever happened to start it.
  • Anyone who can put a file in a folder you sync can write text your agent will read. Gate write and share steps in any automation whose reads come from a folder outsiders can add to.