Procore logo

Procore

Extension app

By Fluidlabs

Contracts, change orders and directory records into agreement workflows, the signed document back on the Procore record.

View on the App Center ↗
Docusign App Center extensionUS region

Procore for Docusign IAM

A Procore Docusign integration that runs inside Workflow Builder: read a prime contract, commitment, change order or project directory record to pre-fill the agreement, write the signing outcome back to Procore, and attach the signed document to the record.

Procore for Docusign IAM is a Fluidlabs extension app listed on the Docusign App Center under the name Procore. Its steps appear natively in Docusign Workflow Builder, and Fluidlabs runs the app on its own infrastructure (US region, AWS), so there is no Zapier, Make or other automation platform to set up.

Install from App Center ↗Read the documentationCompliance review ↓
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.

Automation platforms (Zapier)

Zapier lists Docusign triggers and Procore actions on one page, such as Workflow Completed on the Docusign side and Create Prime Contract on the Procore side. The automations run on Zapier and suit teams that already run their automations there.

This app

Procore for Docusign IAM (this app)

Runs inside Docusign Workflow Builder: a Read step pulls a contract, change order, company or user into the workflow, the document goes out pre-filled, a Writeback records the signing outcome on the same Procore record, and File Upload attaches the signed document to it. Choose it when the agreement process itself runs on Docusign IAM and needs Procore data in and out.

Capabilities

What it adds inside Workflow Builder

Once installed, the app's actions appear as native workflow steps. No code, no separate automation platform, no sync jobs to run.

Read from Procore

Retrieve a prime contract, a commitment subcontract or purchase order, a change order, a project company or a project user, and expose the fields you select as workflow variables. Identify the record by matching its Procore Id, for example to an object_id passed at the workflow start.

Writeback to Procore

Update an existing record, create a new one, or Update or Create in a single step, for example to mark a subcontract as executed after signing. Map fields from the step that produced the new values, such as Send Documents for Signature, so Procore receives the signing outcome rather than the original data.

File Upload to Procore

Attach the signed document to a prime contract, a subcontract or purchase order, or a change order: pick the drive for that object and put the record's Id in the folder. The Docusign Documents drive saves a file in the project's Documents without attaching it to a record.

Private or shared connections

A connection links the app to one Procore company and one project, as a Private connection for one user or a Shared one for the team. Name each connection after its project, and add a connection for each further project without reinstalling the app.

Live in an afternoon

To connect Procore to Docusign, install the app from the App Center like any Docusign extension, authorize your Procore account, and add the steps to a workflow. Full setup, configuration and known behaviors are covered in the documentation.

1

Install from App Center

One click from the official listing into your Docusign account.

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 run on it

Subcontracts

A subcontract signed, filed and marked executed

Read from Procore reads the commitment subcontract, Prepare eSignature Template pre-fills it, and after signing File Upload attaches the signed subcontract to the record while a Writeback sets Executed, the Signed Contract Received Date and Status.

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.

Change orders

The signed change order attached to its record

File Upload to Procore attaches the executed envelope to the prime contract or commitment change order it belongs to, using that change order's drive and its Id in the folder, so the signed paperwork sits with the record 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.

Download the certificate (PDF)
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.

Download the Service Terms (PDF)
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, published on the Docusign App Center 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.
Is this the official Procore integration for Docusign?
It is a Fluidlabs app, not one from Procore or Docusign. Fluidlabs, a Docusign Build IAM Specialized Partner, built it, operates it and supports it, and it is listed on the Docusign App Center under the name Procore, with Fluidlabs as the publisher. Procore publishes its own Docusign integration in the Procore App Marketplace.
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 a contract, change order, company or user from Procore, sends a pre-filled document, writes the signing outcome back to the same record and attaches the signed file. Teams that run their agreement process on Docusign IAM use this app; teams whose documents already live in Procore tools can use Procore's.
Do I need Zapier or Make to connect Procore and Docusign?
No. The steps appear natively in Docusign Workflow Builder once you install the app from the Docusign App Center, and Fluidlabs runs the app on its own infrastructure. There is no Zapier, Make or other automation platform to set up, and no sync jobs to monitor.
Which Procore records can the workflow read and write?
Eight objects: Prime Contracts, Prime Contract Change Orders, Potential Change Orders, Commitment Subcontracts, Commitment Purchase Orders and Commitment Change Orders, plus the Project Users and Project Companies of the project's directory. The Read step exposes the fields you select as variables, and the Writeback step updates or creates records of the same object.
Where can the signed file be stored in Procore?
On the record it belongs to, in its Attachments, and in the project's Documents. File Upload has a drive for each contract and change order object, and the record's Id goes in the folder. The Docusign Documents drive saves a file in Documents without attaching it, for project users, project companies and documents with no record in Procore.
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 to Procore 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, a Procore account with access to the company and project you want to connect, and a Procore company admin to install the app in Procore once.
Where does our project data go?
Project 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 the app under ISO 27001 certification, hosted in the US region on AWS.
How long does setup take?
The install is a short sequence: search for Procore in the Docusign App Center, click Install App, then Install and Authorize. A Procore company admin then installs the app in Procore once, under App Management. Click Connect Account, choose a Private or Shared connection, name it, sign in to Procore and pick the company and project. The three Procore steps are then available in Workflow Builder, and building the workflow takes as long as your process needs.
What does support look like?
Named support at docusign-support@fluidlabs.com, monitored weekdays 09:00-19:00 CET, with priority-based response targets set out in the Service Terms.
Can Fluidlabs build the workflow for us?
Yes. Fluidlabs builds Docusign extension apps and the Workflow Builder flows around them as a service. The team behind this app can design and configure your Procore agreement workflow end to end.

Need Procore to do more than the app covers?

The app covers the steps on this page. When you need a custom object, a module the app skips, or a sync on your own schedule, we scope that work as an integration and put a fixed price in writing. Enterprise Integration starts at $45,000.

Scope a custom integration →See Enterprise Integration →

Setup documentation

Install steps, configuration and known behaviors, kept current.

Read the docs →

All Fluidlabs integrations

Every app we run on the App Center, plus the roadmap.

Browse integrations →

Need a different app built?

We build, submit and operate App Center extension apps.

Extension-app development →

Ready to connect Procore?

Install in minutes, or talk to us about a workflow built around it.

Install from App Center ↗Book a 20-minute call