docusign.github.io

Procore Integration with Docusign Documentation

This is the documentation for the Procore integration with Docusign.

How to Install and Configure

Installing the App on Docusign

For more detailed instructions, please follow the Docusign guide

Step 2. Make sure you have Admin rights to install the Procore app from the Docusign App Center.

Step 3. Find the app and press “Install App”, then press “Continue”.

Step 4. After the app is installed, you’ll be asked to link it to your Procore workspace. Choose the connection type — Private or Shared.

Step 5. Continue by pressing the “Login” button.

Step 6. Select Procore company, project, then click “Continue to Docusign”.

If connected successfully, you can go to Docusign App Center Manage. To manage connections or uninstall the app, please press the three dots next to the app name.

How to Use the App

The Procore extension app bridges Docusign with your project data - automatically syncing signed documents, updating custom fields, and triggering workflows based on document events.

Whether you’re managing subcontractor agreements, change orders, or insurance documents, this extension ensures project teams always have access to the latest version and status - without leaving Procore. After installation, Procore options appear in the Workflow Builder.

You can start by creating a new workflow by following this link or pressing Agreements → Maestro Workflows → Create Workflow.

In the workflow, when adding a new step, you’ll see three Procore options:

File Upload – Upload the file from Procore to use it later for Workflow.
Writeback to Procore – Update or create new data directly in your Procore workspace.
Read from Procore – Retrieve row data (such as IDs or values) for use in other steps.

ℹ️ Configuring “Writeback” to Procore

Select “Writeback to Procore” from the app available options.

Select your connection, as well as the Procore object.

When you select Update or Create in the “Write setting,” the system will either update an existing value or create a new one. Ensure that you select the appropriate option based on your needs.

Add or remove fields that you are willing to write to. Be aware that “Fields” in this case are field names inside your Procore workspace.

After selecting fields, choose which Docusign fields to write to Procore.

Finally, select conditions for comparison and write back to Procore.
In the end, press Apply and proceed to the next Maestro steps.

ℹ️ Configuring “Read” from Procore

Select “Read from Procore” from the app available options.

Select your connection, as well as the Procore object.

Select your fields from which to read.

After pressing Apply, the “Read” step is successfully added to your workflow. You can now use the retrieved Procore data in the following steps.

ℹ️ Configuring “File Output” to Procore

The File Output step allows you to upload signed documents directly to Procore and attach them to specific objects like Prime Contracts.

Select “File Output” from the workflow step options.
Select your Procore connection.
Choose the target object type (e.g., “Prime Contracts”) as the destination drive.
Configure the file path to include the Project ID and Object ID using workflow variables:
- The path format should be: //filename.pdf
- projectId - The Procore project ID where the file will be uploaded
- objectId - The ID of the object (e.g., Prime Contract ID) to attach the file to
The file will be:
1. Uploaded to the Documents folder at: Documents/{objectType}/{objectId}/
2. Automatically attached to the specified object (e.g., Prime Contract)

Example: For a Prime Contract with ID 90529 in project 302381, the signed document will be stored in Documents/primeContracts/90529/ and linked to Prime Contract #90529.

Note: You can use values from a previous “Read from Procore” step to dynamically populate the projectId and objectId in the file path.

ℹ️ Using Project ID in Workflow Steps

By default, all Procore API calls use the project selected during the initial connection setup. However, you can override this by specifying a project_id field in your workflow steps, allowing a single workflow to work with multiple Procore projects.

How It Works

Default Behavior: If project_id is not specified, the connection’s default project is used (set during OAuth setup)
Override Behavior: Include project_id in your Read or Writeback step to use a different project

Using project_id in Read Steps

When configuring a “Read from Procore” step, you can add project_id as a filter condition:

Add a filter condition with field project_id
Set the operator to EQUALS
Provide the project ID value (can be a literal or from a previous workflow step)

The project_id will be used for API routing but will not be included in the actual search comparison. This means you can combine it with other filters:

project_id EQUALS 12345 AND status EQUALS "approved"

In this example, the API call targets project 12345, and only records with status “approved” are returned.

Using project_id in Writeback Steps

When configuring a “Writeback to Procore” step (Create or Update), you can include project_id as a field:

Add project_id to your field mappings
Map it to a value (literal or from a previous step like trigger inputs)

Note: For most object types (Prime Contracts, Project Users, Project Vendors), project_id is used only for API routing and is not sent in the request body. For Change Order Packages, project_id is included in both the URL and request body as required by the Procore API.

Example: Multi-Project Workflow

A workflow triggered from Procore can pass the project context through trigger inputs:

Trigger: Workflow receives project.id from Procore trigger inputs
Read Step: Use project_id filter with value from ``
Writeback Step: Include project_id field mapped to ``

This allows the same workflow to operate on different projects based on where it was triggered.

Supported Field Types

You can use the following Procore field types in Maestro workflows:

string
boolean

How to Reconnect the App

You can connect a Procore account to Docusign Maestro. When you connect to Maestro, you can build workflows that read from and write to your Procore data. If you experience problems with your Procore connection, you can reconnect Maestro and Procore.

Use this procedure to reconnect the application:

Log in to your Docusign eSignature account with account administrator credentials.
In a new browser window, go to the appropriate environment for your account (Production or Demo).
Select the Procore icon and click “Manage Connections”.
Select the three-dot menu icon next to a connection and choose “Reconnect”.

The page refreshes.

File Attachment and Side Panel support by Procore Object Type

CTO Object	Supports File Attachment	Procore Screen	Supports Side Panel
`primeContracts`	Yes	Financials > Prime Contracts	No
`changeOrderPackages`	No	Financials > Change Orders	Yes
`projectUsers`	No	Directory > Users	Yes
`projectVendors`	No	Directory > Vendors	Yes