Help Center

Menu

Microsoft Sharepoint 365

The Microsoft Sharepoint 365 component provides an integration pathway with Microsoft Sharepoint.

This component interacts with your SharePoint Online environment by using the Microsoft Graph API. It retrieves, creates, updates, and deletes objects within your SharePoint sites and document libraries.

Prerequisites

Before you can start using the Microsoft Sharepoint component with Integrations, several conditions must be met first, which includes having:

  • The permissions required to register apps through the Microsoft Azure portal.

  • Set up a flow and are ready to add the Microsoft Sharepoint component to the relevant step.

Register and configure Integrations as an app through the Microsoft Azure portal

  1. Visit the Microsoft Azure portal’s App registrations page, signing in if required.

  2. On the App registrations page, click on New registration.

  3. Specify an appropriate Name (for example, 'Integrations').

  4. Choose the appropriate Supported account types that can access the Azure API.

  5. Click the Register button, which opens the app registration page with the name of your configured app (for example, Integrations) at the top of the page.

  6. On the app registration page, click Authentication (in the nav panel) to open this page.

  7. Click + Add a platform to begin specifying the redirect URI for Integrations in the Microsoft Azure portal.

  8. In the resulting Configure platforms pop-out, click the Web panel option (under Web applications).

  9. Copy the region-appropriate URI value from the list and paste it into the Redirect URIs field on the resulting Configure Web pop-out:

  10. Click Configure towards the end of the pop-out, and review the Web platform section.

  11. Click Certificates & secrets (in the nav panel) to open this page.

  12. Click + New client secret to begin specifying a secret to add for Integrations to integrate with Microsoft Sharepoint.

  13. In the resulting Add a client secret pop-out, specify an appropriate Description (that is, something related to how your Microsoft Sharepoint component is used in the flow) and expiration period in the Expires field.

    Keep this browser tab/window open before continuing.

    For security reasons, the client secret’s value is only displayed temporarily, such that if you were to revisit the Certificates & secrets page again after a short period, the client secret’s value becomes indefinitely obscured. In such instances, you need to delete this client secret and recreate it (by clicking + New client secret) above to access the client secret’s value.

Copy the generated client secret value immediately after you create it, because Azure does not display it again.

  1. Configure Microsoft Graph API permissions for your app:

    Add the following API permissions (application permissions): * Sites.Read.All. * Sites.ReadWrite.All. * Files.Read.All. * Files.ReadWrite.All.

Configure your Microsoft Sharepoint component in Integrations

  1. Ensure you have accessed your flow by clicking Flows (in the nav), then the name of your flow on the main page.

  2. Click Add a new action and in the resulting step configuration panel (Setup this step Configuration), search for 'Sharepoint' and choose the Microsoft Sharepoint component from the list of options.

  3. Click Choose Microsoft Sharepoint to confirm.

  4. In the step configuration panel (Functions), choose the appropriate action you want this component to perform in Microsoft Sharepoint.

    Use the Find function field to filter and narrow down the list of available functions.

  5. In the next step (Credentials), click Add New Credential.

  6. In the Name Your Credential field, update your Microsoft Sharepoint component’s default name to represent the Microsoft Azure portal configuration above, for example, 'My Microsoft Azure portal credential' or 'Funnelback integration credential'.

  7. On the Microsoft Azure portal page’s browser tab/window, copy the Value of the relevant client secret within the Client secrets section of the Certificates & secrets page, and paste this value into the Client Secret field of the Integrations Credentials step.

  8. Back on the Microsoft Azure portal page, click Overview (in the nav panel) to open this page.

  9. Copy the Application (client) ID within the top section of the Overview page, and paste this value into the Client ID field in the Credentials step.

  10. Back on the Credentials step in Integrations, for the Auth URI field, specify the value:

    https://login.microsoftonline.com/<YOUR_TENANT_ID>/oauth2/v2.0/authorize

    Replace <YOUR_TENANT_ID> with your Azure AD tenant ID.

  11. For the Token URI field, specify the value:

    https://login.microsoftonline.com/<YOUR_TENANT_ID>/oauth2/v2.0/token

    Again, replace <YOUR_TENANT_ID> with your Azure AD tenant ID.

  12. In the Scopes (Space-separated list) field, specify the Microsoft Graph scopes that match the permissions granted to your Azure AD application.

    Recommended: use https://graph.microsoft.com/.default when using application permissions.

    For delegated permissions, specify the required delegated scopes. For example: https://graph.microsoft.com/Sites.Read.All https://graph.microsoft.com/Sites.ReadWrite.All.

    Scopes configured in the Scopes (Space-separated list) field must match the registered Azure AD app permissions.

