Fieldstub › Docs

Docs

Written while building Fieldstub and verified by probing a real Procore sandbox, not read off a documentation page. Several of the findings here are not published anywhere else.

Every page is also available as markdown: add .md to the URL, or send Accept: text/markdown.

8 pages · last updated 2026-09-18 · llms.txt · llms-full.txt

Setting it up

For the Procore admin doing the install.

Installing Fieldstub in Procore How to install Fieldstub in a Procore company, who can sign in, what it reads and writes, and how to remove it. Requires Project Financials. /docs/install.md
How the integration works The integration workflow: what Fieldstub reads from Procore, what it writes, and the human approval that sits between a field ticket and a Change Event. /docs/architecture.md

How Procore actually behaves

The API as it is, including the places it tells you something untrue.

Procore budget codes, and why your change event line item lands blank A Procore change event line item needs a WBS code id. The segment_items form returns 200 and is silently discarded, filing every line under a blank code. /docs/procore-budget-codes.md
Every Procore budget code error on a change event line item Wbs Code not found, budget_code is missing, must be an integer. Every response Procore gives a change event line item, including two that return 200 and file blank. /docs/procore-budget-code-errors.md
Creating a Procore change event over the API Auth, the create body Procore actually accepts, line items, amounts as strings, attachments, idempotency and rate limits. Probed against a live sandbox. /docs/procore-change-events-api.md
Procore's T&M Tickets tool: what it does, and what it needs Procore ships a T&M Tickets tool for labor, equipment, materials and signatures. It needs a Procore seat and the mobile app, and it has no public REST API. /docs/procore-tm-tickets.md

Build on Fieldstub

The REST API and the MCP server.

The Fieldstub API Create extra work tickets, read where each line will land, and file them into Procore as change events. REST, API keys, and an OpenAPI spec. /docs/api.md
The Fieldstub MCP server Connect an AI assistant to Fieldstub over MCP. Ten tools for capturing extra work and filing it into Procore, with approval deliberately fenced off. /docs/mcp.md

Docs

Setting it up

How Procore actually behaves

Build on Fieldstub

Put a code on one job and see what comes back.