Skip to content
←Back to Support

Integrations & Sharing

Troubleshoot Procore Integration in Taliho

Resolve the most common Procore issues in Taliho, from missing iframe launch paths to reconnect errors and unlinked projects.

6 min readUpdated March 11, 2026

When Procore integration issues show up, the fastest way to fix them is to identify which layer failed: Procore install and visibility, Taliho company connection, user OAuth, or project-level linking.

Start with these quick checks

Before you dive into a specific symptom, confirm:

Fast first checks
  • Taliho is installed or connected in the correct Procore company.
  • A Procore App Configuration exists and applies to the company or projects you are testing.
  • The user is authenticating with the same Procore company that was configured for Taliho.
  • The Taliho company still has access to the Procore integration based on its current plan or trial state.
  • The Taliho project is linked to a Procore project if the workflow needs project-specific data.

Symptom: Taliho does not appear in Procore at all

Likely cause:

  • the app was not installed in that Procore company
  • no App Configuration was created
  • the configuration was created but not applied to the project you are testing
  • company-level launch was expected, but company-level configuration was never enabled

Best next step:

Have a Procore Company Admin review the install in App Management, confirm the Configurations tab exists, and verify the configuration scope. If needed, use Procore's official references for What are App Configurations? and Create an App Configuration and Apply it to Projects.

Symptom: Taliho opens, but the user gets a message that Taliho is not connected to their Procore company

Likely cause:

  • the user selected the wrong Procore company during connection
  • the app is not actually installed or connected for that Procore company

Best next step:

Ask a Procore Company Admin to confirm Taliho is installed for the same company the user selected. Then retry the Taliho connection flow and choose the correct company if the selection screen appears.

Symptom: The user lands on a reconnect or oauth error flow

Likely cause:

  • the user's Procore OAuth token is no longer valid
  • the user needs to reconnect from Taliho
  • the browser lost the embedded handoff and fell back to a popup or redirect flow

Best next step:

Reconnect from Settings > Integrations in Taliho. Retry in the same browser session, allow popups if the browser blocks them, and avoid switching accounts mid-flow.

Symptom: The company can connect Procore, but users still cannot fetch drawings, tools, or other live project data

Likely cause:

  • the Taliho project is not linked to a Procore project
  • the QR code or group belongs to a Taliho project that is not connected to Procore

Best next step:

Open the Taliho project in create or edit mode and link it to the correct Procore project. Then retry the Procore-backed workflow.

This is especially important for drawing codes, locations, and fetch flows that depend on project-specific Procore data.

Symptom: A user can see the integration, but cannot edit Procore items from Taliho

Likely cause:

  • the company integration is connected, but Allow Procore Item Edits is turned off

Best next step:

Have an admin open Settings > Integrations in Taliho and review the Allow Procore Item Edits setting.

Symptom: Disconnecting one user unexpectedly disconnects the company integration

Likely cause:

  • that user is the Integration Owner

Best next step:

Check whether the user is labeled as the integration owner before disconnecting. If the owner disconnects, the company-level integration may also disconnect and an admin will need to reconnect it.

Symptom: The company suddenly cannot use Procore integration features

Likely cause:

  • the company's active trial ended
  • the company no longer has the required Procore-enabled access state

Best next step:

Review the company's current plan or trial status in Taliho. The live app behavior allows Procore integration for active trial, Business, and Early Adopter states, but not for expired trial access.

Symptom: The install worked in one project but not another

Likely cause:

  • the App Configuration was scoped to only some projects
  • the working project is covered, but the failing project is not

Best next step:

Review the Procore configuration scope and decide whether to add the missing project or move to a global projects configuration.

When to restart the setup from the top

Restart the setup sequence if more than one symptom is happening at once. The clean recovery order is:

  1. Verify the Procore install and configuration.
  2. Verify the user launches the app from the correct Procore company or project context.
  3. Reconnect Procore in Taliho.
  4. Re-link the Taliho project to the correct Procore project.
  5. Re-test one real workflow such as a drawing or tool-based share.
Related guides

Keep moving through the workflow

Ready to try Taliho?

Get documents into the right hands, faster. Start your free trial today.