f64e132a-0cf7-4760-8317-c3468fac32b3.A connection is tied to one Procore company and one project. For another project, add another connection.
Select an object in the Procore object dropdown of a Read or Writeback step.
These objects support Read, Writeback, and File Upload:
These objects support Read and Writeback, with limited File Upload:
They have no File Upload drive of their own. The Docusign Documents drive saves a file to the project's Documents without attaching it to a record, see File Upload to Procore.
Procore uses the word "company" in two senses: the company account that owns your projects, and the companies added to a project. The Project Companies object works with the second kind.
This section describes how Prime Contracts, Prime Contract Change Orders, and Potential Change Orders behave on read and write. On a project with 2 change order tiers, Potential Change Orders are grouped into a Prime Contract Change Order. The app supports projects with 1 or 2 tiers, see Change order tiers.
Fields: Id, Number, Title, Status, Executed, Description, Grand Total, Actual Completion Date, Architect Name, Architect ID, Contract Estimated Completion Date, Contract Start Date, Contract Termination Date, Contractor Name, Contractor ID, Exclusions, Inclusions, Private, Signed Contract Received Date, Substantial Completion Date, Vendor Name, Vendor ID, Created At.
Read only: Id, Grand Total, Architect Name, Contractor Name, Vendor Name, Created At.
Draft, Out For Bid, Out For Signature, Approved, Complete, Terminated.false to show it to every project member.Fields: Id, Number, Title, Status, Contract ID, Executed, Private, Description, Schedule Impact Amount, Due Date, Paid Date, Invoiced Date, Signed Change Order Received Date, Revised Substantial Completion Date, Grand Total, Designated Reviewer Name, Designated Reviewer Id, Created By Name, Created By Id, Reviewed At, Created At, Updated At.
Read only: Id, Grand Total, Designated Reviewer Name, Created By Name, Created By Id, Reviewed At, Created At, Updated At.
Fields: Id, Number, Title, Status, Contract ID, Executed, Description, Grand Total, Schedule Impact Amount, Due Date, Paid Date, Invoiced Date, Signed Change Order Received Date, Private, Location ID, Reference, Paid, Batch ID, Revision, Change Reason, Change Reason Id, Created By Name, Created By Id, Designated Reviewer Name, Designated Reviewer Id, Request Received From Name, Request Received From Id, Created At, Updated At, Reviewed At.
Read only: Id, Grand Total, Paid, Revision, Change Reason, Created By Name, Created By Id, Designated Reviewer Name, Request Received From Name, Created At, Updated At, Reviewed At.
Approved prime contract. Any other status fails the step. Contract ID is required on Create and cannot be changed later.draft, so map both.The same values apply to Prime Contract Change Orders, Potential Change Orders, and Commitment Change Orders. Write the label as Procore shows it or the stored value, in any letter case. Status reads as the stored value.
| Label in Procore | Stored value |
|---|---|
| Draft | draft |
| Pending - Pricing | pricing |
| Pending - Not Pricing | not_pricing |
| Pending - In Review | pending |
| Pending - Revised | revised |
| Pending - Proceeding | proceeding |
| Pending - Not Proceeding | not_proceeding |
| Pending Billable | pending_billable |
| No Charge | no_charge |
| Approved | approved |
| Rejected | rejected |
| Void | void |
Procore keeps subcontracts and purchase orders in the Commitments tool. The app exposes them as two objects, Commitment Subcontracts and Commitment Purchase Orders, plus Commitment Change Orders for the change orders on either kind.
Commitment Subcontracts: Id, Number, Contract Company Name, Contract Company Id, Title, Status, Executed, Default Retainage, Description, Contract Date, Issued On Date, Grand Total, Created By Name, Inclusions, Exclusions, Contract Start Date, Contract Estimated Completion Date, Actual Completion Date, Signed Contract Received Date, Created At, Updated At.
Commitment Purchase Orders: Id, Number, Contract Company Name, Contract Company Id, Title, Status, Executed, Default Retainage, Description, Contract Date, Issued On Date, Grand Total, Created By Name, Assigned To Name, Assigned To Id, Bill To, Payment Terms, Ship To, Ship Via, Delivery Date, Signed Purchase Order Received Date, Created At, Updated At.
Read only: Id, Contract Company Name, Grand Total, Created By Name, Assigned To Name, Created At, Updated At. Every other field can be written.
A contract created from a workflow has no schedule of values, so Grand Total is 0. Add the line items in Procore to get the right total.
Draft and Number continues the project's sequence for that type, including a manual suffix: after SC-115-0822 comes SC-115-0823.Out For Signature only when it has a Contract Company.true or false. yes / no and 1 / 0 also work.| Object | Status values |
|---|---|
| Commitment Subcontracts | Draft, Out For Bid, Out For Signature, Approved, Complete, Terminated, Void |
| Commitment Purchase Orders | Draft, Processing, Submitted, Partially Received, Received, Approved, Closed |
⚠️ With Update or Create, map Number as a field to write as well. The value in the match rule is not written to a new record, so the new contract gets the next number and the next run creates another one.
One object covers change orders on subcontracts and on purchase orders.
Fields: Id, Number, Title, Status, Contract ID, Executed, Description, Reference, Grand Total, Schedule Impact Amount, Due Date, Paid Date, Invoiced Date, Signed Change Order Received Date, Private, Change Reason, Change Reason Id, Location Id, Created By Name, Created By Id, Designated Reviewer Name, Designated Reviewer Id, Request Received From Name, Request Received From Id, Created At, Updated At, Reviewed At.
Read only: Id, Grand Total, Change Reason, Created By Name, Created By Id, Designated Reviewer Name, Request Received From Name, Created At, Updated At, Reviewed At.
Each Procore project sets the number of change order tiers per tool (Commitments, Prime Contracts) under Configure Settings. The app supports projects with 1 or 2 tiers. 3-tier projects are not supported.
Project Companies are the companies listed in the project's Directory under Companies. Your own company is in the list too, marked YOUR COMPANY.
Id, Name, Abbreviated Name, Trade Name / DBA, Email Address, Business Phone, Business Fax, Website, Address, City, State Code, ZIP, Country Code, License Number, Labor Union, Tags/Keywords, Primary Contact ID, Primary Contact First Name, Primary Contact Last Name, Primary Contact Email Address, Primary Contact Business Phone, Primary Contact Cell Phone, Entity Type, Entity Type Number, Created At, Updated At.
Read only: Id, Primary Contact First Name, Last Name, Email Address, Business Phone, Cell Phone, Created At, Updated At.
The fields come from the General tab of the company. Bidder Info, Insurance, Attachments, Logo, and Project Roles are not part of the object.
IL and US.ein or abn. Entity Type Number has no dashes: 12-3456789 reads as 123456789.+1 217-555-0101 does not match 217-555-0101, and a website does not match without https://.il is saved as IL.EIN or ABN. Procore removes dashes and spaces from the number.Project Users are the people listed in the project's Directory under Users.
Fields: Id, Name, First Name, Last Name, Email Address, Initials, Job Title, Business Phone, Business Phone Extension, Cell Phone, Business Fax, Address, City, State Code, ZIP, Country Code, Is Active, Tags/Keywords, Permission Template ID, Vendor ID, Vendor Name, Created At, Updated At.
Read only: Id, Name, Initials, Is Active, Vendor Name, Created At, Updated At. Procore sets Initials from the name.
US and IN, not United States and Indiana.The rules are the same as for Project Companies: Id overrides every other condition, text matches in any letter case, phone numbers match as stored, and an empty value stops the step.
YYYY-MM-DD or an ISO 8601 date-time. The date part is used as written, the time and zone are dropped. 09/10/2026 or 10.09.2026 stops the step.2026-10-01T00:00:00Z.When File Upload cannot attach the file to a record, it still saves the file in the project's Documents in Procore, and the step does not fail.
Documents/Prime Contracts/Signed/12345/.Documents/Docusign/, in a folder named after the drive, followed by your folders.Look for the file in Documents when it does not appear on the record's Attachments.
Open the Docusign App Center and search for Procore.
Click the Procore app card, then click Install App.
Review the access the app requests and click Install and Authorize.
The app now appears with an Installed status. Install the app in Procore before you connect your account.
A Procore company admin installs the app once for the company.
In Procore, open Apps in the top bar and click App Management.
Click Install App and choose Install Custom App.
Enter the App Version ID f64e132a-0cf7-4760-8317-c3468fac32b3 and click Install.
⚠️ Installing by App Version ID is the current way to add the app to Procore. Installation from the Procore Marketplace will be added later.
On the installed app page, click Connect Account.
Connection Visibility: choose how the connection is shared, then click Next:
Name Connection: enter a name that identifies the company and project, for example Demo-Company-Project555. It appears in workflow steps. Click Log In.
Sign in to Procore if you are not signed in already. On the Allow access? screen, click Allow.
Choose your Procore company: select your Procore company account, not a company inside a project, and click Continue.
Choose your default project: select the project the connection works with and click Finish & return to Docusign.
The connection is added and ready to use in workflow steps. Every step of this connection works with the project you picked.
On the Procore app page, open the Manage dropdown and select Manage Connections to see every connection.
Use the three-dot (⋮) menu next to a connection:
Use Manage → New Connection on the app page, or + New Connection on the Connections page. Add one connection per project; each appears separately in workflow steps.
Log in to Docusign and go to Agreements → Workflows.
Click Create Workflow.
Build your workflow using the available steps, including the Procore actions.
Publish the workflow when it is ready.
Click + Add Step and search for Procore:
A typical subcontract signing flow:
The Read from Procore step retrieves a record and exposes its fields as workflow variables.
In this example the workflow starts From an API Call and receives the Id of the record to read.
On the workflow canvas, click Add workflow start.
Select a method: choose From an API Call.
Set up variables: add a Text variable named object_id.
Process type: choose Automated process and click Apply.
Once published, the workflow has a URL your external system calls, passing object_id.
On the workflow canvas, click + below Start Workflow.
Search for Procore and select Read from Procore.
Connection: select the connection you created during installation.
Procore object: choose one of the supported objects. This example uses Commitment Subcontracts.
Click Next.
Click Add or Remove Fields and tick the fields your workflow needs. The selected fields become workflow variables for later steps.
The fields of each object are listed under Prime Contracts, Commitments, and Other Known Behaviors.
Click Next.
Create a rule that tells the step which record to read. In this example, match the Procore Id to the object_id variable from the workflow start:
object_id, under Variables From Workflow StartUnder How many records should this step return?, pick one:
Use preview this step to check the rule against live data. Click Apply.
How each object matches its fields is described under the object's section.
The Writeback to Procore step updates a record or creates a new one.
On the workflow canvas, click + where the writeback belongs, for example after Send Documents for Signature. Search for Procore and select Writeback to Procore.
Connection: select your Procore connection.
Procore object: choose the object to write to. In most workflows it is the object of your Read step.
Write settings:
Click Next.
Click Add or Remove Fields and tick the fields you want to write. Each selected field gets its own row; map it to the workflow variable that supplies the value.
Overwrite if field value exists decides what happens to fields that already hold a value in Procore:
⚠️ Map from the right source. The variable picker also lists the output of your Read from Procore step. Mapping from there writes the original values back unchanged. Map from the step that produced the new data, such as Send Documents for Signature or Collect Data with Web Forms.
Click Next.
Address the record by Id:
object_id from the workflow startVariables from a Procore step carry the object's short name, for example subcontracts / Id for Commitment Subcontracts. See Variable Prefixes.
Each step returns the Id of its own object. A Commitment Change Orders step returns the change order's Id; for the contract, use the Id from a Commitment Subcontracts or Commitment Purchase Orders step.
Click Apply.
Every variable from a Procore step starts with the object's short name.
| Object | Variable prefix |
|---|---|
| Prime Contracts | primeContracts |
| Prime Contract Change Orders | primeCOs |
| Potential Change Orders | potentialCOs |
| Commitment Subcontracts | subcontracts |
| Commitment Purchase Orders | purchaseOrders |
| Commitment Change Orders | commitmentCOs |
| Project Users | projectUsers |
| Project Companies | projectCompanies |
The File Upload to Procore step saves a document produced earlier in the workflow to the project's Documents in Procore and attaches it to a record's Attachments.
Add a step after signing completes, search for Procore, and select File Upload to Procore.
Choose the file or envelope from an earlier step. In this example it is the Combined Envelope File from Send Documents for Signature.
An empty list means no earlier step in the workflow produced a file.
Each record drive attaches the file to a record of the same object and saves it in the project's Documents, in a folder named after the drive: the Commitment Subcontracts drive attaches to a subcontract and saves the file under Documents/Commitment Subcontracts/. Docusign Documents saves the file without attaching it, see The Docusign Documents Drive.
File Upload takes the Id of the record to attach to from the folder. Pick the drive of the object, then put the Id of the record in the folder: with the Prime Contracts drive, the folder holds the Id of the prime contract the file belongs to. With several folders, the Id goes in the last one, see Organizing Files in Folders.
Open the Select folder dropdown and pick New Subfolder.
In the New folder dialog, click Add Variable, choose the step that returns the record, and select Id. A Read or Writeback step on the same object returns it: for the Prime Contract Change Orders drive, take primeCOs / Id. The prefixes of all objects are listed under Variable Prefixes.
The variable appears in the Folder name field. Click Add.
Select folder now shows the Id variable. Click Next.
To keep the files in your own folders before the Id, see Organizing Files in Folders.
Build the file name from Add Text and Add Variable. A timestamp variable keeps repeat runs from producing identical names; : in the timestamp is saved as -.
Click Apply. On a record drive, the file lands on the record's Attachments. A second file on the same record is added next to the first.
If the file cannot be attached, the step still saves it in Documents. See File Upload Fallback.
The same folder logic works on every drive. Folders you add before the Id are created in Documents as you name them, and on a record drive the record is still taken from the last folder.
Pick New Subfolder, click Add Text, type a folder name, and click Add.
Click Add Subfolder for the next level, and repeat.
Add the record's Id as the last subfolder, then click Next.
Procore stores the file in a folder named after the drive, then your folders, then the Id:
Docusign Documents saves the file under Documents/Docusign/ in the folders you build, and attaches it to nothing. Use it to keep files for Project Users and Project Companies, which have no drive of their own: Procore does not let an app attach files to them yet. It also fits documents with no record in Procore. Folders work the same way as on any drive.
The step ran, but a field in Procore did not change.
The field already had a value and Overwrite if field value exists is unticked. Tick it on the step.
Update or Create created a second contract.
Map Number as a field to write, not only in the match rule. See Subcontracts and Purchase Orders.
A new Purchase Order has a Bill To and Ship To I did not set.
Procore copies them from the last Purchase Order in the project. Map both fields in the step.
How do I clear a field?
Not from a workflow. An empty value leaves the field as it is. Clear it in Procore.
The rule does not find a company I can see in Procore.
The company is inactive, or the phone number, website, or number in the rule is written differently from how Procore stores it. Copy the value as the Read step returns it.
Contract Company Id with a company name fails.
Two active companies in the project share that name. Use the company's Id.
The file is in Documents, but not on the record's Attachments.
The last folder did not hold the Id of a record on that drive. Put the Id from a step on the same object in the last folder. See File Upload Fallback.
A field or object I expect is missing from the step.
Open Manage Connections, click Reconnect on the connection, then reopen the step.