Using the SharePoint Integration in Streamline

This article explains how to add the SharePoint integration and how to include it as a step in your workflow. With SharePoint, you can upload files directly into your organization’s Microsoft enterprise content management platform, keeping documents secure and accessible.

Section 1: Connect the SharePoint Integration

Go to the Integrations tab

• Navigate to the Integrations tab on the left-hand side of your screen.
  

Click New Connection

• Select New Connection to view the list of available integrations.

• Use the search bar or browse the list to locate SharePoint.

💡 Tip: Use the category filter on the left to narrow down by integration type, in this case it would be "Event".

Name your connection

• Add a clear, identifiable name and description for this integration. Example: “SharePoint – HR Document Library” or “SharePoint – Marketing Files.”

Authenticate the integration

• You’ll be prompted to log in with your Microsoft account and authorize access to SharePoint.

• It's important to note the account you authenticate with will determine what shows up in the upcoming select sIte section. It's possible you may already be logged into your target SharePoint account via OAuth. 

Understand the permissions this integration requests

The SharePoint integration uses delegated Microsoft Graph permissions only. This means it always acts on behalf of the Microsoft account you authenticate with above, not as an independent, tenant-wide application.

• Sites.Read.All (delegated) — read site, file, and folder information for SharePoint sites the connected account can access.
• Files.ReadWrite.All (delegated) — upload and manage files in locations the connected account can access.
• offline_access — keeps the connection authenticated for workflows that run unattended, so you don’t have to re-authenticate before every run.

Because these are delegated permissions, Streamline’s effective access to SharePoint is always limited to what the connected Microsoft account itself is permitted to see and do. Access is bounded by both the Microsoft Graph scopes above and that account’s own SharePoint permissions.

💡 Tip: To control exactly which sites and document libraries Streamline can reach, connect using a dedicated Microsoft 365 account rather than a personal or admin account, and grant that account access only to the specific SharePoint sites and libraries you want this integration to use.

Note: During consent, Microsoft may describe these permissions broadly, for example “Read items in all site collections on your behalf” or “Have full access to all files you have access to.” This is standard Microsoft wording for these scopes. Actual access remains limited to what the connected account can reach, as described above.

Choose Site

• After authentication, you'll be asked to close the window. Click next on the original page and choose your SharePoint site. 

Complete setup

• Once finished with your settings, click Finish.

• The integration will appear on the Integrations homepage along with its connection status.

💡 Tip: You can rename or update the connection description at any time. Click the ⋮ (three dots) and select Edit details.

Section 2: Add the SharePoint Step to a Workflow

Open your workflow

• Navigate to your workflow and click the plus (+) button to add a new step.

• Select SharePoint as the option.

💡 Tip: Be sure to add this step after a file upload step (e.g., from a Form).

Name and configure the step

• Enter a name, then click to configure the step.

Select your SharePoint connection

• Choose the SharePoint integration you previously set up as your connection.

Choose the action type

• Select Upload file as the action type.

Configure file upload

• Site (required): Select the SharePoint site where files will be uploaded. The dropdown is populated based on the Microsoft account used during connection setup.


• Drive (required): Select the document library within the chosen site.


• Folder (optional): Browse and select a destination folder within the drive. If left empty, files upload to the root of the drive.


• Custom subfolder path (optional): Type or map a subfolder path below the selected folder. Separate segments with / to create nested subfolders (e.g., Region/Country/City). This field supports workflow data mappings, so you can dynamically route files based on form data or other step outputs. Note: long mapped values may exceed SharePoint folder name limits and block the upload.


• File(s) to upload: Select source file(s) from earlier workflow steps and define a file name. By default, a uniqueness stamp is appended to prevent naming conflicts. You can add multiple file rows, each with a different source and naming pattern.

💡 Tip: You can create multiple upload configurations using different naming patterns or folders.

Save and close

• Click the X in the upper-right corner to exit the step configuration.

• The SharePoint step is now added to your workflow.

Summary

That’s it! You’ve successfully:

• Connected the SharePoint integration

• Added a SharePoint upload step to your workflow

If you have questions or need help troubleshooting, reach out to your admin or contact support.