Articles on: Integrations & auth

Connect OneDrive

Connect a Microsoft account to Lido so workflows can watch OneDrive folders, download files, and trigger on new uploads. The same connection powers the OneDrive Trigger and the OneDrive node.



When to connect


  • You want a workflow that runs every time a new file lands in a OneDrive folder.
  • You want workflows to download or list files from OneDrive.
  • Your team uses Microsoft 365 and OneDrive instead of Google Drive.



Before you start


You need:


  • A Microsoft account (personal or Microsoft 365 / Office 365 work account) with access to the folders you want Lido to read or write.
  • For SharePoint or shared folders: confirm the account has at least Read access.
  • Admin rights to add integrations to your Lido workspace.



Step-by-step


  1. Open your Lido workspace settings and find Integrations (or Credentials).
  2. Click Add Integration → OneDrive.
  3. Click Connect to start the OAuth flow. Sign in to the Microsoft account, review the requested scopes, and approve.
  4. Lido stores the connection as a credential.
  5. In the workflow editor, the connected account now appears as a selectable credential on OneDrive Trigger and OneDrive nodes.



What Lido can and can't do with the connection


Can:


  • Watch a OneDrive folder for new files.
  • Download files for processing.
  • List files in a folder.
  • Upload files Lido creates (exports, generated PDFs) to a folder.


Can't (without explicit configuration):


  • Read your entire OneDrive. Lido only accesses what you point it at via folder selection.
  • Modify file permissions.
  • Delete files unless you explicitly configure a deletion action.



Using the connection in workflows


Watch a folder


Add a OneDrive Trigger node. Pick the connected credential, pick the folder, set file types. The workflow fires on every new file.


List files in a folder


Add a OneDrive node with operation List. Returns one item per file. Useful for batch processing.


Download a file


Add a OneDrive node with operation Download. Pass a file URL or ID; returns content for downstream processing.



Microsoft 365 vs. personal OneDrive


Both work. Differences:


  • Microsoft 365 work/school account — admin may need to approve Lido in your tenant's app management. If approval is required, you'll see a notification during OAuth.
  • Personal Microsoft account — no tenant approval; just sign in.
  • SharePoint document libraries — accessible if your work account has rights. Lido treats them as folders within the OneDrive connection.



Tips


  • Use a service account for production workflows. When an employee leaves, their personal connection breaks.
  • Connect with the least-privileged account that still has access to the target folder.
  • Test with a non-production folder first.
  • For SharePoint: confirm the connected account has access to the specific document library, not just the parent SharePoint site.



Common mistakes


  • Connecting an account that doesn't have folder access. OAuth only grants what the user has.
  • Personal vs. work account confusion. A user's personal Microsoft account and their Microsoft 365 account are different — make sure the right one is connected.
  • Watch mode set to "all changes". Re-fires on every edit; use "new files only".
  • Personal account used for production. Same problem as Google: account disabled, workflows break.
  • Tenant admin hasn't approved Lido. OAuth fails partway through; ask your IT admin to allowlist Lido in your Microsoft 365 tenant.



Disconnecting


Open workspace settings → Integrations → find the OneDrive credential → Remove. Workflows using the credential will fail until you reconnect.




  • Build your first workflow
  • Triggers: how workflows start (OneDrive Trigger)
  • Connect Google Drive
  • Automate extraction with workflows

Updated on: 16/04/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!