Skip to main content

SharePoint Forms Integration with Dashpivot via Flowsite

Learn how to integrate Dashpivot with SharePoint for archiving forms

Written by Lara Antoniolli

Introduction

This integration allows you to automatically save Dashpivot forms to a specific folder in your SharePoint site when a form reaches a workflow column. You can export the form as a PDF only, or as a ZIP file containing the PDF and all original photos attached to the form.

How it works

How Flowsite connects to SharePoint

Flowsite uses a User (Delegated) Consent flow to connect to SharePoint. This approach:

  • Requires a user login, and

  • Ties consent to the specific user who authorises the connection

You may choose to create a dedicated Microsoft Entra ID user account with the minimal required permissions to authorise the connection and utilise the integration. This may include only granting this user access to the specific SharePoint sites that will be used with the Flowsite integration.

Please note that Flowsite does not currently support the Admin (App-Only) Consent flow to connect to SharePoint.

Requirements:

  • In order to build this flow, you will need to connect Dashpivot and SharePoint to your Flowsite workspace

  • This integration is only available to customers on the Flowsite Pro+ plans

📓 Note on network drives

Flowsite connects directly to SharePoint document libraries. If your team accesses folders via a mapped network drive or Windows File Explorer, this will work as long as those folders are backed by SharePoint (e.g. synced via OneDrive for Business). Direct integration with on-premise network servers or file shares not connected to SharePoint is not supported.

Supported configurations

The following configurations are supported:

  • Dashpivot workflow templates and Sitemate Start account templates sending forms to SharePoint.

  • Export forms with original photos (ZIP delivery) — export the PDF and all original photos as a ZIP file uploaded to SharePoint

  • Different upload methods, by manually selecting destination folders or filename based routing

  • Option to overwrite existing forms when updates are made, or save as a new form to maintain all historical form data

  • Setting a root folder for filename based routing

  • Controlling folder formatting in SharePoint

  • Saving PDFs into a specific subfolder within an existing SharePoint folder structure (e.g. a project's "Section 8 — Site Returns" folder)

  • Folder name formatting (preserve original field values) — folder names can be set to preserve the original field value including casing, dots, and spaces, rather than converting to a slugified format. For example, a field value like "24.005 Parklife JV SMF" will create or match a folder named "24.005 Parklife JV SMF", not "24-005-parklife-jv-smf". This is useful when filing into an existing ISO or project folder structure where folder names must match exactly.

Did this answer your question?