> **Building with AI coding agents?** Install the authstack plugin with one command. This equips your agent with accurate Scalekit implementation patterns.
>
> **Recommended** (the `-y` flags skip prompts, so the command runs without an interactive terminal):
> ```bash
> npx -y @scalekit-inc/cli setup -y
> ```
>
> Global:
> ```bash
> npm install -g @scalekit-inc/cli
> scalekit setup -y
> ```
>
> Supports Claude Code, Cursor, GitHub Copilot, Codex + skills for other Agent Skills-compatible agents in `~/.agents/skills`.
> Skills: integrate-agentkit, implement-saaskit, add-mcp-oauth, implement-sso, implement-scim.
> [Full setup guide](https://docs.scalekit.com/dev-kit/build-with-ai/)

---

# Connect AI agents to Procore

The Procore connector lets your AI agent act in each user's Procore account. Each user signs in to Procore once, and Scalekit stores and refreshes their tokens, so your agent never handles credentials. It comes with 27 tools.

**Authentication:** OAuth 2.0
**Categories:** Project Management, Collaboration
**Tools:** 27: 16 read, 10 write, 1 destructive
**Users sign in with:** OAuth
**OAuth app:** Your own Procore app
**Built by:** Scalekit connector
**Try it:** [Playground in the Scalekit dashboard](https://app.scalekit.com/ws/signup?sk_intent=playground&provider=PROCORE)

## Setup

1. ### Install the SDK

   **Node.js**

   ```bash
   npm install @scalekit-sdk/node dotenv
   ```

   **Python**

   ```bash
   pip install scalekit-sdk-python python-dotenv
   ```

2. ### Set your credentials

   Add your Scalekit credentials to your `.env` file. Find values in **[app.scalekit.com](https://app.scalekit.com)** > **Developers** > **API Credentials**.

   ```sh title=".env"
   SCALEKIT_ENVIRONMENT_URL=<your-environment-url>
   SCALEKIT_CLIENT_ID=<your-client-id>
   SCALEKIT_CLIENT_SECRET=<your-client-secret>
   ```

3. ### Create the Procore connection

   In **AgentKit > Connections**, create a Procore connection and copy its redirect URI. The name you give it is the `connection_name` your code passes. See [Configure connections](/agentkit/connections/).

4. ### Register an OAuth app

   Procore connections use your own OAuth app. Register one with Procore and add the redirect URI you copied.

   Then enter the app's Client ID and Client Secret on the Procore connection.

5. ### Authorize a user and make your first call

   **Node.js** (`quickstart.mts`)

   ```typescript
   import { ScalekitClient } from '@scalekit-sdk/node'
   import 'dotenv/config'
   import { createInterface } from 'node:readline/promises'

   const scalekit = new ScalekitClient(
     process.env.SCALEKIT_ENVIRONMENT_URL,
     process.env.SCALEKIT_CLIENT_ID,
     process.env.SCALEKIT_CLIENT_SECRET,
   )
   const actions = scalekit.actions

   const connector = 'procore'
   const identifier = 'user_123'

   // Generate an authorization link for the user
   const { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })
   console.log('Authorize Procore:', link)
   const rl = createInterface({ input: process.stdin, output: process.stdout })
   await rl.question('Press Enter after authorizing...')
   rl.close()

   // Make your first call
   const result = await actions.executeTool({
     connector,
     identifier,
     toolName: 'procore_companies_list',
     toolInput: {},
   })
   console.log(result)
   ```

   ```bash
   npx tsx quickstart.mts
   ```

   **Python** (`quickstart.py`)

   ```python
   import os
   from scalekit import ScalekitClient
   from dotenv import load_dotenv
   load_dotenv()

   scalekit_client = ScalekitClient(
       env_url=os.getenv("SCALEKIT_ENVIRONMENT_URL"),
       client_id=os.getenv("SCALEKIT_CLIENT_ID"),
       client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"),
   )
   actions = scalekit_client.actions

   connection_name = "procore"
   identifier = "user_123"

   # Generate an authorization link for the user
   link_response = actions.get_authorization_link(
       connection_name=connection_name,
       identifier=identifier,
   )
   print("Authorize Procore:", link_response.link)
   input("Press Enter after authorizing...")

   # Make your first call
   result = actions.execute_tool(
       tool_input={},
       tool_name="procore_companies_list",
       connection_name=connection_name,
       identifier=identifier,
   )
   print(result)
   ```

   ```bash
   python quickstart.py
   ```

   Each user signs in once. See [Authorize a user](/agentkit/tools/authorize/) for the full flow and statuses.

## Tools

Pass the exact name to `execute_tool`, with an input like each tool's example. To ask for a tool that's missing, use the [request form](https://scalekitsupport.portal.usepylon.com/forms/request-a-connector-tool).

**Node.js**

```typescript
const result = await actions.executeTool({
  toolName: 'procore_companies_list',
  toolInput: {},
  connector: 'procore',
  identifier: 'user_123',
})
```

**Python**

```python
result = actions.execute_tool(
    tool_name="procore_companies_list",
    tool_input={},
    connection_name="procore",
    identifier="user_123",
)
```

`result.data` is the app's response as JSON, and `result.execution_id` (`executionId` in Node.js) is the ID of the call.

### `procore_companies_list`

List Companies · Read-only

List the Procore companies the connected user can access.
Returns an array of companies with id, name and is_active.
Use procore_companies_list first: every other tool needs a company_id.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `page` (`integer`, optional): Page number, starting at 1. Example: 2
- `per_page` (`integer`, optional): Items per page (default 100). Example: 50

Example input: `{}`

### `procore_me_get`

Get Current User · Read-only

Get the Procore user the connection belongs to.
Returns id, login (email) and name.
Use procore_me_get to confirm who is connected. Use procore_companies_list for the companies they can reach.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `procore_notes_logs_list`

List Daily Log Notes · Read-only

List the notes entries of a project's daily log.
Returns an array of notes logs with id, date, comment, is_issue_day, location and created_by.
Use procore_notes_logs_list to read daily log notes. Use procore_notes_log_create to add one.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `company_id` (`integer`, required): Procore company ID, sent as the Procore-Company-Id header (from procore_companies_list). Example: 8089
- `project_id` (`integer`, required): Project ID (from procore_projects_list). Example: 2783
- `created_by_id` (`integer`, optional): Only notes by this user. Example: 4521
- `page` (`integer`, optional): Page number, starting at 1. Example: 2
- `per_page` (`integer`, optional): Items per page (default 100). Example: 50
- `status` (`string`, optional): pending, approved or all. Example: all. One of: `pending`, `approved`, `all`.

Example input: `{"company_id":8089,"project_id":2783}`

### `procore_observation_get`

Get Observation · Read-only

Get one observation item.
Returns the observation with number, name, description, status, priority, type, assignee, location, trade and dates.
Use procore_observation_get when you know the observation ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `company_id` (`integer`, required): Procore company ID, sent as the Procore-Company-Id header (from procore_companies_list). Example: 8089
- `observation_id` (`integer`, required): ID of the observation. Example: 12345
- `project_id` (`integer`, required): Project ID (from procore_projects_list). Example: 2783

Example input: `{"company_id":8089,"observation_id":12345,"project_id":2783}`

### `procore_observation_types_list`

List Observation Types · Read-only

List the observation types available in a project (such as Safety, Quality, Commissioning).
Returns an array of types with id, name and category.
Use procore_observation_types_list to get the type_id for procore_observation_create.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `company_id` (`integer`, required): Procore company ID, sent as the Procore-Company-Id header (from procore_companies_list). Example: 8089
- `project_id` (`integer`, required): Project ID (from procore_projects_list). Example: 2783
- `page` (`integer`, optional): Page number, starting at 1. Example: 2
- `per_page` (`integer`, optional): Items per page (default 100). Example: 50

Example input: `{"company_id":8089,"project_id":2783}`

### `procore_observations_list`

List Observations · Read-only

List observation items (safety, quality and other field observations) on a project, filtered by type, status, assignee or a search.
Returns an array of observations with id, number, name, status, priority, type, due_date, assignee and location.
Use procore_observations_list to review field issues. Use procore_observation_get for one observation.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `company_id` (`integer`, required): Procore company ID, sent as the Procore-Company-Id header (from procore_companies_list). Example: 8089
- `project_id` (`integer`, required): Project ID (from procore_projects_list). Example: 2783
- `assignee_id` (`integer`, optional): Only observations assigned to this user. Example: 4521
- `page` (`integer`, optional): Page number, starting at 1. Example: 2
- `per_page` (`integer`, optional): Items per page (default 100). Example: 50
- `search` (`string`, optional): Search text. Example: guardrail
- `status` (`integer`, optional): Lifecycle status code: 0 Initiated, 1 Ready for Review, 2 Not Accepted, 3 Closed. Example: 0
- `type_id` (`integer`, optional): Observation type ID (from procore_observation_types_list). Example: 12
- `updated_at` (`string`, optional): Updated within an ISO 8601 range, written start...end. Example: 2026-11-01...2026-11-15

Example input: `{"company_id":8089,"project_id":2783}`

### `procore_project_get`

Get Project · Read-only

Get one project.
Returns the project with id, name, project_number, address, dates, stage, type, office, owner and status fields.
Use procore_project_get when you know the project ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `company_id` (`integer`, required): Procore company ID, sent as the Procore-Company-Id header (from procore_companies_list). Example: 8089
- `project_id` (`integer`, required): Project ID (from procore_projects_list). Example: 2783

Example input: `{"company_id":8089,"project_id":2783}`

### `procore_project_users_list`

List Project Users · Read-only

List users in a project's directory, optionally searched by name or email.
Returns an array of users with id, name, email_address, job_title, vendor and permission template.
Use procore_project_users_list to find user IDs for RFI managers, assignees and distribution lists.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `company_id` (`integer`, required): Procore company ID, sent as the Procore-Company-Id header (from procore_companies_list). Example: 8089
- `project_id` (`integer`, required): Project ID (from procore_projects_list). Example: 2783
- `employee` (`boolean`, optional): Only employees of your company (true) or only others (false). Example: true
- `page` (`integer`, optional): Page number, starting at 1. Example: 2
- `per_page` (`integer`, optional): Items per page (default 100). Example: 50
- `search` (`string`, optional): Match first name, last name, email or company. Example: smith

Example input: `{"company_id":8089,"project_id":2783}`

### `procore_projects_list`

List Projects · Read-only

List projects in a company, filtered by status, name, project number or update time.
Returns an array of projects with id, name, display_name, project_number, address, active, stage and dates.
Use procore_projects_list to find a project_id. Use procore_project_get for one project.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `company_id` (`integer`, required): Procore company ID, sent as the Procore-Company-Id header (from procore_companies_list). Example: 8089
- `name` (`string`, optional): Projects whose name matches this text. Example: Tower
- `page` (`integer`, optional): Page number, starting at 1. Example: 2
- `per_page` (`integer`, optional): Items per page (default 100). Example: 50
- `project_number` (`string`, optional): Exact project number. Example: 2026-014
- `sort` (`string`, optional): name, display_name, project_number or status. Example: name. One of: `name`, `display_name`, `project_number`, `status`.
- `status` (`string`, optional): Active (default in the UI), Inactive or All. Example: Active. One of: `All`, `Active`, `Inactive`.
- `updated_at` (`string`, optional): Updated within an ISO 8601 range, written start...end. Example: 2026-11-01...2026-11-15

Example input: `{"company_id":8089}`

### `procore_punch_item_get`

Get Punch Item · Read-only

Get one punch item.
Returns the punch item with name, description, status, priority, due date, location, trade, assignments and attachments.
Use procore_punch_item_get when you know the punch item ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `company_id` (`integer`, required): Procore company ID, sent as the Procore-Company-Id header (from procore_companies_list). Example: 8089
- `project_id` (`integer`, required): Project ID (from procore_projects_list). Example: 2783
- `punch_item_id` (`integer`, required): ID of the punch item. Example: 12345

Example input: `{"company_id":8089,"project_id":2783,"punch_item_id":12345}`

### `procore_punch_items_list`

List Punch Items · Read-only

List punch items on a project, filtered by status, priority, vendor, assignee or a search.
Returns an array of punch items with id, position, name, status, priority, due_date, location, assignments and ball_in_court.
Use procore_punch_items_list to review the punch list. Use procore_punch_item_get for one item.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `company_id` (`integer`, required): Procore company ID, sent as the Procore-Company-Id header (from procore_companies_list). Example: 8089
- `project_id` (`integer`, required): Project ID (from procore_projects_list). Example: 2783
- `page` (`integer`, optional): Page number, starting at 1. Example: 2
- `per_page` (`integer`, optional): Items per page (default 100). Example: 50
- `priority` (`string`, optional): low, medium or high. Example: high. One of: `low`, `medium`, `high`.
- `query` (`string`, optional): Search text. Example: drywall
- `status` (`string`, optional): open, closed or pending. Example: open. One of: `open`, `closed`, `pending`.
- `updated_at` (`string`, optional): Updated within an ISO 8601 range, written start...end. Example: 2026-11-01...2026-11-15
- `vendor_id` (`integer`, optional): Only items assigned to this vendor. Example: 771

Example input: `{"company_id":8089,"project_id":2783}`

### `procore_rfi_get`

Get RFI · Read-only

Get one RFI with its questions and responses.
Returns the RFI with number, subject, status, questions[] (body, answers[]), assignees, rfi_manager, due_date and cost and schedule impact.
Use procore_rfi_get to read an RFI's full thread.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `company_id` (`integer`, required): Procore company ID, sent as the Procore-Company-Id header (from procore_companies_list). Example: 8089
- `project_id` (`integer`, required): Project ID (from procore_projects_list). Example: 2783
- `rfi_id` (`integer`, required): ID of the RFI. Example: 12345

Example input: `{"company_id":8089,"project_id":2783,"rfi_id":12345}`

### `procore_rfis_list`

List RFIs · Read-only

List RFIs on a project, filtered by status, ball in court, priority, overdue or a search on subject and number.
Returns an array of RFIs with id, number, subject, status, due_date, ball_in_court, rfi_manager and assignees.
Use procore_rfis_list to track open questions. Use procore_rfi_get for the question and responses.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `company_id` (`integer`, required): Procore company ID, sent as the Procore-Company-Id header (from procore_companies_list). Example: 8089
- `project_id` (`integer`, required): Project ID (from procore_projects_list). Example: 2783
- `ball_in_court_id` (`integer`, optional): Only RFIs where this user is ball in court. Example: 4521
- `overdue` (`boolean`, optional): Only overdue RFIs. Example: true
- `page` (`integer`, optional): Page number, starting at 1. Example: 2
- `per_page` (`integer`, optional): Items per page (default 100). Example: 50
- `search` (`string`, optional): Search RFI subject or number. Example: kitchen
- `status` (`string`, optional): open, closed, draft, closed_with_revision or closed_draft. Example: open. One of: `open`, `closed`, `draft`, `closed_with_revision`, `closed_draft`.
- `updated_at` (`string`, optional): Updated within an ISO 8601 range, written start...end. Example: 2026-11-01...2026-11-15

Example input: `{"company_id":8089,"project_id":2783}`

### `procore_submittal_get`

Get Submittal · Read-only

Get one submittal.
Returns the submittal with number, revision, title, status, type, dates, approvers, ball_in_court and attachments.
Use procore_submittal_get when you know the submittal ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `company_id` (`integer`, required): Procore company ID, sent as the Procore-Company-Id header (from procore_companies_list). Example: 8089
- `project_id` (`integer`, required): Project ID (from procore_projects_list). Example: 2783
- `submittal_id` (`integer`, required): ID of the submittal. Example: 12345

Example input: `{"company_id":8089,"project_id":2783,"submittal_id":12345}`

### `procore_submittals_list`

List Submittals · Read-only

List submittals on a project, filtered by status, ball in court, spec section or a search, sorted and paged.
Returns an array of submittals with id, number, title, status, type, specification_section, due_date and ball_in_court.
Use procore_submittals_list to track submittals. Use procore_submittal_get for one submittal.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `company_id` (`integer`, required): Procore company ID, sent as the Procore-Company-Id header (from procore_companies_list). Example: 8089
- `project_id` (`integer`, required): Project ID (from procore_projects_list). Example: 2783
- `ball_in_court_id` (`integer`, optional): Only submittals where this user is ball in court. Example: 4521
- `current_revision` (`boolean`, optional): Only current revisions. Example: true
- `page` (`integer`, optional): Page number, starting at 1. Example: 2
- `per_page` (`integer`, optional): Items per page (default 100). Example: 50
- `query` (`string`, optional): Search text. Example: storefront
- `sort` (`string`, optional): number, title, type, status, due_date or another documented sort field. Example: number
- `status_id` (`integer`, optional): Submittal status ID. Example: 1
- `updated_at` (`string`, optional): Updated within an ISO 8601 range, written start...end. Example: 2026-11-01...2026-11-15

Example input: `{"company_id":8089,"project_id":2783}`

### `procore_tasks_list`

List Tasks · Read-only

List tasks (the project task tool) on a project, optionally searched.
Returns an array of tasks with id, number, title, status, due_date, assignees and category.
Use procore_tasks_list to review project tasks.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `company_id` (`integer`, required): Procore company ID, sent as the Procore-Company-Id header (from procore_companies_list). Example: 8089
- `project_id` (`integer`, required): Project ID (from procore_projects_list). Example: 2783
- `page` (`integer`, optional): Page number, starting at 1. Example: 2
- `per_page` (`integer`, optional): Items per page (default 100). Example: 50
- `query` (`string`, optional): Search text. Example: inspection
- `updated_at` (`string`, optional): Updated within an ISO 8601 range, written start...end. Example: 2026-11-01...2026-11-15

Example input: `{"company_id":8089,"project_id":2783}`

### `procore_notes_log_create`

Create Daily Log Note · Write

Add a notes entry to a project's daily log.
Returns the created notes log with id.
Use procore_notes_log_create to record site notes for a day.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `comment` (`string`, required): Note text. Example: Concrete pour delayed by rain
- `company_id` (`integer`, required): Procore company ID, sent as the Procore-Company-Id header (from procore_companies_list). Example: 8089
- `project_id` (`integer`, required): Project ID (from procore_projects_list). Example: 2783
- `date` (`string`, optional): Log date (YYYY-MM-DD); defaults to today. Example: 2026-11-15
- `is_issue_day` (`boolean`, optional): Flag the note as an issue affecting the project. Example: true
- `location_id` (`integer`, optional): Location ID. Example: 9821

Example input: `{"comment":"<comment>","company_id":8089,"project_id":2783}`

### `procore_observation_create`

Create Observation · Write

Create an observation item on a project.
Returns the created observation with id and number.
Use procore_observation_create to log a safety or quality issue. Get type_id from procore_observation_types_list.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `company_id` (`integer`, required): Procore company ID, sent as the Procore-Company-Id header (from procore_companies_list). Example: 8089
- `name` (`string`, required): Short name. Example: Missing guardrail L3
- `project_id` (`integer`, required): Project ID (from procore_projects_list). Example: 2783
- `type_id` (`integer`, required): Observation type ID. Example: 12
- `assignee_id` (`integer`, optional): User ID of the assignee (single-select assignee). Example: 4521
- `description` (`string`, optional): Description. Example: Missing guardrail on level 3 east stair
- `due_date` (`string`, optional): Due date (YYYY-MM-DD). Example: 2026-11-20
- `location_id` (`integer`, optional): Location ID. Example: 9821
- `priority` (`string`, optional): Low, Medium, High or Urgent. Example: High. One of: `Low`, `Medium`, `High`, `Urgent`.
- `trade_id` (`integer`, optional): Trade ID. Example: 55

Example input: `{"company_id":8089,"name":"<name>","project_id":2783,"type_id":12}`

### `procore_observation_update`

Update Observation · Write

Update an observation's name, type, description, priority, due date, assignee or location.
Returns the updated observation.
Use procore_observation_update to change an observation; Procore requires name and type_id on every update.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `company_id` (`integer`, required): Procore company ID, sent as the Procore-Company-Id header (from procore_companies_list). Example: 8089
- `name` (`string`, required): Name (send the current one if unchanged). Example: Missing guardrail L3
- `observation_id` (`integer`, required): ID of the observation. Example: 12345
- `project_id` (`integer`, required): Project ID (from procore_projects_list). Example: 2783
- `type_id` (`integer`, required): Type ID (send the current one if unchanged). Example: 12
- `assignee_id` (`integer`, optional): User ID of the assignee (single-select assignee). Example: 4521
- `description` (`string`, optional): Description. Example: Missing guardrail on level 3 east stair
- `due_date` (`string`, optional): Due date (YYYY-MM-DD). Example: 2026-11-20
- `location_id` (`integer`, optional): Location ID. Example: 9821
- `priority` (`string`, optional): Low, Medium, High or Urgent. Example: High. One of: `Low`, `Medium`, `High`, `Urgent`.
- `trade_id` (`integer`, optional): Trade ID. Example: 55

Example input: `{"company_id":8089,"name":"<name>","observation_id":12345,"project_id":2783,"type_id":12}`

### `procore_punch_item_comment_create`

Comment on Punch Item · Write

Add a comment to a punch item's activity.
Returns the created comment.
Use procore_punch_item_comment_create to post an update on a punch item.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `body` (`string`, required): Comment text. Example: Painter scheduled for Thursday
- `company_id` (`integer`, required): Procore company ID, sent as the Procore-Company-Id header (from procore_companies_list). Example: 8089
- `project_id` (`integer`, required): Project ID (from procore_projects_list). Example: 2783
- `punch_item_id` (`integer`, required): ID of the punch item. Example: 12345

Example input: `{"body":"<body>","company_id":8089,"project_id":2783,"punch_item_id":12345}`

### `procore_punch_item_create`

Create Punch Item · Write

Create a punch item on a project, optionally assigned to users.
Returns the created punch item with id and position.
Use procore_punch_item_create to log a deficiency. Use procore_punch_item_update to change or close it.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `company_id` (`integer`, required): Procore company ID, sent as the Procore-Company-Id header (from procore_companies_list). Example: 8089
- `name` (`string`, required): Short name. Example: Drywall damage at C4
- `project_id` (`integer`, required): Project ID (from procore_projects_list). Example: 2783
- `description` (`string`, optional): Description. Example: Patch and repaint drywall at column C4
- `due_date` (`string`, optional): Due date (YYYY-MM-DD). Example: 2026-11-30
- `location_id` (`integer`, optional): Location ID. Example: 9821
- `login_information_ids` (`array`, optional): User IDs to assign. Example: [4521]
- `priority` (`string`, optional): low, medium or high. Example: medium. One of: `low`, `medium`, `high`.
- `private` (`boolean`, optional): Mark private. Example: false
- `trade_id` (`integer`, optional): Trade ID. Example: 55

Example input: `{"company_id":8089,"name":"<name>","project_id":2783}`

### `procore_punch_item_update`

Update Punch Item · Write

Update a punch item: rename it, change description, due date, priority, assignees or location, or close it.
Returns the updated punch item.
Use procore_punch_item_update with status closed to close an item.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `company_id` (`integer`, required): Procore company ID, sent as the Procore-Company-Id header (from procore_companies_list). Example: 8089
- `name` (`string`, required): Name (Procore requires it on update; send the current name if unchanged). Example: Drywall damage at C4
- `project_id` (`integer`, required): Project ID (from procore_projects_list). Example: 2783
- `punch_item_id` (`integer`, required): ID of the punch item. Example: 12345
- `description` (`string`, optional): Description. Example: Patch and repaint drywall at column C4
- `due_date` (`string`, optional): Due date (YYYY-MM-DD). Example: 2026-11-30
- `location_id` (`integer`, optional): Location ID. Example: 9821
- `login_information_ids` (`array`, optional): User IDs to assign. Example: [4521]
- `priority` (`string`, optional): low, medium or high. Example: medium. One of: `low`, `medium`, `high`.
- `private` (`boolean`, optional): Mark private. Example: false
- `status` (`string`, optional): open or closed. Example: closed. One of: `open`, `closed`.
- `trade_id` (`integer`, optional): Trade ID. Example: 55

Example input: `{"company_id":8089,"name":"<name>","project_id":2783,"punch_item_id":12345}`

### `procore_rfi_create`

Create RFI · Write

Create an RFI on a project with a subject, question and RFI manager; non-draft RFIs notify the assignees.
Returns the created RFI with id and number.
Use procore_rfi_create to raise a question. Use procore_project_users_list to find user IDs.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `company_id` (`integer`, required): Procore company ID, sent as the Procore-Company-Id header (from procore_companies_list). Example: 8089
- `project_id` (`integer`, required): Project ID (from procore_projects_list). Example: 2783
- `question` (`string`, required): The question text. Example: What color should the kitchen wall be?
- `rfi_manager_id` (`integer`, required): User ID of the RFI manager. Example: 4520
- `subject` (`string`, required): RFI subject. Example: Kitchen wall paint color
- `assignee_ids` (`array`, optional): User IDs of the assignees. Example: [4521, 4522]
- `distribution_ids` (`array`, optional): User IDs on the distribution list. Example: [4523]
- `draft` (`boolean`, optional): Save as a draft without notifying. Example: true
- `due_date` (`string`, optional): Due date (YYYY-MM-DD). Example: 2026-11-30
- `location_id` (`integer`, optional): Location ID. Example: 9821
- `private` (`boolean`, optional): Mark the RFI private. Example: false
- `reference` (`string`, optional): Reference text. Example: Detail 5/A-301

Example input: `{"company_id":8089,"project_id":2783,"question":"<question>","rfi_manager_id":4520,"subject":"<subject>"}`

### `procore_rfi_update`

Update RFI · Write

Update an RFI's subject, assignees, due date, distribution or other fields, or close or reopen it with accepted.
Returns the updated RFI.
Use procore_rfi_update to change an RFI. Set accepted true to close it.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `company_id` (`integer`, required): Procore company ID, sent as the Procore-Company-Id header (from procore_companies_list). Example: 8089
- `project_id` (`integer`, required): Project ID (from procore_projects_list). Example: 2783
- `rfi_id` (`integer`, required): ID of the RFI. Example: 12345
- `accepted` (`boolean`, optional): true closes the RFI, false reopens it. Example: true
- `assignee_ids` (`array`, optional): User IDs of the assignees. Example: [4521, 4522]
- `distribution_ids` (`array`, optional): User IDs on the distribution list. Example: [4523]
- `draft` (`boolean`, optional): Save as a draft without notifying. Example: true
- `due_date` (`string`, optional): Due date (YYYY-MM-DD). Example: 2026-11-30
- `location_id` (`integer`, optional): Location ID. Example: 9821
- `private` (`boolean`, optional): Mark the RFI private. Example: false
- `reference` (`string`, optional): Reference text. Example: Detail 5/A-301
- `rfi_manager_id` (`integer`, optional): New RFI manager user ID. Example: 4520
- `subject` (`string`, optional): New subject. Example: Kitchen wall paint color (revised)

Example input: `{"company_id":8089,"project_id":2783,"rfi_id":12345}`

### `procore_submittal_create`

Create Submittal · Write

Create a submittal on a project.
Returns the created submittal with id.
Use procore_submittal_create to log a new submittal. Use procore_submittal_update to change it.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `company_id` (`integer`, required): Procore company ID, sent as the Procore-Company-Id header (from procore_companies_list). Example: 8089
- `number` (`string`, required): Submittal number. Example: 08 41 13-1
- `project_id` (`integer`, required): Project ID (from procore_projects_list). Example: 2783
- `description` (`string`, optional): Description. Example: Aluminum storefront system
- `due_date` (`string`, optional): Due date (YYYY-MM-DD). Example: 2026-12-05
- `private` (`boolean`, optional): Mark private. Example: false
- `received_from_id` (`integer`, optional): User ID the submittal was received from. Example: 4521
- `responsible_contractor_id` (`integer`, optional): Vendor ID of the responsible contractor. Example: 771
- `specification_section_id` (`integer`, optional): Specification section ID. Example: 3312
- `submittal_manager_id` (`integer`, optional): User ID of the submittal manager (admins only). Example: 4520
- `title` (`string`, optional): Title. Example: Storefront shop drawings
- `type` (`string`, optional): Submittal type name, as configured on the project. Example: Shop Drawing

Example input: `{"company_id":8089,"number":"<number>","project_id":2783}`

### `procore_submittal_update`

Update Submittal · Write

Update a submittal's title, type, spec section, contractor, manager, due date or other fields.
Returns the updated submittal.
Use procore_submittal_update to change a submittal.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `company_id` (`integer`, required): Procore company ID, sent as the Procore-Company-Id header (from procore_companies_list). Example: 8089
- `number` (`string`, required): Submittal number (Procore requires it on update; send the current number if unchanged). Example: 08 41 13-1
- `project_id` (`integer`, required): Project ID (from procore_projects_list). Example: 2783
- `submittal_id` (`integer`, required): ID of the submittal. Example: 12345
- `description` (`string`, optional): Description. Example: Aluminum storefront system
- `due_date` (`string`, optional): Due date (YYYY-MM-DD). Example: 2026-12-05
- `private` (`boolean`, optional): Mark private. Example: false
- `received_from_id` (`integer`, optional): User ID the submittal was received from. Example: 4521
- `responsible_contractor_id` (`integer`, optional): Vendor ID of the responsible contractor. Example: 771
- `specification_section_id` (`integer`, optional): Specification section ID. Example: 3312
- `status_id` (`integer`, optional): New status ID (admins only). Example: 2
- `submittal_manager_id` (`integer`, optional): User ID of the submittal manager (admins only). Example: 4520
- `title` (`string`, optional): Title. Example: Storefront shop drawings
- `type` (`string`, optional): Submittal type name, as configured on the project. Example: Shop Drawing

Example input: `{"company_id":8089,"number":"<number>","project_id":2783,"submittal_id":12345}`

### `procore_punch_item_delete`

Delete Punch Item · Destructive

Delete a punch item (it moves to the project's recycle bin).
Returns an empty response on success.
Use procore_punch_item_delete to remove an item logged by mistake; close it with procore_punch_item_update otherwise.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `company_id` (`integer`, required): Procore company ID, sent as the Procore-Company-Id header (from procore_companies_list). Example: 8089
- `project_id` (`integer`, required): Project ID (from procore_projects_list). Example: 2783
- `punch_item_id` (`integer`, required): ID of the punch item. Example: 12345

Example input: `{"company_id":8089,"project_id":2783,"punch_item_id":12345}`

## Related

Other Project Management connectors ([all 67](/agentkit/connectors/?category=project-management)):

- [Notion](/agentkit/connectors/notion/): Scalekit connector, OAuth, 51 tools
- [Linear](/agentkit/connectors/linear/): Scalekit connector, OAuth, 64 tools
- [Airtable](/agentkit/connectors/airtable/): Scalekit connector, OAuth, 26 tools


---

## More Scalekit documentation

| Resource | What it contains | When to use it |
|----------|-----------------|----------------|
| [/llms.txt](/llms.txt) | Structured index with routing hints per product area | Start here — find which documentation set covers your topic before loading full content |
| [/llms-full.txt](/llms-full.txt) | Complete documentation for all Scalekit products in one file | Use when you need exhaustive context across multiple products or when the topic spans several areas |
| [sitemap-0.xml](https://docs.scalekit.com/sitemap-0.xml) | Full URL list of every documentation page | Use to discover specific page URLs you can fetch for targeted, page-level answers |
