Procore logo
Coming to the Docusign App CenterIn developmentUS region

Procore for Docusign IAM

A Procore Docusign integration that runs inside Workflow Builder: read a project user or vendor from the Procore directory, send the paperwork for signature pre-filled, write the signed details back to the same record, and start the whole workflow from inside Procore with the Workflow Builder Launcher side panel.

In development for the Docusign App Center. The documentation is already published, so you can review the setup and the workflow steps before the app lists.

Compare the routes

Which Procore + Docusign route do you need?

Procore already offers a Docusign integration of its own, and it solves a different job from this app. Here is how the routes compare.

Procore's DocuSign integration

Procore's own integration sends documents from inside Procore tools for e-signature. Procore describes it as integrating with Correspondence, Documents, Project Financials, Invoicing and Portfolio Financials. Choose it when the document already lives in one of those tools and only needs a signature.

Generic connectors (Zapier, Make)

Middleware passes data between Procore and Docusign through automations that run outside both products. Flexible for one-off recipes, with the connection maintained in a third system.

This app

Procore for Docusign IAM (this app)

Runs inside Docusign Workflow Builder: a Read step pulls a project user or vendor into the workflow, the document goes out pre-filled, and a Writeback updates the same Procore record with what the signer entered. Choose it when the agreement process itself runs on Docusign IAM and needs directory data in and out.

Capabilities

What it will add inside Workflow Builder

Once installed, the app's actions will appear as native workflow steps. Every capability below is already described in the published documentation.

Read from Procore

Retrieve a Project User or a Project Vendor from the Procore directory and expose the fields you select as workflow variables. Identify the record by matching its Procore ID to the workflow's object_id, so a workflow started from a Procore record always reads the record it was launched from.

Writeback to Procore

Update an existing user or vendor, create a new one, or Update or Create in a single step. Map fields such as First Name, Last Name, City, State and Zip from the step where the values were finalised, typically Send Documents for Signature, so Procore receives what the signer entered rather than the original data.

File Upload to Procore

Attach the combined envelope file to a Procore record. Today the upload targets Prime Contracts, addressed by Project ID and the Prime Contract's own ID; the documentation lists the other targets as still in development.

Workflow Builder Launcher side panel

Start a published workflow from inside Procore. Open a user or a company in edit mode, open the launcher in the side panel, authorise Docusign once, and pick the workflow. Procore passes the record's ID, the project ID and the company ID into the workflow automatically.

Ready to run on day one

Once it lists, connecting Procore to Docusign will work like any Docusign extension: install the app from the App Center, authorize your Procore account, and add the steps to a workflow. The setup, configuration and known behaviors are already written up in the documentation.

1

Install from the App Center, once listed

One click from the listing into your Docusign account, the same as every Fluidlabs app.

2

Connect Procore

Authorize your Procore account and name the connection.

3

Add steps to any workflow

The Procore actions appear as native Workflow Builder steps.

What construction teams will run on it

Vendor paperwork

Onboarding a vendor from the directory record

Open the vendor in Procore, launch the workflow from the side panel, and let Read from Procore pull the company's details into the agreement. The signed pack comes back through the same workflow, and a Writeback updates the vendor record with the confirmed details.

People on the project

User agreements pre-filled from the Project Directory

For a project user, the workflow reads name and contact fields from Procore, sends the document pre-filled, and writes back the address or other details the signer completed, using Update or Create so new and existing records are handled by one workflow.

Filed on the contract

The signed document attached to the Prime Contract

File Upload to Procore stores the executed envelope against the Prime Contract, addressed by Project ID and contract ID, so the signed paperwork sits with the contract it belongs to rather than in a download folder.

Security & compliance

Built to pass your security review

The documents your security team will ask for exist, are current, and are ready to hand over. Terms of service and the privacy policy are published on this site.

ISO/IEC 27001:2022
Certified
SOC 2
In progress

EUR 1M technology and cyber insurance, evidenced on request.

Certification

ISO/IEC 27001:2022 certificate

Independently certified by Swiss Approval, current to May 2027 and verifiable through the issuing body.

Data processing

Standard DPA

GDPR, UK GDPR and Swiss FADP covered, with the EU standard contractual clauses incorporated. Read it now, request the version for signature.

Download the DPA (PDF)
Terms

Service Terms

Licence, support response targets, availability, IP and liability for your use of the extension apps. Personal data stays with the DPA.

Security overview

Security & Data Protection Overview

Certifications, hosting and encryption, access control, secure development, monitoring and incident response, in one document for your security assessment.

The Security & Data Protection Overview and the DPA prepared for signature are provided on request: , or email secops@fluidlabs.com.

FAQ

The Procore Docusign integration, answered

Does Procore integrate with Docusign?
Yes, in more than one way. Procore's own DocuSign integration sends documents from Procore tools such as Correspondence, Documents and Project Financials for signature. Procore for Docusign IAM, in development by Fluidlabs, a Docusign Build IAM Specialized Partner, works at the workflow layer instead: it adds Read, Writeback and File Upload steps for Procore inside Docusign Workflow Builder, and a side panel to launch workflows from a Procore record.
Is the Procore app available on the Docusign App Center yet?
Not yet. It is in development and the documentation is already live, so you can review the exact steps before the listing appears. Use the notify link on this page and we will tell you when it lists.
How is this different from Procore's own DocuSign integration?
Procore's integration starts in Procore and is built to get a document that already lives there signed. This app starts in Docusign: a Workflow Builder workflow reads directory data from Procore, sends a pre-filled document, and writes the result back to the same user or vendor record. Teams that run their agreement process on Docusign IAM use this app; teams that only need to sign Procore documents can use Procore's.
Which Procore records can the workflow read and write?
Project Users and Project Vendors, the people and companies listed in a project's directory. The Read step exposes the fields you select as variables, and the Writeback step updates or creates records of the same type.
What is the side panel for?
The Workflow Builder Launcher lets you start a published workflow from the record you have open in Procore. It passes the record's ID into the workflow as object_id, so the Read and Writeback steps operate on exactly that user or vendor with no manual input.
Where can the signed file be stored in Procore?
On a Prime Contract, addressed by the Project ID and the contract's own ID. The documentation lists file upload for other Procore targets as still in development.
Does it work with Docusign Maestro?
Yes. Maestro is now called Docusign Workflow Builder, and that is where the Procore steps run. Read from Procore, Writeback to Procore and File Upload are added to a workflow like any other step.
What do I need to use it?
A Docusign account with admin rights to install and manage apps in the App Center, and a Procore account where a connection can be created to a specific Procore company and project. The side panel is installed separately as the Workflow Builder Launcher.
Where does our project data go?
Directory data moves between Procore and your Docusign account at workflow runtime: the Read step pulls the fields you selected into workflow variables, and the Writeback and File Upload steps send data and signed files back to Procore. Fluidlabs operates its apps under ISO 27001 certification, hosted in the US region on AWS.
Can Fluidlabs build the workflow for us?
Yes. Fluidlabs builds Docusign extension apps and the Workflow Builder flows around them as a service, with the same documentation standard you can read here today.

Be first to know when Procore launches

Read the documentation today, or leave your email and we will tell you the day it lists on the App Center.