Procore

The Procore app connects Procore construction project management to Sprigr Team. Agents can read and update projects, RFIs, submittals, drawings, daily logs, change events and change orders, budgets, commitments, direct costs, prime contracts, observations, punch items, inspections, photos, meetings and directory records, and can reach every documented Procore REST operation when a curated action does not exist. Procore data is synced into the install so lookups are fast, and Procore webhooks turn record changes into events for workflows.

Note

Procore ships as a marketplace app with one connection per install. An admin authorises one Procore account for the workspace and every agent with the app acts as that account, so choose an account whose Procore permissions match what your agents should see and do.

Prerequisites

• A Procore account with access to the company and projects you want agents to work with. A Procore sandbox account also works for evaluation.
• Admin or Owner role in your Sprigr Team organisation to install the app.

Installing and connecting

1. Install the app

   Sign in to team.sprigr.com, open Apps in the sidebar, find Procore under Available, and install it. See Installing Apps.

2. Connect to Procore

   Open the app’s settings page from Apps > Installed. Under Connection, choose Connect to Procore (sandbox) or production, sign in to Procore and approve the requested access. The choice is remembered, and the page offers Connect (sandbox) and Connect (prod) links to reconnect later.

3. Select a company

   After connecting, the app lists the Procore companies the account can reach. Pick the one your agents should work in under Select company. If none are listed, run the connect flow again.

4. Check the connection

   Ask your agent “Which Procore projects are active?” The settings page also shows the last full and incremental sync times and recent activity.

Try asking your agent

“What RFIs are open on the Riverside project and who is holding each one?”

“Create a daily log for today on Riverside: 14 on site, concrete pour on level 3 completed, rain delay 45 minutes.”

“List punch items on the Harbour job that are overdue.”

Sync, webhooks and undo

• Synced records. A full sync of Procore resources runs nightly and an incremental sync every 15 minutes, so agents can resolve project, RFI and submittal references quickly without paging through Procore.
• Webhooks and events. Ask the agent to register Procore webhooks for the connected company (the register_webhooks action); the app then emits an event for each change: RFIs, submittals, observations, punch items, change events and change orders, daily logs, photos, projects, directory users, vendors, budget changes and more (73 event types, named procore.<resource>.<created|updated|deleted>). A workflow can subscribe to any of them.
• Confirmation before destructive changes. Actions that delete, void, revoke or deactivate records pause for your confirmation in the chat before they run.
• Undo. A reversible delete keeps a copy of the record, and the platform’s undo layer can recreate it.
• Disconnect without uninstalling. The connection can be revoked from the settings page or by an agent (procore_disconnect) while the app stays installed.

What agents can do

The app exposes a single procore tool that takes an action. It has three layers:

• Curated actions for everyday construction workflows: list and get projects, RFIs (create, update, close, reopen, reply), submittals (create, with workflow, respond), drawings and drawing sets, daily logs in every subtype, directory users and vendors, cost codes, change events and change orders, budget line items, modifications and changes (with approve, void and submit for review), commitments (subcontracts and purchase order contracts), subcontractor invoices, billing periods, direct costs, prime contracts, observations, punch items, inspections, photos, locations, meetings, incidents, action plans, and company-level lookups (offices, project stages and types, trades, roles, vendor insurances).
• Every documented Procore REST operation as a named action, generated from Procore’s own API specification, so anything Procore exposes is reachable by name.
• Discovery and passthrough: search_endpoints finds the right operation for a task, and procore_request calls any endpoint directly.

Ask the agent what it can do with Procore to see the catalogue in your workspace.

Common use cases

• RFI triage. “Which RFIs are due this week and unanswered?” returns the list with ball-in-court and due dates.
• Daily log from the field. A site manager dictates the day in chat and the agent creates the daily log entries.
• Submittal chasing. The agent lists submittals awaiting response and drafts reminders for the responsible parties.
• Budget questions. “Where are we against budget on Riverside?” reads budget line items, modifications and commitments.
• Punch list close-out. The agent lists open punch items by location and closes them as the team confirms.
• Event-driven updates. A workflow on procore.rfi.created posts new RFIs to the project’s Slack channel.

Troubleshooting

Not connected Nobody has completed the Connect step, or the connection was revoked. Reconnect from the app’s settings page, choosing sandbox or production to match the account.

No companies discovered Run the OAuth flow again from the settings page. The company list is fetched during the callback.

Agent cannot see a project or record The app acts as the single connected Procore account. That account must have permission for the project and tool in Procore.

Sandbox versus production Sandbox and production are separate Procore environments with separate logins and data. Reconnect with the other option if you connected the wrong one.

An action is waiting for confirmation Destructive actions pause until you confirm in the chat.

Next steps

• Integrations Overview: See all available integrations.
• Workflows: React to Procore RFI, submittal and punch item events.
• Creating Agents: Create a dedicated project-administration agent.