Skip to main content
Feedback

Microsoft SharePoint connector

The Boomi SharePoint connector provides a seamless, secure integration point between the Boomi Integration platform and Microsoft SharePoint (SharePoint Online), via the Microsoft Graph API. It lets you build processes that read from and write to SharePoint content — document libraries, folders, lists, and list items — without managing the complexities of Graph REST calls, OAuth 2.0 token handling, ID resolution, or file uploads yourself.

With the SharePoint connector, you can:

  • Retrieve file metadata, or download a file's binary content, from a SharePoint document library
  • Upload new files into a SharePoint document library
  • Retrieve, create, and delete folders within a document library
  • Retrieve, create, and delete SharePoint lists, including their custom columns
  • Retrieve, create, and delete items within a SharePoint list, including custom columns
  • Delete files from a SharePoint document library

For more information, refer to Microsoft Graph API — SharePoint reference.

Benefits

  • Simplified access to SharePoint files, folders, lists, and list items through a single connector
  • Support for three action types: Get, Create, and Delete
  • Secure OAuth 2.0 authentication against Microsoft Entra ID (Azure AD) — supports Client Credentials, Certificate-Based Authentication (CBA), and Authorization Code (delegated) grant types
  • Dynamic schema generation for list items, built live from a list's actual custom columns
  • Select only the fields you need on Get operations to keep responses smaller and faster
  • Automatic retry with exponential backoff for throttled (429) and transient server (5xx) Graph API errors, honoring the Retry-After header
  • Runtime-scoped caching of resolved Site, Drive, and List GUIDs to minimize redundant Graph API lookups across a process run

Connector configuration

To configure the connector, create these reusable components and add them to your process:

  • Microsoft SharePoint connection
  • Microsoft SharePoint operation (Get, Create, or Delete)

After you build the connection and operation, place the connector step in your process and map the request/response as required by your use case.

Prerequisites

  • A Microsoft 365 tenant with SharePoint Online enabled
  • An Azure AD (Microsoft Entra ID) App Registration with Microsoft Graph API permissions granted and admin-consented (for example, Sites.Read.All / Sites.ReadWrite.All, Files.ReadWrite.All)
  • The Tenant ID, Client (Application) ID, and Client Secret — or an uploaded certificate for Certificate-Based Authentication — from the Azure App Registration
  • The full URL of the target SharePoint site (for example, https://contoso.sharepoint.com/sites/finance)
  • Appropriate SharePoint site-level permissions for the account or service principal being used

Supported versions and SDKs

  • Boomi Connector SDK: 2.30.1
  • Java: 8
  • Microsoft Graph API version: v1.0

Business use cases

  • Document management — Automate retrieval and upload of contracts, invoices, reports, and other business files stored in SharePoint document libraries.
  • Content onboarding — Populate SharePoint document libraries and folders with files and metadata from external systems.
  • Business process tracking — Create SharePoint list items to drive task tracking, approval workflows, and status boards from external systems.
  • Content retrieval — Fetch file, folder, list, and list item metadata (or binary file content) on demand for downstream processing.
  • Content cleanup — Remove obsolete files, folders, lists, or list items as part of a scheduled housekeeping or offboarding process.

Best practices

  • Use Item ID (GUID) instead of path/name wherever available — it skips an extra Graph lookup.
  • Fetch only the fields you need on Get by ticking just those properties or columns on the operation's Fields tab, instead of retrieving everything.
  • Let the connector's built-in retry handle transient 429/5xx errors — avoid layering your own retry logic on top, which can compound backoff delays.
  • Resolve and verify the target item with a Get immediately before a Delete step in the same process, especially when the identifier is built dynamically. Prefer Item ID (GUID) over Drive Name + Path for Delete wherever possible.
  • Prefer Certificate-Based Authentication over Client Secret where your organization's security policy allows it, and grant the narrowest Graph API permission scope your integration actually needs.
  • Keep files uploaded through Create at or under 250 MB; split larger files before upload.
  • Configure "Return Application Error Response(s)" so document-level Graph errors route to an error path in your process instead of failing the whole batch.
caution

Deletion through this connector is permanent. Microsoft Graph does not return the deleted item's content, and the connector does not prompt for confirmation or verify the target's identity beyond the configured Drive Name/Path/Item ID or List Name/Item ID. Recovery, if any, depends entirely on your tenant's SharePoint recycle-bin retention policy.

Known limitations

  • Latency — Operation performance depends on Microsoft Graph service latency, the tenant's region, and network path. Response times can range from milliseconds to several seconds.
  • Rate limiting — All requests are subject to Microsoft Graph API throttling. If a process exceeds tenant/app-level limits, Graph returns HTTP 429. The connector retries automatically with exponential backoff, but sustained high-volume batches may still be throttled.
  • Usage limits — Subject to Microsoft 365 tenant-level Graph API service limits (requests per app, per site, per user), which vary by license tier and current service health.
  • File size (Create) — Create supports files up to 250 MB only. There is no chunked-upload path for Create in this operation set — larger files must be split or uploaded another way before being brought into SharePoint through this connector.
  • Memory — File content for Get/Create is streamed directly without buffering, regardless of size. Folder, List, and List Item bodies are JSON and are handled in memory; very large list item payloads or column sets can affect Atom memory usage.
  • List and list item discovery — There is no runtime action to enumerate all lists in a site. List names must be selected during the design-time browse/import wizard (List Item) or already known in advance; Get and Delete on the List object type both require an explicit List Name.
  • Column schema drift — The List Item request/response profile is generated at design time from the list's columns as they existed at import time. If columns are later added, renamed, or removed in SharePoint, the operation must be manually re-imported — the profile does not update automatically at runtime.
On this Page