Connectors

/

Procore

/

Create Procore observation from field note
Write

Turn a field note into a Procore observation with an owner

For site teams who want a field observation logged in Procore with the right type and assignee by asking their AI assistant.

Try PopdockAI free
Get a live demo
Create Procore observation from field note
Log an observation called Missing edge protection Level 4 on Riverside Tower, type Safety, assigned to Marcus Webb.
No open observation on Riverside Tower looks like this one, so this will be a new record. - Name: Missing edge protection Level 4 - Type: Safety (one match) - Assignee: Marcus Webb - Email: none will be sent Shall I create it?
Procore
Sample figures. Your results come from your own account.
procore-get-viewer-documents-accessible-tools
procore-get-project-observation-types
procore-get-observations-assignees
procore-get-observations-items
procore-create-observation-item

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

Field notes never reach Procore with an owner

Observations are jotted down on site and entered later, often with a guessed type and no assignee. A similar item may already be open, so the same issue is logged twice.

Without PopdockAI

  • Copy the note from a notebook or message
  • Pick a type from the project's list by guess
  • Hunt for the right assignee
  • Realise a similar observation was already open

With PopdockAI

  • The type is matched to the project's own list
  • The assignee is checked against people who can be assigned
  • Similar open observations are shown before you confirm
  • The record is read back and no email is sent

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 an observation named {observation-name} in {project-name} of type {type-name}, assigned to {assignee-name}.

**Step 1: Resolve the project**

Call `procore-get-viewer-documents-accessible-tools` with `project-name` equal to {project-name} to resolve the project id. If nothing matches, retry with `project-name.contains`. If more than one project matches, list them with their ids and stop and ask which one. If the user named a Procore company, pass it in the `company` parameter on every call.

**Step 2: Resolve type and assignee**

Call `procore-get-project-observation-types` with the `project-id` and match {type-name}. Call `procore-get-observations-assignees` with the `project-id` and match {assignee-name}. Show the matches; if either is ambiguous, ask.

**Step 3: Check for a duplicate**

Call `procore-get-observations-items` with the `project-id` and look for an open observation with a similar name.

**Step 4: Confirm and create**

Show the user the exact values you will send, the project, and anything you could not resolve, and ask for an explicit yes. Do not call the write tool until the user confirms in this conversation. Then call `procore-create-observation-item` with the `project-id`, `observation-name` and `observation-assignee-id`.

**Step 5: Verify**

Call `procore-get-observations-items` with the `project-id` and confirm the observation exists.

**Step 6: Report**

Report the observation number, name, type, assignee and status, or the exact error.

**Rules & Guidelines:**

* The only write tool you may call is `procore-create-observation-item`, and only once, after the user confirms. Do not call any other create, update, delete, send or bulk tool.
* Never invent an id, name or date. If a required value is missing or a lookup is ambiguous, ask.
* If the write fails, report the exact error and stop. Do not retry with changed values.
* Do not send the observation by email; never call `procore-send-observation-item-email` or `procore-send-unsent-observation-items`.
* If the create tool has no parameter for the type, tell the user the type cannot be set from here instead of guessing.

**Validation:**

* If the project cannot be resolved, stop and say so. Do not read records from an unresolved project.
* If the main read returns nothing, say the project has none and stop. Do not fill the gap with assumptions.

Who it's for

One answer, three teams that use it

Safety officers

Log hazards while they are fresh

Turn a hazard spotted on a walk into an observation with the right type and owner before you leave the area.

Create a Safety observation on Fabrikam Depot called Unguarded saw in the carpentry shop, assign it to Dana Whitfield.

Quality managers

Assign defects to someone

Get quality observations created with a named assignee so nothing sits unowned after the inspection round.

Log a Quality observation on Contoso Warehouse called Honeycombing on slab B2 and assign it to Sam Patel.

Site engineers

Avoid logging the same issue twice

See similar open observations before a new one is created, so you add to the record that exists rather than a copy.

Add an observation on Northwind Plaza called Cracked kerb at gate 2, type General, owner Priya Shah, unless one is already open.

How it works

What PopdockAI does when you ask

You describe the issue and who owns it in plain words. Your AI assistant matches the type and assignee and creates the observation once, only after you confirm.

Ask

You give the observation name, the project, the type and who it is for.

Your AI tool

Match

It resolves the type and assignee and looks for a similar open observation.

procore-get-viewer-documents-accessible-tools
procore-get-project-observation-types
procore-get-observations-assignees
procore-get-observations-items

Confirm

You see the exact values it will send and say yes.

No items found.

Create

It creates the observation once and reports its number, type, assignee 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-viewer-documents-accessible-tools

Returns Procore viewer documents accessible tools records from the Project Management area. Filter by project and by the record's own fields; reads only, nothing is changed.
get-data

procore-get-project-observation-types

Returns Procore project observation types records from the Project Management area. Filter by project and by the record's own fields; reads only, nothing is changed.
get-data

procore-get-observations-assignees

Returns the people and vendors a Procore observation can be assigned to on a project. Filter by project and vendor name.
get-data

procore-get-observations-items

Returns Procore observation items for a project, with status, assignee and due date.
run-action

procore-create-observation-item

Creates an observation item on a Procore project. Writes to live Procore data. Not individually tested, so try it on a sandbox project first.
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

Every field note becomes one owned observation

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