If the scopes are mismatched or insufficient, the component can return authentication errors or permission denied errors when you execute actions.

  1. Click Authenticate.

  2. If Integrations has been correctly integrated with Microsoft Sharepoint, Integrations indicates Success.

Then complete the remainder of the Microsoft Sharepoint component’s step configurations based on the action you chose above.

Triggers

Get New and Updated Objects Polling

Polls SharePoint for objects that have been created or updated after the snapshot time. The trigger can emit results one-by-one or as pages.

Configuration fields

Name Your Credential

A required string. Any label that helps you identify the credential.

Site ID

A required string. The unique identifier of the SharePoint site to monitor.

Object Type

A required drop-down. The type of SharePoint object to poll on. For example, Base Site Pages.

Time stamp field to poll on

An optional drop-down. The date/time field to evaluate. For example, lastModifiedDateTime. The default is Last Modified.

Start Time

An optional string. An ISO 8601 timestamp for the initial poll. The default is 1970-01-01T00:00:00Z when omitted. Format: YYYY-MM-DD[T]HH:MM:SS[Z].

Size of Polling Page

An optional number. The number of records to request per API call. The default is 100. Valid values are between 1 and 100. This reduces to 10 in debug or sample flows.

Emit Behavior

An optional drop-down. Defines how the results are emitted. The default is Emit individually.

Output metadata

Emit individually

The trigger emits each record as an individual message. The structure matches the Lookup Objects response for the selected object type.

Emit page

The trigger emits pages of results. The message includes a results array with the same structure as individual records.

Snapshot behavior

The trigger stores the most recent seen value of the selected time stamp field. The next poll starts strictly after that timestamp. If no additional data is found, the trigger adds one second to avoid duplicate emissions.

Actions

Delete Object By ID

Deletes a single object from SharePoint by its unique identifier (ID).

Configuration fields

Object Type

A required drop-down. The SharePoint object type to delete. Options include: List, List Item, Site Column, List Column, Base Site Page, and Drive Item.

Input metadata

ID Value

A required string. The identifier of the record to delete.

When Object Type is Drive Item: Site ID (soft delete):: A required string for soft delete. Drive ID (permanent delete):: A required string for permanent delete. Delete Permanently:: An optional boolean. If selected, the action uses permanent deletion behavior for drive items.

Output metadata

ID Value

A required string. The identifier of the record that was deleted.

Lookup Object By Unique Criteria

Retrieves a single object from SharePoint using unique lookup criteria.

Configuration fields

Lookup Criteria

A required drop-down. The field used for the lookup. Available options depend on the selected object type.

Common options include: * ID for most object types. * Title for List. * Path for Drive Item. * default for Drive (uses the site default drive).

Input metadata

Additional fields depend on the selected object type and lookup criteria. Common requirements include: * Site ID. * List ID.

For Drive with default lookup criteria, Site ID is required.

Output metadata

The output message contains a single object. Common fields include: * id (string). * name (string). * createdDateTime (date-time). * lastModifiedDateTime (date-time).

Additional fields depend on the selected object type. For Drive Item objects, if Download To Maester is enabled and the item has a download URL, the output includes an internalUrl field.

