Set up a Procore connector

This connector is in beta. This means it’s undergoing ongoing testing and development while we gather feedback, validate functionality, and improve stability. Beta connectors are generally stable, but they may have limited feature support, incomplete error handling, or occasional issues.We recommend closely monitoring workflows that use this connector and contacting our Support team with any issues or feedback.

Capabilities

Resource	Sync	Provision
Accounts
Projects
Companies

The Procore connector supports automatic account provisioning. This connector does not support account deprovisioning. You must deprovision accounts directly in Procore.

Account provisioning configuration notes

When configuring account provisioning for Procore, you must include the Procore companyId of the company newly created accounts should be assigned to. Pass this ID as a string, in the form "555134325726800". Optionally, you can pass the Procore vendorId to the new account as well.

Gather Procore credentials

Configuring the connector requires you to pass in credentials generated in Procore. Gather these credentials before you move on.

A user with the permission to create apps in Procore must perform this task.

Create a Procore app

In the Procore Developer Portal, navigate to My Apps > Create a New App.

Give the new app a name, such as “C1”.

Click Create.

Next, go to the new app’s configuration page.

Click Data Connector Components and click to enable Service Account at both the Company and Project levels.

Give the app the following permissions:

Manage companies
Manage projects
Manage users

Carefully copy and save the app’s Client ID and Client Secret.

Add the app to App Management

Next, navigate to Select an App > App Management.

Locate your new app and click View.

Click the Permissions tab.

Select the projects the app will be available in from the Permitted Projects menu.

Click Add.

Enable project directories

For each Procore project you want to provision using C1:

Navigate to the project’s admin settings and click Tools.

Enable the project directory.

Done. Next, move on to the connector configuration instructions.

Configure the Procore connector

To complete this task, you’ll need:

The Connector Administrator or Super Administrator role in C1
Access to the set of Procore credentials generated by following the instructions above

Cloud-hosted
Self-hosted

Follow these instructions to use a built-in, no-code connector hosted by C1.

In C1, navigate to Integrations > Connectors and click Add connector.

Search for Procore and click Add.

Choose how to set up the new Procore connector:

Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with C1)
Add the connector to a managed app (select from the list of existing managed apps)
Create a new managed app

Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of C1 users. Setting multiple owners is allowed.If you choose someone else, C1 will notify the new connector owner by email that their help is needed to complete the setup process.

Click Next.

Find the Settings area of the page and click Edit.

Enter the Procore credentials into the relevant fields.

Click Save.

The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

Done. Your Procore connector is now pulling access data into C1.

Follow these instructions to use the Procore connector, hosted and run in your own environment.When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1 UI for access reviews and access requests.

Resources

Official download center: For stable binaries (Windows/Linux/macOS) and container images.
GitHub repository: Access the source code, report issues, or contribute to the project.

Step 1: Set up a new Procore connector

In C1, navigate to Integrations > Connectors > Add connector.

Search for Baton and click Add.

Choose how to set up the new Procore connector:

Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with C1)
Add the connector to a managed app (select from the list of existing managed apps)
Create a new managed app

Click Next.

In the Settings area of the page, click Edit.

Click Rotate to generate a new Client ID and Secret.Carefully copy and save these credentials. We’ll use them in Step 2.

Step 2: Create Kubernetes configuration files

Create two Kubernetes manifest files for your Procore connector deployment:

Secrets configuration

# baton-procore-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-procore-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>

  # Procore specific credentials
  BATON_CLIENT_ID: <Procore app client ID>
  BATON_CLIENT-SECRET: <Procore app client secret>

  # Optional: Include if you want C1 to provision access using this connector
  BATON_PROVISIONING: true

See the connector’s README or run --help to see all available configuration flags and environment variables.

Deployment configuration

# baton-procore.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-procore
  labels:
    app: baton-procore
spec:
  selector:
    matchLabels:
      app: baton-procore
  template:
    metadata:
      labels:
        app: baton-procore
        baton: true
        baton-app: procore
    spec:
      containers:
      - name: baton-procore
        image: public.ecr.aws/conductorone/baton-procore:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-procore
        envFrom:
        - secretRef:
            name: baton-procore-secrets

Step 3: Deploy the connector

Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.

Check that the connector data uploaded correctly. In C1, click Apps. On the Managed apps tab, locate and click the name of the application you added the Procore connector to. Procore data should be found on the Entitlements and Accounts tabs.

Done. Your Procore connector is now pulling access data into C1.

Set up a PrivX connector

Set up a Productboard connector

⌘I

Welcome

Manage connectors

Deploy connectors

Upload connector data

Configurable connectors

Pre-built connectors

Set up a Procore connector

Capabilities

Account provisioning configuration notes

Gather Procore credentials

Create a Procore app

Add the app to App Management

Enable project directories

Configure the Procore connector

Resources

Step 1: Set up a new Procore connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector

​Capabilities

​Account provisioning configuration notes

​Gather Procore credentials

​Create a Procore app

​Add the app to App Management

​Enable project directories

​Configure the Procore connector

​Resources

​Step 1: Set up a new Procore connector

​Step 2: Create Kubernetes configuration files

​Secrets configuration

​Deployment configuration

​Step 3: Deploy the connector

Capabilities

Account provisioning configuration notes

Gather Procore credentials

Create a Procore app

Add the app to App Management

Enable project directories

Configure the Procore connector

Resources

Step 1: Set up a new Procore connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector