This guide explains how to set up a SharePoint integration using Dashpivot and Flowsite. This workflow enables automatic syncing of forms, reports, and photos from Dashpivot into SharePoint folders, helping teams keep project documents organised and up to date without manual uploads. Both Dashpivot workflow templates and Sitemate Start account templates are supported for this integration.
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.
Prerequisites
Before you begin make sure you have the following:
Plan: All Plan Types
Permission: Dashpivot Contributor
Skills Required: Workflow Automation
Device Type: Computer/Browser
Subscription: Dashpivot, Flowsite, SharePoint
Step-by-Step Instructions
1. Access your Flowsite workspace
2. In the Connections tab, ensure you have connections with both Dashpivot & SharePoint. You will need to have access to SharePoint to set this up
3. Access the Flows tab
4. Select the green Add Flow button in the top right corner of the screen
5. Select the Save PDF Copy option at the bottom left, which should have the SharePoint icon
6. From there, you can set up the flow - you will need to enter the template ID and select the workflow column that will trigger the export. Then click 'Next'
7. At the 'Download form' stage, select your preferred Download content option:
Form only — exports the form as a PDF (existing behaviour)
Form with original photos — exports a ZIP file containing the PDF and all original photos attached to the form
Then click 'Next'.
8. At the 'Upload file' stage, you'll need to select:
The relevant SharePoint connection
The Site Name, which is the relevant SharePoint 'space'
You can also add your site using its URL. See Can’t find your SharePoint site? below
The Document Library, which is the SharePoint drive where the relevant folder(s) is located
The Upload Method, this is where you select what upload method you need for forms to be transferred
Manually Select Folder
You can select which folder the forms need to be transferred to.
You can directly navigate your SharePoint folders using the blue 'Select folder' button. Note: Only one folder can be selected
Filename Based Routing
You can select which parts of the filename to use for folder routing
Matching folders will be used if they exist - otherwise, new folders will be created automatically
Sharepoint filename routing depends on the template filename configuration in Dashpivot. Any changes made on the template will require reconfiguration of the filename routing
You can reference How to create custom PDF filenames for your exports in Dashpivot Web for custom filename configuration
Note: Entering a site URL is available in SharePoint Save PDF copy flows. It isn’t available in SharePoint Lists flows.
9. Under Editing existing forms, you can set the expected behavior to handle new versions of existing forms:
Create New: This means a new copy of the form is created in the SharePoint folder(s)
Overwrite: This will overwrite the existing form, with the new updated version
10. Click Done when ready
11. Select the green Save button in the top right corner to finalise the flow creation
12. Repeat for any other templates
If you see an error
Message | What to do |
Enter a SharePoint site URL, e.g. https://company.sharepoint.com/sites/site-name | This link isn’t a SharePoint site URL. Open the site in SharePoint and copy the URL again. |
Site not found or you don’t have access to it | Check the URL. Then make sure the Microsoft account used for this connection has access to the site. See Troubleshooting: Permission Errors. |
Microsoft connection expired. | Reconnect your Microsoft account in the Connections tab, then try again. |
Couldn’t find the site. Try again. | Something unexpected went wrong. Try again, and contact support if it keeps happening. |
Notes
Both Dashpivot workflow templates and Sitemate Start account templates are supported for SharePoint integrations.
When Form with original photos is selected, a ZIP file (not a PDF) is uploaded to SharePoint.
Template IDs can be found in the Dashpivot URL (between
/apps/and/forms/).You can use organisation-level or project-level template IDs depending on your use case.
Filename-based routing depends on the template filename configuration in Dashpivot and may require reconfiguration if changes are made.
Since the SharePoint connection is tied to the user who authorised it, if that user leaves your organisation the connection will break and existing flows will stop running. To resolve this, a new Microsoft connection must be created in Flowsite and each affected flow must be manually updated to point to the new connection. See How to Connect Systems in Flowsite for guidance.
Can’t find your SharePoint site?
The SharePoint Site list in the Upload file step may not show every site your connection can access. For example, sites stored in a different region of a Multi-Geo Microsoft 365 tenant may not appear. If your site isn’t in the list, add it with its URL:
In the Upload file step, open the SharePoint Site dropdown.
At the top of the list, click Can’t find your site? Enter its URL.
In SharePoint, open the site you want to use, then copy the URL from your browser’s address bar.
Paste the URL into the Site URL field. The site is selected once Flowsite finds it.
Choose the Document Library and continue setting up the flow as normal.
The site is now selected and shows by name in the SharePoint Site dropdown.
💡 Tips
You don’t need the site’s home page. A link to any page or document library in the site works, and Flowsite works out which site it belongs to.
Site URLs usually look like
https://yourcompany.sharepoint.com/sites/site-nameorhttps://yourcompany.sharepoint.com/teams/site-name.
FAQs
Do I need to create a new flow every time a new project or job folder is added in SharePoint?
Not necessarily. If you use Filename Based Routing, Flowsite can route forms to the correct folder automatically based on field values in the form — for example, a Project Name or Job Number field. If the matching folder already exists in SharePoint, Flowsite routes to it. If it doesn’t exist yet, Flowsite creates it automatically.
This means one flow can cover new projects or jobs as they’re added, without any manual flow setup each time. See the Filename Based Routing section above for setup instructions.
Creating flows programmatically via API or SharePoint trigger is not currently supported.
Can I route forms to a multi-level folder structure like Builder > Job > Document Type?
Yes — Filename Based Routing supports nested folder paths. You can reference multiple Dashpivot fields to build a folder path with as many levels as you need, for example:
{Builder} / {Job Number} / {Document Type}
Each segment maps to a field value on the form. If any folder in the path doesn’t exist in SharePoint, Flowsite creates it automatically.
Can Flowsite flows be created automatically via API or a SharePoint trigger?
No — flows must be set up manually in Flowsite. There is no API endpoint or SharePoint trigger for creating flows automatically. If Filename Based Routing doesn’t cover your use case, raise a feature request with Sitemate.




