Procore
- Andrea Harvey
On This Page
Overview
The Procore connector in DryvIQ allows you to analyze, migrate, copy, and synchronize files between your Procore project documents and your cloud storage repositories and/or on-premise network file shares. The first step is to create the Procore connection by providing the connection information required for DryvIQ to connect to the project. The connector can be created using any Procore user account with permissions to access the project documents. Once the connector is created, you can use it to create the jobs needed to manage the content.
DryvIQ currently only supports connecting to specific projects under a company and not to the company itself.
Creating a Connection
Expand the Manage section in the left navigation menu.
Click Connections.
Click Add connection.
Select Procore as the platform on the Add connection modal.
Enter the connection information. Reference the table below for details about each field.
Click Sign in with Procore.
On the Log In modal, enter the required credentials and click Log In.Â
You will see a green "Connected” message on the bottom of the modal when DryvIQ establishes connection. (If the connection fails, verify the information you entered.)
Click Done.
Add connection modal for Procore
Â
Â
Â
Field | Description | Required |
|---|---|---|
Display as | Enter the display name for the connection. If you will be creating multiple connections, ensure the name readily identifies the connection. The name displays in the application, and you can use it to search for the connection and filter lists. If you do not add a display name, the connection will automatically be named “Procore.”  DryvIQ recommends you enter a name that more readily identifies the connection, especially if you will be creating multiple connections. | Optional |
Platform API Credentials | Required | |
Use the system default client credentials | Select this option to use the default DryvIQ client application credentials. |  |
Use custom client credentials | Select this option to use custom client credentials provided by your administrator. When selected, three additional fields will be available to enter the credentials. |  |
Domain | This field displays only when you select Use custom client credentials. Enter the Procore login URL: https://api.procore.com/ | Optional |
Client ID | This field displays only when you select Use custom client credentials. Enter the client ID required to access the the account. This value will be provided by your administrator. | Optional |
Client Secret | This field displays only when you select Use custom client credentials. Enter the client secret required to access the account. This value will be provided by your administrator. | Optional |
Â
Procore LoginÂ
Features and Limitations
Platforms all have unique features and limitations. DryvIQ’s transfer engine manages these differences between platforms and allows you to configure actions based on Job Policies and Behaviors. Use the Platform Comparison tool to see how your integration platforms may interact regarding features and limitations.Â
Supported Features | Unsupported Features | Other Features/Limitations |
|---|---|---|
Invalid characters: / < > : \ \\ | ? * | ||
File size maximum: N/A | ||
 | Path length maximum: 255 | |
 | Segment path length: N/A | |
 | Restricted types: N/A | |
 | No trailing whitespace before extensions | |
 | No trailing whitespace after extensions | |
 |  | |
 |  |
Rate Limits
The Procore API allows 3,600 calls per hour per client. For jobs set to run on a schedule, DryvIQ attempts to balance the rate limit and scale back on the content being handled to prevent reaching the limit. If DryvIQ can’t transfer all the content due to the hourly rate limit, the remaining content will be transferred as part of the next job run when the rate limit resets.
Service Accounts
To aid with tracking when using a Procore Service Account, you should ensure that “DryvIQ” appears in the Service Account name. Refer to the Procore support information regarding how to Add, Modify, or Delete a Service Account.
Instead of using a Service Account, another option is to create a user named “DryvIQ” and to approve the integration through this user. This user will act like a Service Account and allow you to implement permissions without using a Service Account.