We're excited to announce an enhancement to the Procore–Box integration that improves how project documentation is synchronized to Box.
Previously, the integration synchronized only Drawings, RFIs, and Submittals, and did so without pulling in supporting files. With this release, we have expanded our one-way sync capabilities to include additional Procore tools and introduced attachment synchronization for supported record types. This allows eligible attachments to be synchronized to Box alongside their corresponding PDF documents.
This allows users to access both the generated PDF and all supported attachments from a single location.
The integration synchronizes supported information from Procore to Box.
One-way synchronization: Information is transferred from Procore to Box only.
PDF generation: Supported Procore records are synchronized as PDF documents.
Automatic updates: Changes to supported records in Procore can trigger synchronization of the updated information.
Organized folders: Records are grouped into folders according to the tool and record structure.
Attachment synchronization: Eligible attachments are placed in a dedicated folder alongside the corresponding PDF.
No reverse sync: Changes made in Box do not synchronize back to Procore.
Open your Procore–Box integration in SyncEzy.
Navigate to the project configuration or Add Project to Sync section.
Select the project you want to configure.
Open the project tools or sync options.
Enable the supported tools you want to synchronize.
Select the destination location in Box, if prompted.
Save the configuration.
For the additional tools described in the reference article, the connected Procore user must have Admin-level access to each applicable tool at the project level.
Inspections limitation: Only Pass/Fail-type inspections are supported .
SyncEzy organizes synchronized information into dedicated folders within the selected project destination. The folder hierarchy helps users locate records by tool, template, and document type.
Overall Tool Folder Structure
Parent Root Folder
├── Commitments/
│ └── PDFs/
│ ├── [Commitment PDF file]
│ └── [Commitment Attachment Folder]
├── Drawings/
│ └── [Area Name]/
│ └── [Discipline]/
│ └── [Drawing PDF file]
├── Forms/
│ └── [Form Template Name]/
│ └── Completed Forms/
│ ├── [Form PDF file]
│ └── [Form Attachment Folder]/
├── Incidents/
│ └── PDFs/
│ └── [Incident PDF file]
├── Inspections/
│ └── [Inspection Template Name]/
│ └── PDFs/
│ ├── [Inspection PDF file]
│ └── [Inspection Attachment Folder]/
├── Observations/
│ └── PDFs/
│ ├── [Observation PDF file]
│ └── [Observation Attachment Folder]/
├── RFIs/
│ ├── [RFI Name].pdf
│ └── [RFI Name] (Attachment Folder)/
│ ├── [Main Attachments]
│
└── Submittals/
├── [Submittal Name].pdf
└── [Submittal Name] (Attachment Folder)/
└── [Main Attachments]
Attachment folders are created in the same Box location as the corresponding PDF, providing a complete view of the record and its supporting documents.
When a supported record has eligible attachments, the integration creates a dedicated attachment folder alongside its corresponding PDF.
For example, an RFI named RFI-123 – Door Hardware Clarification may be organized as follows:
RFIs/
├── RFI-123 - Door Hardware Clarification.pdf
└── RFI-123 - Door Hardware Clarification/
├── Door Hardware Schedule.xlsx
The attachment folder is created automatically and stored alongside the corresponding PDF.
| Procore tool | Supported attachments |
|---|---|
| RFIs | Files in the main Attachments section only |
| Submittals | Files in the main Attachments section only |
| Commitments | Files in the main Attachments section only |
| Forms | Files in the main Attachments section only |
| Inspections | Files in the main Attachments section only |
| Observations | Files in the main Attachments section only |
These attachments are stored in the corresponding attachment folder alongside the generated PDF.
The reference documentation does not include the following attachment types in the supported synchronization scope:
RFIs : Review and response attachments.
Submittals: Review and response attachments.
Commitments: Correspondence and response attachments.
Forms: Attachments associated with response, activity, or workflow actions.
Inspections: Response and activity attachments.
Observations: Response and activity attachments.
For example, if a Submittal has one file in its main Attachments section and another file attached to a review or response, only the file in the main Attachments section is included in the documented attachment-sync scope.
The same distinction applies to other supported record types: an attachment must be added in a supported location within the Procore record.
If a supported record has no eligible attachments, it continues to synchronize as a PDF without an attachment folder.
For example:
RFIs/
└── RFI-789 - Lighting Fixture Location.pdfIf eligible attachments are added later, the integration can create the corresponding attachment folder and synchronize the supported files during the applicable sync process.
For supported records, eligible attachments are synchronized into the corresponding attachment folder when the record is processed.
Existing records will continue to function normally.
If an existing RFI, Submittal, Commitment, Form, Inspection or Observation receives a new eligible attachment or is updated with eligible attachments, the integration will automatically:
No manual Box configuration is required.
Where the Box integration provides manual synchronization through File Manager:
Open your integration in SyncEzy.
Navigate to File Manager.
Select the relevant project.
Open the applicable module, such as RFIs, Submittals, Commitments, Forms, Inspections, or Observations.
Use the available Sync action to process the records.
The integration processes eligible records and attachments according to the configured sync behavior.
A new configuration option is available in Settings that allows you to define the naming convention for attachment folders.
You can select multiple fields that will be used when generating the folder name.
We recommend using the same fields that are currently configured for your PDF naming convention.
For example, if your PDF name uses:
Then the attachment folder should use the same fields:
RFIs/
├── RFI-123 - Door Hardware Clarification.pdf
└── RFI-123 - Door Hardware Clarification/
This provides a consistent and easy-to-navigate structure within Box.
The attachment synchronization feature supports:
Supported Attachments
The integration will synchronize attachments that are added directly to the record itself, including:
These files will be synchronized to Box and stored in the corresponding attachment folder.
Attachments added as part of reviews, responses, correspondence, or workflow activities are not currently synchronized for RFIs, Submittals, Commitments, Forms, Inspections or Observations.
For example, if a Submittal contains a file in the main Attachments section and another file attached as part of a Review/Response, only the file in the main Attachments section will be synchronized to Box.
The screenshots below highlight the attachment locations that are currently supported and unsupported:
With this release, the Procore–Box integration now provides a more complete synchronization experience by including main attachments for RFIs, Submittals, Commitments, Forms, Observations and Inspections
This enhancement helps ensure that eligible attachments associated with RFIs, Submittals, Commitments, Forms, Inspections, and Observations are synchronized and organized alongside their corresponding PDF documents in Box.
If you have any questions about this enhancement or need assistance configuring the new attachment synchronization settings, please contact our support team at support@syncezy.com.
We're happy to help with configuration, synchronization, and any questions regarding how this feature will work within your Box environment.
Support for response-level, activity-level, review, correspondence, and other workflow-related attachments is not currently available.