Skip to main content

Microsoft OneDrive integration

Sync files and folders across your clients' OneDrive accounts via Microsoft Graph.

What it does

The Microsoft OneDrive integration lets your agency move files in and out of a client's OneDrive and start workflows whenever items change in the drive. Connect a client's Microsoft 365 or personal Microsoft account once and your workflows can list root contents, look up a file or folder by ID, create folders, upload small files, download bytes for downstream processing, and delete items the agency no longer needs to keep around.

Connect a Microsoft OneDrive account

  1. Open your workspace in TaskJuice and navigate to Connections.
  2. Choose Microsoft OneDrive and click Connect.
  3. Sign in with the Microsoft 365 or personal Microsoft account whose OneDrive files you want to manage on behalf of your client.
  4. Grant the requested scopes (Files.Read, Files.ReadWrite, Files.ReadWrite.All, and offline_access so TaskJuice can refresh the access token in the background).
  5. TaskJuice returns you to the workspace with the connection ready to use in any workflow.

To revoke access at any time, sign in to My Account at portal.office.com and remove the TaskJuice entry under Apps and Services.

Triggers

  • microsoft-onedrive/drive-item-changed polls the OneDrive delta endpoint on a configurable interval and emits one activation per cycle containing every DriveItem that was added, modified, or removed since the previous cycle. Drop a Loop node downstream to process each item individually, or feed the array into a digest step.

Actions

  • microsoft-onedrive/list-root-children lists items at the root of the connected user's OneDrive with optional field selection and order controls. Long results paginate automatically via the standard Microsoft Graph next-page link.
  • microsoft-onedrive/get-drive-item retrieves the metadata for a single DriveItem by its ID, with optional $select and $expand parameters.
  • microsoft-onedrive/create-folder creates a new folder under a given parent DriveItem, with control over the conflict-resolution behavior when a sibling with the same name already exists.
  • microsoft-onedrive/upload-small-file uploads a file (up to 4 MB) from a previous step's FileReference to a target parent folder and filename in OneDrive.
  • microsoft-onedrive/download-file downloads the binary content of a DriveItem and returns a FileReference that downstream steps can attach to outbound emails, forward to other apps, or persist.
  • microsoft-onedrive/delete-drive-item permanently deletes a file or folder by its DriveItem ID.

Known limitations

  • The drive-item-changed trigger is polling-based. Microsoft Graph also offers Change Notifications via subscriptions, but those notifications carry their auth proof in the request body rather than a signed header, which falls outside the declarative inbound-auth contract. The polling delta endpoint is the supported path today (60 seconds minimum, five minutes by default), and latency is bounded by the chosen interval rather than instant.
  • The upload-small-file action is limited to payloads of 4 MB or less. Larger uploads require Microsoft Graph's upload-session protocol, which is on the roadmap as a separate action.
  • Microsoft Graph enforces per-app and per-tenant throttling. When a 429 is returned, TaskJuice surfaces it as a retryable rate-limit error and respects the recommended backoff.
  • The connected account must have at least one OneDrive provisioned. Brand-new Microsoft 365 tenants whose users have never opened OneDrive in the browser may need to provision the drive before the connection becomes usable.
Was this helpful?
Microsoft OneDrive integration | TaskJuice Docs