Lookup Objects (plural)

Retrieves multiple objects from SharePoint. The action can emit records individually or as a single message.

Configuration fields

Emit Behavior

An optional drop-down. The default is Emit individually. Valid options:

  • Emit individually: emit each record as a separate message.

  • Emit All: emit all records in a single message as an array.

Input metadata

Query Parameters

An optional object. The action sends OData query parameters to the Microsoft Graph API. Parameters include: top, filter, orderby, select, and expand. The action applies the $ prefix automatically (for example, top becomes $top).

For top: The default is 100. The value must be between 1 and 100.

Output metadata

Emit individually

Each output message contains a single object. The output structure matches the selected object type.

Emit All

Each output message contains an object with a results array. Each element in results has the same structure as the individual emit records.

For Drive Folder Contents with Download To Maester enabled: Items with download URLs include an internalUrl field in the output.

Make Raw Request

Sends a custom HTTP request to the Microsoft Graph API. Use this action when you need functionality not covered by prebuilt actions.

Configuration fields

None.

Input metadata

URL

A required string. The resource path relative to the base URL. It is the part of the path after https://graph.microsoft.com/v1.0.

Method

A required string. The HTTP verb to use in the request. Allowed values: GET, POST, PUT, PATCH, and DELETE.

Request Body

An optional object. The body of the request to send.

Output metadata

Status Code

A required number. The HTTP status code of the response.

Headers

A required object. The HTTP headers of the response.

Response Body

An optional object. The HTTP response body.

Upsert Object

Creates a record or updates an existing one depending on the selected operation and the presence of a record ID.

Configuration fields

Object Type

A required drop-down. The SharePoint entity to create or update.

For Create, supported options include: * List. * List Item. * Site Column. * List Column. * Drive Item (Metadata). * Drive Item (Content).

For Update, supported options include: * List Item. * Site Column. * List Column. * Drive Item (Metadata). * Drive Item (Content).

Input metadata

The input schema is generated dynamically based on the selected object type and operation. It contains all writable fields for that entity.

For Drive Item (Content): File URL:: A conditional required string. Required when Text Content is not provided.

Text Content

A conditional required string. Required when File URL is not provided.

Output metadata

The output matches the record returned by Microsoft Graph for the selected object type. Common fields include: * id (string). * name (string). * createdDateTime (date-time). * lastModifiedDateTime (date-time).

Additional fields depend on the selected object type.

For Drive Item (Content), Create creates a new file, and Update replaces the content of an existing file.

Examples

Example 1: Create Drive Item (Metadata): Create a Folder

{
  "siteId": "1234567890abc",
  "parentId": "root",
  "name": "My New Folder",
  "description": "A folder for organizing documents",
  "folder": {},
  "conflictBehavior": "rename"
}

Example 2: Update Drive Item (Metadata): Update File Metadata

{
  "siteId": "1234567890abc",
  "idValue": "01ABC123DEF456GHI789",
  "name": "Updated Document.pdf",
  "description": "Updated description for the document"
}

Example 3: Create List

{
  "siteId": "1234567890abc",
  "displayName": "Project Tasks",
  "description": "A list to track project tasks and milestones",
  "list": {
    "template": "genericList",
    "hidden": false
  }
}

Known limitations

  • For the polling trigger, when the polling object type is List Items, List ID must be provided in addition to Site ID.

  • When authenticating credentials, you must have an active Azure AD session and the registered application must have the appropriate permissions granted.

  • File size limits: when downloading files to Maester storage, files must not exceed platform file size limits.

  • Drive item creation (using Create with Drive Item (Content)) only supports files up to 250 MB.

  • Drive item permanent deletion requires the Drive ID. It uses a POST request to the drive item’s permanent delete endpoint.

  • Concurrent login limitations: Microsoft Graph API restrictions exist when multiple users authenticate simultaneously using the same credentials. This is a Microsoft-imposed limitation and cannot be resolved at the component level.