Connectors

/

Procore

/

Create a Procore change event from scope
Write

Raise a Procore change event once, not three times

For project managers who want a change event created from a scope description by asking their AI assistant.

Try PopdockAI free
Get a live demo
Create a Procore change event from scope
Raise a change event on Riverside Tower titled Added blocking for wall mounted screens, scope: extra timber blocking in Level 6 meeting rooms.
No change event on Riverside Tower has a similar title, so this will be a new one. - Project: Riverside Tower - Title: Added blocking for wall mounted screens - Scope: extra timber blocking in Level 6 meeting rooms Shall I create the change event?
Procore
Sample figures. Your results come from your own account.
procore-get-budget
procore-get-change-events
procore-create-change-event

On this page

The problem

The problem

The prompt

Who it's for

How it works

Tools used

Connector

Procore

Procore
Run it on your own Procore data.

Connect Procore, pick your AI tool and paste the prompt.

Try PopdockAI free

The problem

The same change is raised under different titles

Change events are logged quickly when scope moves, often without checking what is already open. The same change then sits under two or three titles and the cost team has to sort them out.

Without PopdockAI

  • Open the project's change events
  • Scan titles for a similar one
  • Type a title and scope from the field notes
  • Merge or close the duplicates later

With PopdockAI

  • The project is resolved from the budget, exactly once
  • Similar change events are shown before you continue
  • A missing scope is asked for, not invented
  • One event is created and read back with its number

The prompt

Use this prompt

Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.

Prompt
**Objective:** Create a change event on `{project-name}` titled `{title}` with scope `{scope}`.

**Step 1: Resolve the project id**

Call `procore-get-budget` with `project-name` set to `{project-name}` and read `project-id`. If no project or more than one matches, list matches and stop.

**Step 2: Check for duplicates**

Call `procore-get-change-events` with `project-name` and `title.contains` set to `{title}`. If a similar event exists, show it and ask whether to continue before step 3.

**Step 3: Confirm**

Show the project, title, scope and the `project-id` that will be used. Ask for explicit confirmation. Do not call any write tool until the user says yes.

**Step 4: Create**

Call `procore-create-change-event` with `project-id`, `title` and `scope`. Then call `procore-get-change-events` again to confirm it exists and report its number and status.

**Rules & Guidelines:**

* The only write tool allowed is `procore-create-change-event`, called once, after confirmation.
* Do not call update, delete or sync tools.
* Never invent values for fields the user did not provide.

**Validation:**

* If `{scope}` is blank, ask for it before step 3, since scope is required.
* If creation fails, report the error and do not retry.

Who it's for

One answer, three teams that use it

Project managers

Capture scope changes quickly

Raise a change event while the conversation is fresh, with a duplicate check you would not otherwise do.

Create a change event on Fabrikam Depot titled Relocated hose bibs with scope: move three exterior hose bibs to the north wall.

Cost controllers

Keep the log free of repeats

Similar events are surfaced first, so the log you roll up to the budget does not count one change twice.

Add a change event Upgraded glazing spec on Contoso Warehouse, scope: switch to double low-e units, after checking for a similar one.

Site engineers

Raise events from the field

Turn a site observation into a change event with a clear scope, ready for the project manager to price.

Raise a change event on Northwind Plaza called Unforeseen rock at footing F4 with scope: additional excavation and breaking.

How it works

What PopdockAI does when you ask

You describe the change in plain words. Your AI assistant checks for similar events and creates one change event only after you have confirmed, with no retries.

Ask

You give the project, a title and the scope of the change.

Your AI tool

Check

It resolves the project and looks for a change event with a similar title.

procore-get-budget
procore-get-change-events

Confirm

You see the project, title, scope and project id and say yes.

No items found.

Create

It creates one change event and reads it back with its number and status.

Your AI tool

What PopdockAI provides

The tools behind the answer

Ready made tools for Procore and one secure connection to your AI tool. No code, no exports.

get-data

procore-get-budget

Returns Procore budget meta data for a project, including the project id other Procore financial tools need. Filter by project name.
get-data

procore-get-change-events

Returns change events records from Procore. Filter by the tool's input parameters. Part of the Procore Construction Financials area; the tool is built Inactive until switched on.
run-action

procore-create-change-event

Create change event in Procore, under change events (POST). Create Change Event. Writes to live Procore data. It is built Inactive and has not been run end to end through MCP, so test it in a sandbox before switching it on.
Read only.Nothing in Procore Changes

This report is built from Get data tools only. PopdockAI applies the row, field and parameter rules your admin sets, and every query is written to the audit trail.

How Popdock AI secures your data

The outcome

One change event per change

Try PopdockAI free
Get a live demo

Related use cases

More ways to put this data to work

One prompt template with infinite possibilities.

‍

Your AI assistant adapts its approach, tone, and capabilities to match each unique context while you maintain a single, manageable workflow.

Join forward-thinking companies that are transforming their operations with intelligent, secure AI automation.

Try PopdockAI Free
See Documentation