Integration Roadmap

VitruAI + Procore

The VitruAI + Procore integration authenticates against a Procore company workspace via the official REST API and reads/writes RFIs, submittals, drawings, and contracts for the RFI Agent and Scope Agent. It extends project memory across design and construction and is available now as a Labs engagement under MSA + Appendix, with a productised release on the roadmap.

  • Reads Procore RFIs, submittals, drawings, and contracts through the official REST API with project-scoped permissions.
  • Powers the RFI Agent drafting workflow and the Scope Agent contract-clause monitoring across active projects.
  • Available now as a Labs engagement under MSA + Appendix; productised VitruAI for Procore release sits on the roadmap.
Join the waitlist See capabilities ↓
Capabilities

Install, authentication, and what runs through the integration.

  • Procore developer-app authentication

    A Procore company admin installs the VitruAI developer app once at the company level, then authorises it for selected projects through Procore’s standard OAuth flow. Permissions follow the existing project member model, so the integration only reads RFIs, submittals, drawings, and contracts that the VitruAI service account can see. This keeps RFI drafting and tracking aligned with the firm’s current Procore permission structure.

  • REST API only — no inbound webhooks required

    VitruAI connects to Procore using the public REST API endpoints for RFIs, submittals, drawings, and documents; no inbound webhooks or firewall exceptions are required. The service polls each authorised project on a cadence the firm’s IT team approves, typically in single-digit minutes. Polling scopes by project ID so pilots can start with one or two projects before expanding across a full portfolio.

  • Drafts, never auto-submits

    Every output from the RFI Agent or Scope Agent lands in Procore as a draft or not-yet-submitted item, never as an auto-sent RFI, submittal, or change event. Project engineers and coordinators review the suggested language, attachments, and references before they hit Submit. This pattern fits firms that want speed on first drafts while keeping human sign-off on anything that reaches the GC, owner, or design team.

  • Available now as a Labs engagement

    VitruAI for Procore is available as a Labs engagement under MSA + Appendix, scoped against the firm’s current project-doc structure and naming conventions. The team maps how RFIs, submittals, drawings, and contracts are organised in the Procore instance, then tunes the Scope Agent and RFI Agent prompts to match that structure. The roadmap productised release will standardise these patterns into configuration screens instead of one-off Labs tuning.

  • ACC + Procore context for RFIs

    For firms running both Autodesk Construction Cloud and Procore, the integration pairs with the VitruAI + ACC connector so design context flows into construction RFIs. The RFI Agent can read sheets, models, and issues from ACC, draft an RFI that cites the relevant view or detail, and then write that draft into Procore for review. This keeps design-side decisions in ACC while construction-side tracking stays in Procore.

Common questions

Procore integration FAQ

  • Does it auto-submit RFIs without review?

    No. The VitruAI + Procore integration always writes RFI content as drafts or not-yet-submitted items inside Procore, never as auto-sent correspondence. A project engineer, coordinator, or PM must review and edit the draft before hitting Submit, so nothing reaches the design team or owner without human sign-off. This applies to RFI text, suggested attachments, and any cross-references created by the RFI Agent.

  • What permissions does the integration need?

    The integration follows Procore’s project member permission model and does not require full company-admin access for day-to-day use. A company admin installs the VitruAI app, then grants it access only to the projects where RFIs, submittals, and contracts should be read or drafted. Within those projects, the service account can be scoped so that the Scope Agent only reads contract documents while the RFI workflows focus on RFI and drawing tools.

  • When is the productised release?

    VitruAI for Procore is available now as a Labs engagement under MSA + Appendix, with a roadmap path to a productised integration. Labs projects define the exact RFI, submittal, and contract patterns the firm wants to standardise, and these patterns inform the packaged release. Each Labs deployment includes a short configuration guide so the eventual productised version can be rolled out across additional projects with minimal rework.

  • Does it integrate with ACC for the design side?

    Yes. For firms that use Autodesk Construction Cloud for design coordination and Procore for construction management, the integration can pair with the VitruAI + ACC connector. In that setup, the RFI Agent reads models, sheets, and issues from ACC, drafts RFIs with direct design references, and then writes those RFIs into Procore as drafts. This keeps design context in ACC while RFIs, submittals, and daily construction tracking stay in Procore.

More from VitruAI

Related

Adjacent agents, use cases, integrations, and regulations that pair with this one.

Agent VitruAI Labs

Structural Sizing Agent — preliminary member sizing from the architectural model

The Structural Sizing Agent reads the architectural Revit model, applies the firm’s preliminary-sizing rules, and emits concept-stage member sizes — beams, columns, slabs — for early…

IFCRevitGlobal
Agent VitruAI Labs

Document AI Agent — ai document parsing for aec drawings, PDFs, and DWGs

The Document AI Agent extracts structured data — door and window schedules, mechanical components and dimensions, RFI responses, submittal answers, and plan-archive search results — from…

AutoCADIFCRevitGlobalMENA
Agent Live

Comms Agent — AEC project comms agent for meetings to action items

The Comms Agent reads project-meeting transcripts from Zoom, Microsoft Teams, Google Meet, and Slack huddles, extracts decisions and action items with assigned owner and due date,…

Global
Agent Beta

Project Memory Agent — ai project memory for aec, claim-ready timelines on demand

The Project Memory Agent ingests project correspondence, meeting minutes, RFIs, design submissions, change orders, and contract documents into a structured project memory, then produces decision logs,…

BIM 360 / ACCProcoreGlobal
Agent Roadmap

RFI Agent — ai rfi drafting and tracking for aec

The RFI Agent drafts RFIs grounded in the project record—drawings, specifications, prior RFIs, and meeting minutes—and tracks each item’s schedule, scope, and cost implications inside Procore…

BIM 360 / ACCProcoreGlobal
Agent Beta

Contract Agent — ai contract clause monitoring for aec

The Contract Agent reads signed project contracts—owner-architect, design-build, owner-contractor, and subconsultant agreements—and monitors insurance, indemnity, and payment-terms clauses across the project lifecycle. It tracks which clauses…

Global
Agent Beta

Scope Agent — ai scope drift detection for aec projects

The Scope Agent reads the signed contract scope of services and watches RFIs, meeting minutes, design submissions, and email correspondence for asks that fall outside that…

ProcoreGlobal
Agent Roadmap

Clash Review Agent — the BIM coordination AI agent that prioritises the three clashes you need to look at today.

The Clash Review Agent ingests Navisworks and BIM 360 / ACC clash reports with thousands of issues and ranks each clash by cost-of-late-discovery, trade dependency, and…

BIM 360 / ACCNavisworksRevitGlobal
Next step

On the roadmap. Want first dibs?

Join the waitlist