Bluerithm + Procore Integration
The Bluerithm integration with Procore was created to automate common overlapping workflows and activities between the platforms.
There are two types of connections available with the Bluerithm + Procore Integration:
- Embedded dashboards
- Data integration to synchronize Procore Observations and Bluerithm Issues
With this feature, you can display custom Bluerithm dashboards in Procore.
How to Connect a Custom Dashboard
First, create the dashboard(s) in the Bluerithm project that you want to embed in the Procore project. You can learn how to do that in this KB article.
To set up a dashboard in Procore, copy the dashboard ID from the 'Manage Sharing' dialog in the Bluerithm project:
In Procore, from the Apps menu, click App Management.
Then Create Configuration
Enter a recognizable name for the dashboard and paste the dashboard ID you got from Bluerithm.
The dashboard will now be available from the list of Apps, which you can select and view in Procore.
Data Integration: Sync Procore Observations and Bluerithm Issues
Observations are assigned in Procore to project team members and are used similarly as Issues in Bluerithm.
How to Connect the Data Integration
Once logged in, you will be redirected to a page where you can select the Procore Project you would like the Bluerithm Project to be assigned to.
Observation Types that are available to the selected Procore Project are available to select as the default Observation Type. This is needed for Push functionality to push all previously existed Bluerithm Issues.
Observation and Issue Priorities
A configuration form in Bluerithm can be used to update all existing issue priorities in a single operation, if desired.
Observation Title and Issue Identifier
Current Data Integration Features
Synchronize Procore Observations and Bluerithm Issues
Push: When push is enabled any Issues created or updated will create/update the corresponding Procore Observation. Any Issues that previously existed before the Procore Project connection will be pushed via the Function App that runs every three minutes. Any issues that use custom Priorities will not be synced until the Issue is updated with the allowed Priorities.
Pull: When pull is enabled any Procore Observations created or updated will create/update the corresponding Issue. Any Observations that previously existed before the Procore Project connection will be pulled via the Function App that runs every three minutes.
Two-Way: Two-Way Sync implements both Push and Pull.
Continuous Sync: When the Continuous Sync option is selected in the Project Settings all changes are continuously synchronized between linked issues in Bluerithm and Procore regardless of the Sync Type (Push, Pull, Two-Way). The sync checks for the most recent update between the Issue (Entered Date, Last Owner Edit, Last Respondent Edit fields) and the Observation (Updated At field) and updates the latest changes.
NOTE: The profile that Procore Observations show for Created By, edits, etc. will be the Procore profile that was used to connect to the Procore project. It may be advisable to create a Procore profile specifically for Bluerithm to authenticate with so that Observations created and edited in Bluerithm are clearly shown as such in Procore. This Procore profile must have sufficient write privileges to create Observations.
Similarly, the profile that Bluerithm Issues will show Entered By, edits, etc. for will be the Bluerithm profile that was used to connect to the Procore project. It may be advisable to create a Bluerithm profile specifically to authenticate with Procore so that Issues created and edited in Procore are clearly shown as such in Bluerithm. This profile can be a guest profile so it won't count against your seat limit, but it must be set to an Account Admin role at least for the it's used to authenticate to the Procore project.
- Files will not be synchronized between the platforms.
- Procore comments to not support formatted text, so any formatting in Bluerithm comments, including any pasted images in the editor, will be removed when synced.