Microsoft SharePoint integration

What it does

The Microsoft SharePoint integration lets your agency manage a client's SharePoint sites without leaving TaskJuice. Connect a client's Microsoft 365 work or school account once and your workflows can search for sites, look up a site's metadata, list and create folders in the default document library, enumerate the lists defined on a site, and add new list items. The same connection drives a polling trigger that watches for changes in a site's document library so workflows can react when a client uploads, renames, or removes a file.

Connect a Microsoft SharePoint account

1. Open your workspace in TaskJuice and navigate to Connections.
2. Choose Microsoft SharePoint and click Connect.
3. Sign in with a Microsoft 365 work or school account that has access to the SharePoint sites you want to manage on behalf of your client.
4. Grant the requested scopes (Sites.Read.All, Sites.ReadWrite.All, 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 myaccount.microsoft.com and remove the TaskJuice entry under Apps and Services.

Triggers

• sharepoint/drive-item-changed polls a SharePoint site's document library 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

• sharepoint/search-sites searches the SharePoint sites the connected account can see by keyword and returns matching site records, paginating automatically via the standard Microsoft Graph next-page link.
• sharepoint/get-site retrieves a SharePoint site's metadata by its Graph site ID, with optional $select and $expand parameters.
• sharepoint/list-drive-root-children lists items at the root of a site's default document library with optional field selection and order controls. Long results paginate automatically.
• sharepoint/create-folder creates a new folder under a given parent DriveItem in the site's document library, with control over the conflict-resolution behavior when a sibling with the same name already exists.
• sharepoint/list-site-lists enumerates every SharePoint list defined on a site (document libraries, custom lists, and system lists), useful when picking a list ID for downstream item creation.
• sharepoint/create-list-item creates a new item in a SharePoint list with the given column-name to value map.

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.
• Sites are addressed by Graph composite site IDs (hostname,site-collection-id,web-id). Use search-sites to discover the ID for a known site name before plumbing it into other actions.
• 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.
• create-list-item writes to the list's internal column names, which can diverge from the display names a user sees in the SharePoint UI. Confirm the internal names via list-site-lists with $expand=columns before mapping fields.
• The integration targets a site's default document library (the drive endpoint). Workflows that need to operate against a specific non-default document library can address it by drive ID through future actions on the roadmap.