---
canonical_url: "https://docs.composio.dev/toolkits/procore_field_operations"
markdown_url: "https://docs.composio.dev/toolkits/procore_field_operations.md"
product: "platform"
version: null
last_updated: null
---

# Procore Field Operations

Manage Procore field productivity, daily logs, schedules, and scheduling workflows.

- **Category:** project management
- **Auth:** OAUTH2
- **Composio-managed OAuth available?** No
- **Tools:** 399
- **Triggers:** 0
- **Slug:** `PROCORE_FIELD_OPERATIONS`
- **Version:** 00000000_00

## Tools

### Bulk Create Actual Production Quantities

**Slug:** `PROCORE_FIELD_OPERATIONS_BULK_CREATE_ACTUAL_PRODUCTION_C26A001B`

Beta. Bulk Create Actual Production Quantities. This Procore endpoint is beta and its contract may change. Source: https://developers.procore.com/reference/rest/actual-production-quantities?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Bulk Create

**Slug:** `PROCORE_FIELD_OPERATIONS_BULK_CREATE_EQUIPMENT_TIMECARD_A93B6418`

Beta. Bulk Create. This Procore endpoint is beta and its contract may change. Source: https://developers.procore.com/reference/rest/equipment-timecard-entries?version=2.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique identifier for the company. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Bulk Create Materials

**Slug:** `PROCORE_FIELD_OPERATIONS_BULK_CREATE_MATERIALS`

Bulk Create Materials. Source: https://developers.procore.com/reference/rest/material?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Bulk Create Time and material equipment logs

**Slug:** `PROCORE_FIELD_OPERATIONS_BULK_CREATE_TIME_AND_MATERIAL_BDC74841`

Bulk Create Time and material equipment logs. Source: https://developers.procore.com/reference/rest/time-and-material-equipment-log?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Bulk Create Time and material timecards

**Slug:** `PROCORE_FIELD_OPERATIONS_BULK_CREATE_TIME_AND_MATERIAL_TIMECARDS`

Bulk Create Time and material timecards. Source: https://developers.procore.com/reference/rest/time-and-material-timecard?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Bulk Create Timecard Entries

**Slug:** `PROCORE_FIELD_OPERATIONS_BULK_CREATE_TIMECARD_ENTRIES`

Bulk Create Timecard Entries. Source: https://developers.procore.com/reference/rest/timesheets?version=1.1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Bulk Create

**Slug:** `PROCORE_FIELD_OPERATIONS_BULK_CREATE_TIMESHEETS_V1_1`

Beta. Bulk Create. This Procore endpoint is beta and its contract may change. Source: https://developers.procore.com/reference/rest/timesheets?version=1.1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Bulk Delete Managed Equipment

**Slug:** `PROCORE_FIELD_OPERATIONS_BULK_DELETE_MANAGED_EQUIPMENT`

Deprecated. Bulk Delete Managed Equipment. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/managed-equipment---company-level?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Bulk Delete Managed Equipment Attachment

**Slug:** `PROCORE_FIELD_OPERATIONS_BULK_DELETE_MANAGED_EQUIPMENT_7F174BC7`

Deprecated. Bulk Delete Managed Equipment Attachment. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/managed-equipment-attachment?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Identifier of the managed equipment that owns the attachments. |
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Bulk Delete Managed Equipment Maintenance Log Attachments

**Slug:** `PROCORE_FIELD_OPERATIONS_BULK_DELETE_MANAGED_EQUIPMENT_F7AFEE86`

Deprecated. Bulk Delete Managed Equipment Maintenance Log Attachments. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/company-managed-equipment-maintenance-log-attachment?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Identifier of the managed equipment maintenance log. |
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Bulk Delete Materials

**Slug:** `PROCORE_FIELD_OPERATIONS_BULK_DELETE_MATERIALS`

Bulk Delete Materials. Source: https://developers.procore.com/reference/rest/material?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Bulk Delete Time and Material Attachments

**Slug:** `PROCORE_FIELD_OPERATIONS_BULK_DELETE_TIME_AND_MATERIAL_34D0A956`

Bulk Delete Time and Material Attachments. Source: https://developers.procore.com/reference/rest/time-and-material-attachment?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Bulk Delete Time and material equipment logs

**Slug:** `PROCORE_FIELD_OPERATIONS_BULK_DELETE_TIME_AND_MATERIAL_97F91FD4`

Bulk Delete Time and material equipment logs. Source: https://developers.procore.com/reference/rest/time-and-material-equipment-log?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Bulk Delete Time and material timecards

**Slug:** `PROCORE_FIELD_OPERATIONS_BULK_DELETE_TIME_AND_MATERIAL_TIMECARDS`

Bulk Delete Time and material timecards. Source: https://developers.procore.com/reference/rest/time-and-material-timecard?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Bulk Destroy Actual Production Quantities

**Slug:** `PROCORE_FIELD_OPERATIONS_BULK_DESTROY_ACTUAL_PRODUCTION_20CD28F6`

Beta. Bulk Destroy Actual Production Quantities. This Procore endpoint is beta and its contract may change. Source: https://developers.procore.com/reference/rest/actual-production-quantities?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Bulk Retrieve Managed Equipment

**Slug:** `PROCORE_FIELD_OPERATIONS_BULK_RETRIEVE_MANAGED_EQUIPMENT`

Deprecated. Bulk Retrieve Managed Equipment. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/managed-equipment---company-level?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Bulk Update Actual Production Quantities

**Slug:** `PROCORE_FIELD_OPERATIONS_BULK_UPDATE_ACTUAL_PRODUCTION_F26A5080`

Beta. Bulk Update Actual Production Quantities. This Procore endpoint is beta and its contract may change. Source: https://developers.procore.com/reference/rest/actual-production-quantities?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Bulk Update Managed Equipment models

**Slug:** `PROCORE_FIELD_OPERATIONS_BULK_UPDATE_MANAGED_EQUIPMENT_MODELS`

Deprecated. Bulk Update Managed Equipment models. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/equipment-model?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Bulk Update Managed Equipment types

**Slug:** `PROCORE_FIELD_OPERATIONS_BULK_UPDATE_MANAGED_EQUIPMENT_TYPES`

Deprecated. Bulk Update Managed Equipment types. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/equipment-type?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Bulk Update Materials

**Slug:** `PROCORE_FIELD_OPERATIONS_BULK_UPDATE_MATERIALS`

Bulk Update Materials. Source: https://developers.procore.com/reference/rest/material?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Bulk Updates for Daily Logs

**Slug:** `PROCORE_FIELD_OPERATIONS_BULK_UPDATES_FOR_DAILY_LOGS`

Bulk Updates for Daily Logs. Source: https://developers.procore.com/reference/rest/daily-log-bulk-updates?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Bulk Update Time and Material Equipment logs

**Slug:** `PROCORE_FIELD_OPERATIONS_BULK_UPDATE_TIME_AND_MATERIAL_D98A7CCE`

Bulk Update Time and Material Equipment logs. Source: https://developers.procore.com/reference/rest/time-and-material-equipment-log?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Bulk Update Time and material timecards

**Slug:** `PROCORE_FIELD_OPERATIONS_BULK_UPDATE_TIME_AND_MATERIAL_TIMECARDS`

Bulk Update Time and material timecards. Source: https://developers.procore.com/reference/rest/time-and-material-timecard?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Bulk Update Timecard Entries

**Slug:** `PROCORE_FIELD_OPERATIONS_BULK_UPDATE_TIMECARD_ENTRIES`

Bulk Update Timecard Entries. Source: https://developers.procore.com/reference/rest/timesheets?version=1.1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Accident Log

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_ACCIDENT_LOG`

Create Accident Log. Source: https://developers.procore.com/reference/rest/accident-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `attachments` | array | No | Accident Log Attachments. To upload attachments you must upload the entire payload as `multipart/form-data` content-type and specify each parameter as form-data together with `attachments[]` as files. |
| `accident_log` | object | No | Structured accident log data matching the documented Procore schema. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Actual Production Quantity

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_ACTUAL_PRODUCTION_QUANTITY`

Create Actual Production Quantity. Source: https://developers.procore.com/reference/rest/actual-production-quantities?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create attachment

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_ATTACHMENT_TIME_AND_MAT_890D8AAA`

Create attachment. Source: https://developers.procore.com/reference/rest/time-and-material-attachment?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Calendar Item

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_CALENDAR_ITEM`

Create Calendar Item. Source: https://developers.procore.com/reference/rest/calendar-items?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Call Log

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_CALL_LOG`

Create Call Log. Source: https://developers.procore.com/reference/rest/call-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `call_log` | object | No | Structured call log data matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `attachments` | array | No | Call Log Attachments are not viewable or used on web. To upload attachments you must upload the entire payload as `multipart/form-data` content-type and specify each parameter as form-data together with `attachments[]` as files. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Clones Daily Logs from one Date to another Date

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_CLONES_DAILY_LOGS_FROM_213674A9`

Clones Daily Logs from one Date to another Date. Source: https://developers.procore.com/reference/rest/daily-log-clones?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `idempotency_token` | string | No | Client-generated UUID v4 identifying a create operation. Retrying with the same token returns the original result instead of creating a duplicate. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Daily Construction Report Log

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_DAILY_CONSTRUCTION_REPORT_LOG`

Create Daily Construction Report Log. Source: https://developers.procore.com/reference/rest/daily-construction-report-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `attachments` | array | No | Daily Construction Report Log Attachments. To upload attachments you must upload the entire payload as `multipart/form-data` content-type and specify each parameter as form-data together with `attachments[]` as files. |
| `run_configurable_validations` | boolean | No | If true, validations are run for the corresponding Configurable Field Set. |
| `daily_construction_report_log` | object | No | Structured daily construction report log data matching the documented Procore schema. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Delay Log

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_DELAY_LOG`

Create Delay Log. Source: https://developers.procore.com/reference/rest/delay-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `delay_log` | object | No | Structured delay log data matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `attachments` | array | No | Attachments pertaining the Log. To upload attachments you must upload the entire payload as `multipart/form-data` content-type and specify each parameter as form-data together with `attachments[]` as files. |
| `run_configurable_validations` | boolean | No | If true, validations are run for the corresponding Configurable Field Set. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Delivery Log

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_DELIVERY_LOG`

Create Delivery Log. Source: https://developers.procore.com/reference/rest/delivery-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `attachments` | array | No | Delivery Log Attachments are not viewable or used on web. To upload attachments you must upload the entire payload as `multipart/form-data` content-type and specify each parameter as form-data together with `attachments[]` as files. |
| `delivery_log` | object | No | Structured delivery log data matching the documented Procore schema. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Draft Create

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_DRAFT_CREATE`

Deprecated. Draft Create. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/timesheets?version=1.1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Dumpster Log

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_DUMPSTER_LOG`

Create Dumpster Log. Source: https://developers.procore.com/reference/rest/dumpster-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `attachments` | array | No | Dumpster Log Attachments are not viewable or used on web To upload attachments you must upload the entire payload as `multipart/form-data` content-type and specify each parameter as form-data together with `attachments[]` as files. |
| `dumpster_log` | object | No | Structured dumpster log data matching the documented Procore schema. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Email a Time And Material Entry

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_EMAIL_TIME_AND_MATERIAL_ENTRY`

Email a Time And Material Entry. This action has an irreversible external effect. Source: https://developers.procore.com/reference/rest/time-and-material-entry?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Unique identifier of the Time & Material entry. |
| `body` | object | Yes | Structured Procore email request. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Equipment

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_EQUIPMENT`

Deprecated. Create Equipment. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/managed-equipment---company-level?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create equipment Category

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_EQUIPMENT_CATEGORY`

Deprecated. Create equipment Category. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/equipment-category?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create equipment log

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_EQUIPMENT_LOG_COMPANY_E_7D3E41DC`

Deprecated. Create equipment log. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/equipment-log?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Equipment Log

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_EQUIPMENT_LOG_PROJECT_A_65E45AD1`

Create Equipment Log. Source: https://developers.procore.com/reference/rest/admin-equipment-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `attachments` | array | No | Equipment Log Attachments. To upload attachments you must upload the entire payload as `multipart/form-data` content-type and specify each parameter as form-data together with `attachments[]` as files. |
| `equipment_log` | object | No | Structured equipment log data matching the documented Procore schema. |
| `run_configurable_validations` | boolean | No | If true, validations are run for the corresponding Configurable Field Set. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Equipment Maintenance Log

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_EQUIPMENT_MAINTENANCE_LOG`

Deprecated. Create Equipment Maintenance Log. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/equipment-maintenance-log?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create an equipment make

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_EQUIPMENT_MAKE`

Deprecated. Create an equipment make. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/equipment-make?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create an equipment Model

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_EQUIPMENT_MODEL`

Deprecated. Create an equipment Model. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/equipment-model?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create an equipment type

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_EQUIPMENT_TYPE`

Deprecated. Create an equipment type. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/equipment-type?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Gps Position

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_GPS_POSITION`

Create Gps Position. Source: https://developers.procore.com/reference/rest/gps-positions?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Inspection Log

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_INSPECTION_LOG`

Create Inspection Log. Source: https://developers.procore.com/reference/rest/inspection-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `attachments` | array | No | Inspection Log Attachments are not viewable or used on web. To upload attachments you must upload the entire payload as `multipart/form-data` content-type and specify each parameter as form-data together with `attachments[]` as files. |
| `inspection_log` | object | No | Structured inspection log data matching the documented Procore schema. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Instructions

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_INSTRUCTIONS`

Create Instructions. Source: https://developers.procore.com/reference/rest/instructions?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Instruction Types

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_INSTRUCTION_TYPES`

Create Instruction Types. Source: https://developers.procore.com/reference/rest/instruction-types?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Lookahead

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_LOOKAHEAD`

Create Lookahead. Source: https://developers.procore.com/reference/rest/lookaheads?version=1.1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Lookahead Task

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_LOOKAHEAD_TASK`

Create Lookahead Task. Source: https://developers.procore.com/reference/rest/lookahead-tasks?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Lookahead

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_LOOKAHEAD_V1_0`

Create Lookahead. Source: https://developers.procore.com/api/v1/resource_groups/full_oas?version=1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create maintenance log attachment

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_MAINTENANCE_LOG_ATTACHMENT`

Deprecated. Create maintenance log attachment. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/company-managed-equipment-maintenance-log-attachment?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Identifier of the managed equipment maintenance log. |
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Manpower Log

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_MANPOWER_LOG`

Create Manpower Log. Source: https://developers.procore.com/reference/rest/manpower-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `attachments` | array | No | Manpower Log Attachments. To upload attachments you must upload the entire payload as `multipart/form-data` content-type and specify each parameter as form-data together with `attachments[]` as files. |
| `manpower_log` | object | No | Structured manpower log data matching the documented Procore schema. |
| `run_configurable_validations` | boolean | No | If true, validations are run for the corresponding Configurable Field Set. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Material

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_MATERIAL`

Create Material. Source: https://developers.procore.com/reference/rest/material?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create new Delay Log Type

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_NEW_DELAY_LOG_TYPE`

Create new Delay Log Type. Source: https://developers.procore.com/reference/rest/delay-log-types?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create a new equipment

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_NEW_EQUIPMENT`

Deprecated. Create a new equipment. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/managed-equipment---project-level?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create a new Time And Material Equipment Log

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_NEW_TIME_AND_MATERIAL_E_3D7AA7C0`

Create a new Time And Material Equipment Log. Source: https://developers.procore.com/reference/rest/time-and-material-equipment-log?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `run_configurable_validations` | boolean | No | If true, validations are run for the corresponding Configurable Field Set. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create a new Time And Material Entry

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_NEW_TIME_AND_MATERIAL_ENTRY`

Create a new Time And Material Entry. Source: https://developers.procore.com/reference/rest/time-and-material-entry?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `run_configurable_validations` | boolean | No | If true, validations are run for the corresponding Configurable Field Set. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create a new Time And Material Notification

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_NEW_TIME_AND_MATERIAL_N_294214A6`

Create a new Time And Material Notification. Source: https://developers.procore.com/reference/rest/time-and-material-notification?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `run_configurable_validations` | boolean | No | If true, validations are run for the corresponding Configurable Field Set. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Notes Log

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_NOTES_LOG`

Create Notes Log. Source: https://developers.procore.com/reference/rest/notes-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `notes_log` | object | No | Structured notes log data matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `attachments` | array | No | Notes Log Attachments are not viewable or used on web. To upload attachments you must upload the entire payload as `multipart/form-data` content-type and specify each parameter as form-data together with `attachments[]` as files. |
| `run_configurable_validations` | boolean | No | If true, validations are run for the corresponding Configurable Field Set. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create a piece of Equipment

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_PIECE_OF_EQUIPMENT`

Create a piece of Equipment. Source: https://developers.procore.com/reference/rest/time-and-material-entry?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Plan Revision Log

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_PLAN_REVISION_LOG`

Create Plan Revision Log. Source: https://developers.procore.com/reference/rest/plan-revision-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `attachments` | array | No | Plan Revision Log Attachments are not viewable or used on web. To upload attachments you must upload the entire payload as `multipart/form-data` content-type and specify each parameter as form-data together with `attachments[]` as files. |
| `plan_revision_log` | object | No | Structured plan revision log data matching the documented Procore schema. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Productivity Log

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_PRODUCTIVITY_LOG`

Create Productivity Log. Source: https://developers.procore.com/reference/rest/productivity-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create an Project Equipment Log

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_PROJECT_EQUIPMENT_LOG`

Deprecated. Create an Project Equipment Log. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/equipment-log?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Project Equipment Maintenance Log

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_PROJECT_EQUIPMENT_MAINT_C20A24D5`

Deprecated. Create Project Equipment Maintenance Log. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/equipment-maintenance-log?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Signature for Timesheet

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_PROJECT_TIMESHEET_SIGNATURE`

Create Signature for Timesheet. Source: https://developers.procore.com/api/v1/resource_groups/full_oas?version=1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Quantity Log

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_QUANTITY_LOG`

Create Quantity Log. Source: https://developers.procore.com/reference/rest/quantity-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `attachments` | array | No | Quantity Log Attachments. To upload attachments you must upload the entire payload as `multipart/form-data` content-type and specify each parameter as form-data together with `attachments[]` as files. |
| `quantity_log` | object | No | Structured quantity log data matching the documented Procore schema. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Creates Requested Change

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_REQUESTED_CHANGE_GLOBAL_30FFE0C4`

Deprecated. Creates Requested Change. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/requested-changes?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `task_id` | integer | Yes | The task for which requested changes will be added to. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Requested Change

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_REQUESTED_CHANGE_PROJEC_F36EAFBE`

Create Requested Change. Source: https://developers.procore.com/reference/rest/task-requested-changes?version=1.1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `task_id` | integer | Yes | Task ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create resource

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_RESOURCE`

Create resource. Source: https://developers.procore.com/reference/rest/schedule-resources?version=1.1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create resource

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_RESOURCE_V1_0`

Create resource. Source: https://developers.procore.com/api/v1/resource_groups/full_oas?version=1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create rounding configuration

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_ROUNDING_CONFIGURATION`

Create rounding configuration. Source: https://developers.procore.com/reference/rest/rounding-configuration?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Safety Violation Log

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_SAFETY_VIOLATION_LOG`

Create Safety Violation Log. Source: https://developers.procore.com/reference/rest/safety-violation-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `attachments` | array | No | Safety Violation Log Attachments are not viewable or used on web. To upload attachments you must upload the entire payload as `multipart/form-data` content-type and specify each parameter as form-data together with `attachments[]` as files. |
| `safety_violation_log` | object | No | Structured safety violation log data matching the documented Procore schema. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Setup Managed Equipment Taxonomy

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_SETUP_MANAGED_EQUIPMENT_TAXONOMY`

Deprecated. Setup Managed Equipment Taxonomy. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/managed-equipment---company-level?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Signature for Time and Material Entry

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_SIGNATURE_FOR_TIME_AND_F8374167`

Create Signature for Time and Material Entry. Source: https://developers.procore.com/reference/rest/time-and-material-signature?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Signature for Timesheet

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_SIGNATURE_FOR_TIMESHEET`

Create Signature for Timesheet. Source: https://developers.procore.com/reference/rest/timesheets?version=1.1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create task

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_TASK`

Create task. Source: https://developers.procore.com/reference/rest/tasks?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Time And Material Timecard

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_TIME_AND_MATERIAL_TIMECARD`

Create Time And Material Timecard. Source: https://developers.procore.com/reference/rest/time-and-material-timecard?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `run_configurable_validations` | boolean | No | If true, validations are run for the corresponding Configurable Field Set. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create timecard entry (Company)

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_TIMECARD_ENTRY_COMPANY`

Create timecard entry (Company). Source: https://developers.procore.com/reference/rest/timecard-entries?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create timecard entry

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_TIMECARD_ENTRY_GLOBAL_T_95E28737`

Create timecard entry. Source: https://developers.procore.com/reference/rest/timecard-entries?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create timecard entry (Project)

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_TIMECARD_ENTRY_PROJECT`

Create timecard entry (Project). Source: https://developers.procore.com/reference/rest/timecard-entries?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `serializer_view` | string | No | Changes which fields are included in the serialized response. - `extended_daily_log` - Returns extended fields plus Daily Log segment associations - Default (not specified) - Returns the standard extended Daily Log field set  |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Timecard Entry

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_TIMECARD_ENTRY_PROJECT_AE77F64E`

Create Timecard Entry. Source: https://developers.procore.com/reference/rest/timesheets?version=1.1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Timeline Event

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_TIMELINE_EVENT`

Create Timeline Event. Source: https://developers.procore.com/reference/rest/timeline-events?version=2.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | string | Yes | Unique identifier for the company |
| `project_id` | string | Yes | Unique identifier for the project |
| `schedule_id` | string | Yes | Unique identifier for the schedule |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Timesheet

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_TIMESHEET`

Create Timesheet. Source: https://developers.procore.com/reference/rest/timesheets?version=1.1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create timesheet to budget configuration

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_TIMESHEET_TO_BUDGET_CON_8BDEB276`

Create timesheet to budget configuration. Source: https://developers.procore.com/reference/rest/timesheet-to-budget-configuration?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create todo

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_TODO`

Deprecated. Create todo. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/todos?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Visitor Log

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_VISITOR_LOG`

Create Visitor Log. Source: https://developers.procore.com/reference/rest/visitor-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `run_configurable_validations` | boolean | No | If true, validations are run for the corresponding Configurable Field Set. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Waste Log

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_WASTE_LOG`

Create Waste Log. Source: https://developers.procore.com/reference/rest/waste-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `waste_log` | object | No | Structured waste log data matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `attachments` | array | No | Waste Log Attachments are not viewable or used on web. To upload attachments you must upload the entire payload as `multipart/form-data` content-type and specify each parameter as form-data together with `attachments[]` as files. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Weather Log

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_WEATHER_LOG`

Create Weather Log. Source: https://developers.procore.com/reference/rest/weather-logs?version=1.1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `attachments` | array | No | Weather Log Attachments. To upload attachments you must upload the entire payload as `multipart/form-data` content-type and specify each parameter as form-data together with `attachments[]` as files. |
| `weather_log` | object | No | Structured weather log data matching the documented Procore schema. |
| `run_configurable_validations` | boolean | No | If true, validations are run for the corresponding Configurable Field Set. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Work Log

**Slug:** `PROCORE_FIELD_OPERATIONS_CREATE_WORK_LOG`

Create Work Log. Source: https://developers.procore.com/reference/rest/work-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `work_log` | object | No | Structured work log data matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `attachments` | array | No | Scheduled Work Log Attachments are not viewable or used on web. To upload attachments you must upload the entire payload as `multipart/form-data` content-type and specify each parameter as form-data together with `attachments[]` as files. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Accident Log

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_ACCIDENT_LOG`

Delete Accident Log. Source: https://developers.procore.com/reference/rest/accident-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Accident log ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Actual Production Quantity

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_ACTUAL_PRODUCTION_QUANTITY`

Delete Actual Production Quantity. Source: https://developers.procore.com/reference/rest/actual-production-quantities?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Unique identifier of the Actual Production Quantity. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Calendar Item

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_CALENDAR_ITEM`

Delete Calendar Item. Source: https://developers.procore.com/reference/rest/calendar-items?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Calendar Item ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Call Log

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_CALL_LOG`

Delete Call Log. Source: https://developers.procore.com/reference/rest/call-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Call log ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Daily Construction Report Log

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_DAILY_CONSTRUCTION_REPORT_LOG`

Delete Daily Construction Report Log. Source: https://developers.procore.com/reference/rest/daily-construction-report-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Daily Construction Report Log ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Delay Log

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_DELAY_LOG`

Delete Delay Log. Source: https://developers.procore.com/reference/rest/delay-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Delay log ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Delivery Log

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_DELIVERY_LOG`

Delete Delivery Log. Source: https://developers.procore.com/reference/rest/delivery-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Delivery Log ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Dumpster Log

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_DUMPSTER_LOG`

Delete Dumpster Log. Source: https://developers.procore.com/reference/rest/dumpster-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Dumpster Log ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Equipment Category

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_EQUIPMENT_CATEGORY`

Deprecated. Delete Equipment Category. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/equipment-category?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | ID of the Equipment Category |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Equipment

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_EQUIPMENT_COMPANY_MANAG_0DEAF16C`

Deprecated. Delete Equipment. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/managed-equipment---company-level?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Unique identifier of the managed equipment. |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Equipment Log

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_EQUIPMENT_LOG`

Delete Equipment Log. Source: https://developers.procore.com/reference/rest/admin-equipment-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Equipment Log ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Equipment Maintenance Log

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_EQUIPMENT_MAINTENANCE_LOG`

Deprecated. Delete Equipment Maintenance Log. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/equipment-maintenance-log?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Identifier of the equipment maintenance log. |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete an equipment make

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_EQUIPMENT_MAKE`

Deprecated. Delete an equipment make. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/equipment-make?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | ID of the equipment make |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete an equipment model

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_EQUIPMENT_MODEL`

Deprecated. Delete an equipment model. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/equipment-model?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Unique identifier of the equipment model. |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete an equipment

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_EQUIPMENT_PROJECT_MANAG_54FBDDDF`

Deprecated. Delete an equipment. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/managed-equipment---project-level?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Unique identifier of the managed equipment. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete equipment timecard entry (Project)

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_EQUIPMENT_TIMECARD_ENTRY_PROJECT`

Beta. Delete equipment timecard entry (Project). This Procore endpoint is beta and its contract may change. Source: https://developers.procore.com/reference/rest/equipment-timecard-entries?version=2.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | ID of the equipment timecard entry |
| `company_id` | integer | Yes | Unique identifier for the company. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete a equipment type

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_EQUIPMENT_TYPE`

Deprecated. Delete a equipment type. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/equipment-type?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Unique identifier of the equipment type. |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Inspection Log

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_INSPECTION_LOG`

Delete Inspection Log. Source: https://developers.procore.com/reference/rest/inspection-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Inspection Log ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Instruction

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_INSTRUCTION`

Delete Instruction. Source: https://developers.procore.com/reference/rest/instructions?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Instruction ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Instruction Type

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_INSTRUCTION_TYPE`

Delete Instruction Type. Source: https://developers.procore.com/reference/rest/instruction-types?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Instruction ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Lookahead

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_LOOKAHEAD`

Delete Lookahead. Source: https://developers.procore.com/reference/rest/lookaheads?version=1.1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Lookahead ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Lookahead Task

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_LOOKAHEAD_TASK`

Delete Lookahead Task. Source: https://developers.procore.com/reference/rest/lookahead-tasks?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Lookahead Task ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Lookahead

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_LOOKAHEAD_V1_0`

Delete Lookahead. Source: https://developers.procore.com/api/v1/resource_groups/full_oas?version=1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Lookahead ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Managed Equipment Attachment

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_MANAGED_EQUIPMENT_ATTACHMENT`

Deprecated. Delete Managed Equipment Attachment. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/managed-equipment-attachment?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Unique identifier of the managed equipment attachment. |
| `company_id` | integer | Yes | Unique identifier for the company. |
| `managed_equipment_id` | integer | Yes | Identifier of the managed equipment that owns the attachment. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Managed Equipment Maintenance Log Attachment

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_MANAGED_EQUIPMENT_MAINT_B38507FC`

Deprecated. Delete Managed Equipment Maintenance Log Attachment. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/company-managed-equipment-maintenance-log-attachment?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Identifier of the managed equipment maintenance log. |
| `company_id` | integer | Yes | Unique identifier for the company. |
| `attachment_id` | integer | Yes | Identifier of the managed equipment maintenance log attachment. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Manpower Log

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_MANPOWER_LOG`

Delete Manpower Log. Source: https://developers.procore.com/reference/rest/manpower-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Manpower Log ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Material

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_MATERIAL`

Delete Material. Source: https://developers.procore.com/reference/rest/material?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Unique identifier of the material. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Multiple Signatures

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_MULTIPLE_SIGNATURES`

Delete Multiple Signatures. Source: https://developers.procore.com/reference/rest/time-and-material-signature?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Notes Log

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_NOTES_LOG`

Delete Notes Log. Source: https://developers.procore.com/reference/rest/notes-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Notes Log ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Plan Revision Log

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_PLAN_REVISION_LOG`

Delete Plan Revision Log. Source: https://developers.procore.com/reference/rest/plan-revision-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Plan Revision Log ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Productivity Log

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_PRODUCTIVITY_LOG`

Delete Productivity Log. Source: https://developers.procore.com/reference/rest/productivity-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Productivity Log ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete an Project Equipment Log

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_PROJECT_EQUIPMENT_LOG`

Deprecated. Delete an Project Equipment Log. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/equipment-log?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Identifier of the equipment log entry. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Project Equipment Maintenance Log

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_PROJECT_EQUIPMENT_MAINT_D32209DB`

Deprecated. Delete Project Equipment Maintenance Log. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/equipment-maintenance-log?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Identifier of the equipment maintenance log. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Quantity Log

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_QUANTITY_LOG`

Delete Quantity Log. Source: https://developers.procore.com/reference/rest/quantity-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Quantity Log ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete resource

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_RESOURCE`

Delete resource. Source: https://developers.procore.com/reference/rest/schedule-resources?version=1.1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | ID of the resource |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete resource

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_RESOURCE_V1_0`

Delete resource. Source: https://developers.procore.com/api/v1/resource_groups/full_oas?version=1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | ID of the resource |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete rounding configuration

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_ROUNDING_CONFIGURATION`

Delete rounding configuration. Source: https://developers.procore.com/reference/rest/rounding-configuration?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Safety Violation Log

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_SAFETY_VIOLATION_LOG`

Delete Safety Violation Log. Source: https://developers.procore.com/reference/rest/safety-violation-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Safety Violation Log ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete A Signature

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_SIGNATURE_COMPANY_TIMES_2FA406CB`

Delete A Signature. Source: https://developers.procore.com/reference/rest/timesheets?version=1.1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | ID |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Signature

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_SIGNATURE_PROJECT_TIME_827BA64E`

Delete Signature. Source: https://developers.procore.com/reference/rest/time-and-material-signature?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Signature ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Signature

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_SIGNATURE_PROJECT_TIMES_1C3BB9E2`

Delete Signature. Source: https://developers.procore.com/reference/rest/timesheets?version=1.1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Signature ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete task

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_TASK`

Delete task. Source: https://developers.procore.com/reference/rest/tasks?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | ID of the task |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete a Time and Material Attachment

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_TIME_AND_MATERIAL_ATTACHMENT`

Delete a Time and Material Attachment. Source: https://developers.procore.com/reference/rest/time-and-material-attachment?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | ID of the Time and Material Attachment |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete a Time And Material Entry

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_TIME_AND_MATERIAL_ENTRY`

Delete a Time And Material Entry. Source: https://developers.procore.com/reference/rest/time-and-material-entry?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Unique identifier of the Time & Material entry. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete a Time And Material Equipment Log

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_TIME_AND_MATERIAL_EQUIPMENT_LOG`

Delete a Time And Material Equipment Log. Source: https://developers.procore.com/reference/rest/time-and-material-equipment-log?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Unique identifier of the Time & Material equipment log. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete a Time And Material Notification

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_TIME_AND_MATERIAL_NOTIFICATION`

Delete a Time And Material Notification. Source: https://developers.procore.com/reference/rest/time-and-material-notification?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Time And Material Timecard

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_TIME_AND_MATERIAL_TIMECARD`

Delete Time And Material Timecard. Source: https://developers.procore.com/reference/rest/time-and-material-timecard?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Unique identifier of the Time & Material timecard. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Timecard Entries

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_TIMECARD_ENTRIES`

Delete Timecard Entries. Source: https://developers.procore.com/reference/rest/timesheets?version=1.1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete timecard entry

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_TIMECARD_ENTRY`

Delete timecard entry. Source: https://developers.procore.com/reference/rest/timecard-entries?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | ID of the timecard entry |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete timecard entry (Company)

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_TIMECARD_ENTRY_COMPANY`

Delete timecard entry (Company). Source: https://developers.procore.com/reference/rest/timecard-entries?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | ID of the timecard entry |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete timecard entry (Project)

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_TIMECARD_ENTRY_PROJECT`

Delete timecard entry (Project). Source: https://developers.procore.com/reference/rest/timecard-entries?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | ID of the timecard entry |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Timeline Event

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_TIMELINE_EVENT`

Delete Timeline Event. Source: https://developers.procore.com/reference/rest/timeline-events?version=2.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `company_id` | string | Yes | Unique identifier for the company |
| `project_id` | string | Yes | Unique identifier for the project |
| `schedule_id` | string | Yes | Unique identifier for the schedule |
| `timeline_event_id` | string | Yes | Timeline Events ID |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Timesheet

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_TIMESHEET`

Beta. Delete Timesheet. This Procore endpoint is beta and its contract may change. Source: https://developers.procore.com/reference/rest/timesheets?version=1.1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete timesheet to budget configuration

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_TIMESHEET_TO_BUDGET_CON_5B5DD41A`

Delete timesheet to budget configuration. Source: https://developers.procore.com/reference/rest/timesheet-to-budget-configuration?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete todo

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_TODO`

Deprecated. Delete todo. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/todos?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | ID of the todo |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Visitor Log

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_VISITOR_LOG`

Delete Visitor Log. Source: https://developers.procore.com/reference/rest/visitor-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Visitor Log ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Waste Log

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_WASTE_LOG`

Delete Waste Log. Source: https://developers.procore.com/reference/rest/waste-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Waste Log ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Weather Log

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_WEATHER_LOG`

Delete Weather Log. Source: https://developers.procore.com/reference/rest/weather-logs?version=1.1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Weather Log ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Work Log

**Slug:** `PROCORE_FIELD_OPERATIONS_DELETE_WORK_LOG`

Delete Work Log. Source: https://developers.procore.com/reference/rest/work-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Work Log ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Download schedule file

**Slug:** `PROCORE_FIELD_OPERATIONS_DOWNLOAD_SCHEDULE_FILE`

Downloads a file. Download schedule file. Returns the documented file response. Source: https://developers.procore.com/reference/rest/schedule-integration?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Export Company Time Index to CSV

**Slug:** `PROCORE_FIELD_OPERATIONS_EXPORT_COMPANY_TIME_INDEX_TO_CSV`

Deprecated Downloads a file. Export Company Time Index to CSV. This Procore endpoint is deprecated; use it only for legacy workflows. Returns the documented file response. Source: https://developers.procore.com/reference/rest/timesheets?version=1.1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique identifier for the company. |
| `filters_end_date` | string | No | Provider parameter `filters[end_date]`. |
| `filters_deleted_at` | string | No | Returns item(s) deleted within the specified ISO 8601 datetime range. |
| `filters_start_date` | string | No | Provider parameter `filters[start_date]`. |
| `filters_updated_at` | string | No | Return item(s) last updated within the specified ISO 8601 datetime range. Formats: `YYYY-MM-DD`...`YYYY-MM-DD` - Date `YYYY-MM-DDTHH:MM:SSZ`...`YYYY-MM-DDTHH:MM:SSZ` - DateTime with UTC Offset `YYYY-MM-DDTHH:MM:SS+XX:00`...`YYYY-MM-DDTHH:MM:SS+XX:00` - Datetime with Custom Offset |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show Accident Logs

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_ACCIDENT_LOGS`

Show Accident Logs. Source: https://developers.procore.com/reference/rest/accident-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Accident log ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Activity by ID

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_ACTIVITY_BY_ID`

Get Activity by ID. Source: https://developers.procore.com/reference/rest/activities?version=2.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `company_id` | string | Yes | Unique identifier for the company |
| `project_id` | string | Yes | Unique identifier for the project |
| `activity_id` | string | Yes | unique identifier of the activity |
| `schedule_id` | string | Yes | Unique identifier for the schedule |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Activity Link by ID

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_ACTIVITY_LINK_BY_ID`

Get Activity Link by ID. Source: https://developers.procore.com/reference/rest/activity-links?version=2.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `company_id` | string | Yes | Unique identifier for the company |
| `project_id` | string | Yes | Unique identifier for the project |
| `schedule_id` | string | Yes | Unique identifier for the schedule |
| `activity_link_id` | string | Yes | Activity Link ID |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show Actual Production Quantity

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_ACTUAL_PRODUCTION_QUANTITY`

Show Actual Production Quantity. Source: https://developers.procore.com/reference/rest/actual-production-quantities?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Unique identifier of the Actual Production Quantity. |
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Calendar by ID (V2.1)

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_CALENDAR_BY_ID_V2_1`

Get Calendar by ID (V2.1). Source: https://developers.procore.com/reference/rest/calendars?version=2.1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `company_id` | string | Yes | Unique identifier for the company |
| `project_id` | string | Yes | Unique identifier for the project |
| `calendar_id` | string | Yes | Calendar ID |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show Calendar Item

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_CALENDAR_ITEM`

Show Calendar Item. Source: https://developers.procore.com/reference/rest/calendar-items?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Calendar Item ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show Call Logs

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_CALL_LOGS`

Show Call Logs. Source: https://developers.procore.com/reference/rest/call-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Call log ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show Change History

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_CHANGE_HISTORY_TIME_AND_MA_DB0BDC50`

Show Change History. Source: https://developers.procore.com/reference/rest/time-and-material-entry?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Unique identifier of the Time & Material entry. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show Daily Construction Report Logs

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_DAILY_CONSTRUCTION_REPORT_LOGS`

Show Daily Construction Report Logs. Source: https://developers.procore.com/reference/rest/daily-construction-report-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Daily Construction Report Log ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Daily Log Headers for the Project

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_DAILY_LOG_HEADERS_FOR_PROJECT`

Get Daily Log Headers for the Project. Source: https://developers.procore.com/reference/rest/daily-log-headers?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `end_date` | string | No | The right (latest) boundary of the requested date range, inclusive, matched against each header's `log_date`. Defaults to today when omitted and is always capped at today, so a future `end_date` returns results only through the current date. |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `start_date` | string | No | The left (earliest) boundary of the requested date range, inclusive, matched against each header's `log_date`. Defaults to the project's creation date when omitted. Supply a `start_date` earlier than the project's creation date to retrieve headers dated before the project was created. |
| `next_cursor` | string | No | Continuation cursor from the previous page. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get the Daily Log Header via date or id

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_DAILY_LOG_HEADER_VIA_DATE_OR_ID`

Get the Daily Log Header via date or id. Source: https://developers.procore.com/reference/rest/daily-log-headers?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | No | The id of the requested Daily Log Header |
| `log_date` | string | No | The log date for the requested Daily Log Header |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show Delay Logs

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_DELAY_LOGS`

Show Delay Logs. Source: https://developers.procore.com/reference/rest/delay-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Delay log ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show Delivery Log

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_DELIVERY_LOG`

Show Delivery Log. Source: https://developers.procore.com/reference/rest/delivery-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Delivery Log ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show Dumpster Logs

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_DUMPSTER_LOGS`

Show Dumpster Logs. Source: https://developers.procore.com/reference/rest/dumpster-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Dumpster Log ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show an equipment category

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_EQUIPMENT_CATEGORY`

Deprecated. Show an equipment category. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/equipment-category?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | ID of the equipment category |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show Equipment Change History

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_EQUIPMENT_CHANGE_HISTORY`

Deprecated. Show Equipment Change History. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/managed-equipment---company-level?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Unique identifier of the managed equipment. |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show Equipment

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_EQUIPMENT_COMPANY_MANAGED_48094FC1`

Deprecated. Show Equipment. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/managed-equipment---company-level?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Unique identifier of the managed equipment. |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Retrieve Equipment

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_EQUIPMENT_COMPANY_MANAGED_DD9B0E90`

Deprecated. Retrieve Equipment. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/managed-equipment---company-level?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Unique identifier of the managed equipment. |
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show an equipment log

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_EQUIPMENT_LOG`

Deprecated. Show an equipment log. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/equipment-log?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Identifier of the equipment log entry. |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show Equipment Logs

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_EQUIPMENT_LOGS`

Show Equipment Logs. Source: https://developers.procore.com/reference/rest/admin-equipment-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Equipment Log ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show Equipment Maintenance Log

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_EQUIPMENT_MAINTENANCE_LOG`

Deprecated. Show Equipment Maintenance Log. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/equipment-maintenance-log?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Identifier of the equipment maintenance log. |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show an equipment make

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_EQUIPMENT_MAKE`

Deprecated. Show an equipment make. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/equipment-make?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | ID of the equipment make |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show an equipment model

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_EQUIPMENT_MODEL`

Deprecated. Show an equipment model. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/equipment-model?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Unique identifier of the equipment model. |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show equipment

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_EQUIPMENT_PROJECT_MANAGED_DE2DAC91`

Deprecated. Show equipment. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/managed-equipment---project-level?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Unique identifier of the managed equipment. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show an equipment type

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_EQUIPMENT_TYPE`

Deprecated. Show an equipment type. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/equipment-type?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Unique identifier of the equipment type. |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show Gps Position

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_GPS_POSITION`

Show Gps Position. Source: https://developers.procore.com/reference/rest/gps-positions?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | ID of the Gps Position |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get import logs

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_IMPORT_LOGS`

Get import logs. Source: https://developers.procore.com/reference/rest/import-logs?version=2.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `job_id` | string | Yes | Import job id |
| `locale` | string | No | Optional. Locale for parsing the import report (e.g. en, fr-FR, ja-JP). Must match the locale used when the import was initiated. A mismatch will result in a parsing error. |
| `company_id` | string | Yes | Unique identifier for the company |
| `project_id` | string | Yes | Unique identifier for the project |
| `schedule_id` | string | Yes | Unique identifier for the schedule |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get import status

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_IMPORT_STATUS`

Get import status. Source: https://developers.procore.com/reference/rest/import-status?version=2.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `job_id` | string | Yes | Import job id |
| `company_id` | string | Yes | Unique identifier for the company |
| `project_id` | string | Yes | Unique identifier for the project |
| `schedule_id` | string | Yes | Unique identifier for the schedule |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show an individual managed equipment maintenance log attachment

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_INDIVIDUAL_MANAGED_EQUIPME_821CDF24`

Deprecated. Show an individual managed equipment maintenance log attachment. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/company-managed-equipment-maintenance-log-attachment?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Identifier of the managed equipment maintenance log. |
| `company_id` | integer | Yes | Unique identifier for the company. |
| `attachment_id` | integer | Yes | Identifier of the managed equipment maintenance log attachment. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show an individual time and material attachment

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_INDIVIDUAL_TIME_AND_MATERI_B5940A29`

Show an individual time and material attachment. Source: https://developers.procore.com/reference/rest/time-and-material-attachment?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Unique identifier of the Time & Material attachment. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show Inspection Logs

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_INSPECTION_LOGS`

Show Inspection Logs. Source: https://developers.procore.com/reference/rest/inspection-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Inspection Log ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show Instruction

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_INSTRUCTION`

Show Instruction. Source: https://developers.procore.com/reference/rest/instructions?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Instruction ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show Instruction Type

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_INSTRUCTION_TYPE`

Show Instruction Type. Source: https://developers.procore.com/reference/rest/instruction-types?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Instruction ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get a list of possible Timesheet Creator Ids

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_LIST_OF_POSSIBLE_TIMESHEET_08BDAA15`

Get a list of possible Timesheet Creator Ids. Source: https://developers.procore.com/reference/rest/timesheets?version=1.1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get a list of possible Timesheet Creators

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_LIST_OF_POSSIBLE_TIMESHEET_CREATORS`

Get a list of possible Timesheet Creators. Source: https://developers.procore.com/reference/rest/timesheets?version=1.1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `next_cursor` | string | No | Continuation cursor from the previous page. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show Lookahead

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_LOOKAHEAD`

Show Lookahead. Source: https://developers.procore.com/reference/rest/lookaheads?version=1.1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Lookahead ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show Lookahead

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_LOOKAHEAD_V1_0`

Show Lookahead. Source: https://developers.procore.com/api/v1/resource_groups/full_oas?version=1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Lookahead ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show Manpower Logs

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_MANPOWER_LOGS`

Show Manpower Logs. Source: https://developers.procore.com/reference/rest/manpower-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Manpower Log ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show Material

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_MATERIAL`

Show Material. Source: https://developers.procore.com/reference/rest/material?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Unique identifier of the material. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show Notes Logs

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_NOTES_LOGS`

Show Notes Logs. Source: https://developers.procore.com/reference/rest/notes-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Notes Log ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show Plan Revision Logs

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_PLAN_REVISION_LOGS`

Show Plan Revision Logs. Source: https://developers.procore.com/reference/rest/plan-revision-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Plan Revision Log ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show Productivity Logs

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_PRODUCTIVITY_LOGS`

Show Productivity Logs. Source: https://developers.procore.com/reference/rest/productivity-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Productivity Log ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show an Project Equipment Log

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_PROJECT_EQUIPMENT_LOG`

Deprecated. Show an Project Equipment Log. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/equipment-log?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Identifier of the equipment log entry. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show Project Equipment Maintenance Log

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_PROJECT_EQUIPMENT_MAINTENANCE_LOG`

Deprecated. Show Project Equipment Maintenance Log. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/equipment-maintenance-log?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Identifier of the equipment maintenance log. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show Project Schedule Settings

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_PROJECT_SCHEDULE_SETTINGS`

Show Project Schedule Settings. Source: https://developers.procore.com/reference/rest/schedule-settings?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show A Signature

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_PROJECT_TIMESHEET_SIGNATURE`

Show A Signature. Source: https://developers.procore.com/api/v1/resource_groups/full_oas?version=1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Signature ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show Quantity Logs

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_QUANTITY_LOGS`

Show Quantity Logs. Source: https://developers.procore.com/reference/rest/quantity-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Quantity Log ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show recent Timecard Entry wbs code ids (DEPRECATED)

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_RECENT_TIMECARD_ENTRY_WBS_2102728A`

Deprecated. Show recent Timecard Entry wbs code ids (DEPRECATED). This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/timesheets?version=1.1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show resource

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_RESOURCE`

Show resource. Source: https://developers.procore.com/reference/rest/schedule-resources?version=1.1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | ID of the resource |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show resource assignment

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_RESOURCE_ASSIGNMENT`

Show resource assignment. Source: https://developers.procore.com/reference/rest/schedule-resource-assignments?version=1.1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | ID of the resource assignment. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show resource

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_RESOURCE_V1_0`

Show resource. Source: https://developers.procore.com/api/v1/resource_groups/full_oas?version=1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | ID of the resource |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show rounding configuration

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_ROUNDING_CONFIGURATION`

Show rounding configuration. Source: https://developers.procore.com/reference/rest/rounding-configuration?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show Safety Violation Logs

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_SAFETY_VIOLATION_LOGS`

Show Safety Violation Logs. Source: https://developers.procore.com/reference/rest/safety-violation-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Safety Violation Log ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Schedule by ID

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_SCHEDULE_BY_ID`

Get Schedule by ID. Source: https://developers.procore.com/reference/rest/schedules?version=2.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `company_id` | string | Yes | Unique identifier for the company |
| `project_id` | string | Yes | Unique identifier for the project |
| `schedule_id` | string | Yes | Unique identifier for the schedule |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Schedule Import processing state

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_SCHEDULE_IMPORT_PROCESSING_STATE`

Get Schedule Import processing state. Source: https://developers.procore.com/reference/rest/schedule-imports?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show the schedule integration type for a project

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_SCHEDULE_INTEGRATION_TYPE_25461B8A`

Deprecated. Show the schedule integration type for a project. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/schedule-type?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Schedule Metadata

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_SCHEDULE_METADATA`

Get Schedule Metadata. Source: https://developers.procore.com/reference/rest/schedule?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show A Signature

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_SIGNATURE_COMPANY_TIMESHEETS_V1_1`

Show A Signature. Source: https://developers.procore.com/reference/rest/timesheets?version=1.1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | ID |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show A Signature

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_SIGNATURE_PROJECT_TIME_AND_0E37D81B`

Show A Signature. Source: https://developers.procore.com/reference/rest/time-and-material-signature?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Signature ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show task

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_TASK`

Show task. Source: https://developers.procore.com/reference/rest/tasks?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | ID of the task |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show Time And Material Entry

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_TIME_AND_MATERIAL_ENTRY`

Show Time And Material Entry. Source: https://developers.procore.com/reference/rest/time-and-material-entry?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Unique identifier of the Time & Material entry. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show Time And Material Equipment Log

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_TIME_AND_MATERIAL_EQUIPMENT_LOG`

Show Time And Material Equipment Log. Source: https://developers.procore.com/reference/rest/time-and-material-equipment-log?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Unique identifier of the Time & Material equipment log. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show Time And Material Notification

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_TIME_AND_MATERIAL_NOTIFICATION`

Show Time And Material Notification. Source: https://developers.procore.com/reference/rest/time-and-material-notification?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show Time And Material Timecard

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_TIME_AND_MATERIAL_TIMECARD`

Show Time And Material Timecard. Source: https://developers.procore.com/reference/rest/time-and-material-timecard?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Unique identifier of the Time & Material timecard. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show timecard entry

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_TIMECARD_ENTRY`

Show timecard entry. Source: https://developers.procore.com/reference/rest/timecard-entries?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | ID of the timecard entry |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show timecard entry change history (Company)

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_TIMECARD_ENTRY_CHANGE_HIST_9EB4B2CE`

Show timecard entry change history (Company). Source: https://developers.procore.com/reference/rest/timecard-entries?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | ID of the timecard entry |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show timecard entry (Company)

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_TIMECARD_ENTRY_COMPANY`

Show timecard entry (Company). Source: https://developers.procore.com/reference/rest/timecard-entries?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | ID of the timecard entry |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show timecard entry (Project)

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_TIMECARD_ENTRY_PROJECT`

Show timecard entry (Project). Source: https://developers.procore.com/reference/rest/timecard-entries?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | ID of the timecard entry |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `serializer_view` | string | No | Changes which fields are included in the serialized response. - `extended_daily_log` - Returns extended fields plus Daily Log segment associations - Default (not specified) - Returns the standard extended Daily Log field set  |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Timeline Event by ID

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_TIMELINE_EVENT_BY_ID`

Get Timeline Event by ID. Source: https://developers.procore.com/reference/rest/timeline-events?version=2.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `company_id` | string | Yes | Unique identifier for the company |
| `project_id` | string | Yes | Unique identifier for the project |
| `schedule_id` | string | Yes | Unique identifier for the schedule |
| `timeline_event_id` | string | Yes | Timeline Events ID |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show A Timesheet

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_TIMESHEET`

Show A Timesheet. Source: https://developers.procore.com/reference/rest/timesheets?version=1.1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show timesheet approval status filters

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_TIMESHEET_APPROVAL_STATUS_FILTERS`

Show timesheet approval status filters. Source: https://developers.procore.com/reference/rest/timesheets-filters?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show timesheet billable filters

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_TIMESHEET_BILLABLE_FILTERS`

Show timesheet billable filters. Source: https://developers.procore.com/reference/rest/timesheets-filters?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show timesheet created by filters

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_TIMESHEET_CREATED_BY_FILTERS`

Show timesheet created by filters. Source: https://developers.procore.com/reference/rest/timesheets-filters?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show timesheet crews filters

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_TIMESHEET_CREWS_FILTERS`

Show timesheet crews filters. Source: https://developers.procore.com/reference/rest/timesheets-filters?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show timesheet department filters

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_TIMESHEET_DEPARTMENT_FILTERS`

Show timesheet department filters. Source: https://developers.procore.com/reference/rest/timesheets-filters?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show timesheet employee filters

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_TIMESHEET_EMPLOYEE_FILTERS`

Show timesheet employee filters. Source: https://developers.procore.com/reference/rest/timesheets-filters?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show timesheet employee id filters

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_TIMESHEET_EMPLOYEE_ID_FILTERS`

Show timesheet employee id filters. Source: https://developers.procore.com/reference/rest/timesheets-filters?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show timesheet location filters

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_TIMESHEET_LOCATION_FILTERS`

Show timesheet location filters. Source: https://developers.procore.com/reference/rest/timesheets-filters?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show timesheet office filters

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_TIMESHEET_OFFICE_FILTERS`

Show timesheet office filters. Source: https://developers.procore.com/reference/rest/timesheets-filters?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show timesheet project filters

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_TIMESHEET_PROJECT_FILTERS`

Show timesheet project filters. Source: https://developers.procore.com/reference/rest/timesheets-filters?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show timesheet region filters

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_TIMESHEET_REGION_FILTERS`

Show timesheet region filters. Source: https://developers.procore.com/reference/rest/timesheets-filters?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show timesheet sub job filters

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_TIMESHEET_SUB_JOB_FILTERS`

Show timesheet sub job filters. Source: https://developers.procore.com/reference/rest/timesheets-filters?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show timesheet time type filters

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_TIMESHEET_TIME_TYPE_FILTERS`

Show timesheet time type filters. Source: https://developers.procore.com/reference/rest/timesheets-filters?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show timesheet to budget configuration

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_TIMESHEET_TO_BUDGET_CONFIGURATION`

Show timesheet to budget configuration. Source: https://developers.procore.com/reference/rest/timesheet-to-budget-configuration?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show timesheet wbs code filters

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_TIMESHEET_WBS_CODE_FILTERS`

Show timesheet wbs code filters. Source: https://developers.procore.com/reference/rest/timesheets-filters?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show timesheet work classification filters

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_TIMESHEET_WORK_CLASSIFICAT_30DE4EAC`

Show timesheet work classification filters. Source: https://developers.procore.com/reference/rest/timesheets-filters?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show todo

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_TODO`

Deprecated. Show todo. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/todos?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | ID of the todo |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get total workers and man hours

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_TOTAL_WORKERS_AND_MAN_HOURS`

Get total workers and man hours. Source: https://developers.procore.com/reference/rest/manpower-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `end_date` | string | No | End date of specific logs desired in YYYY-MM-DD format (use together with start_date) |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `start_date` | string | No | Start date of specific logs desired in YYYY-MM-DD format (use together with end_date) |
| `filters_created_by_id` | array | No | Returns item(s) created by the specified User IDs. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show Visitor Logs

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_VISITOR_LOGS`

Show Visitor Logs. Source: https://developers.procore.com/reference/rest/visitor-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Visitor Log ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show Waste Logs

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_WASTE_LOGS`

Show Waste Logs. Source: https://developers.procore.com/reference/rest/waste-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Waste Log ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show Weather Log

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_WEATHER_LOG`

Show Weather Log. Source: https://developers.procore.com/reference/rest/weather-logs?version=1.1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Weather Log ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show Weather Logs

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_WEATHER_LOGS`

Deprecated. Show Weather Logs. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/weather-logs?version=1.1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Use log date as your ID. Format YYYYMMDD ie:20161108 |
| `log_date` | string | No | Log date of specific log desired in YYYY-MM-DD format (This will override ID as log Date) |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show Work Logs

**Slug:** `PROCORE_FIELD_OPERATIONS_GET_WORK_LOGS`

Show Work Logs. Source: https://developers.procore.com/reference/rest/work-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Work Log ID |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Initiate schedule import

**Slug:** `PROCORE_FIELD_OPERATIONS_INITIATE_SCHEDULE_IMPORT`

Initiate schedule import. Source: https://developers.procore.com/reference/rest/schedule-import?version=2.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | string | No | Structured request body matching the documented Procore schema. |
| `file` | object | Yes | Schedule file to import. Supported formats: .mpp, .ppx, .xer. |
| `locale` | string | No | Optional. Locale for the import report (e.g. en, fr-FR, ja-JP). Determines the language of validation errors and warnings in the generated report. Must be the same locale used when fetching logs via the logs endpoint. |
| `company_id` | string | Yes | Unique identifier for the company |
| `project_id` | string | Yes | Unique identifier for the project |
| `schedule_id` | string | Yes | Unique identifier for the schedule |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Accepted Weather Conditions

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_ACCEPTED_WEATHER_CONDITIO_473161B8`

List Accepted Weather Conditions. Source: https://developers.procore.com/reference/rest/weather-conditions?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Accepted Weather Conditions

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_ACCEPTED_WEATHER_CONDITIO_99B808D4`

Deprecated. List Accepted Weather Conditions. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/weather-logs?version=1.1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Accident Logs

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_ACCIDENT_LOGS`

List Accident Logs. Source: https://developers.procore.com/reference/rest/accident-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `end_date` | string | No | End date of specific logs desired in YYYY-MM-DD format (use together with start_date) |
| `log_date` | string | No | Date of specific logs desired in YYYY-MM-DD format |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `start_date` | string | No | Start date of specific logs desired in YYYY-MM-DD format (use together with end_date) |
| `next_cursor` | string | No | Continuation cursor from the previous page. |
| `filters_location_id` | array | No | Return item(s) with the specified Location IDs. |
| `filters_created_by_id` | integer | No | Return item(s) created by the specified User ID |
| `filters_daily_log_segment_id` | array | No | Daily Log Segment ID filter |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Activities

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_ACTIVITIES`

List Activities. Source: https://developers.procore.com/reference/rest/activities?version=2.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | The page number to retrieve |
| `sort` | string ("activity_id" | "activity_name" | "start_date" | "finish_date" | "percent_complete" | "parent_id" | "ordered_parent_index" | "deadline_date" | "created_at" | "last_modified_at" | "starts_at" | "finishes_at") | No | Sort by supported fields. Accepts comma separated values to sort by multiple fields. Order is ascending by default, prefix field with '-' for descending |
| `per_page` | integer | No | Number of records per page |
| `company_id` | string | Yes | Unique identifier for the company |
| `project_id` | string | Yes | Unique identifier for the project |
| `next_cursor` | string | No | Continuation cursor from the previous page. |
| `schedule_id` | string | Yes | Unique identifier for the schedule |
| `filters_activity_id` | string | No | Filter activities by activity_id |
| `filters_is_critical` | boolean | No | Filter activities by critical path status in read only project schedule |
| `filters_activity_name` | string | No | Filter activities by name |
| `filters_updated_at_gt` | string | No | Filter for activities updated after this timestamp (ISO 8601) |
| `filters_start_date_gte` | string | No | Filter activities with start date on or after this date (inclusive, ISO 8601 date YYYY-MM-DD in project-local time) |
| `filters_start_date_lte` | string | No | Filter activities with start date on or before this date (inclusive, ISO 8601 date YYYY-MM-DD in project-local time) |
| `filters_finish_date_gte` | string | No | Filter activities with finish date on or after this date (inclusive, ISO 8601 date YYYY-MM-DD in project-local time) |
| `filters_finish_date_lte` | string | No | Filter activities with finish date on or before this date (inclusive, ISO 8601 date YYYY-MM-DD in project-local time) |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Activity Links

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_ACTIVITY_LINKS`

List Activity Links. Source: https://developers.procore.com/reference/rest/activity-links?version=2.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | The page number to retrieve |
| `sort` | string ("id" | "from_activity" | "to_activity" | "updated_at") | No | Sort by supported fields. Accepts comma separated values to sort by multiple fields. Order is ascending by default, prefix field with '-' for descending |
| `per_page` | integer | No | Number of records per page |
| `company_id` | string | Yes | Unique identifier for the company |
| `filters_id` | string | No | Filter activity links by ID |
| `project_id` | string | Yes | Unique identifier for the project |
| `next_cursor` | string | No | Continuation cursor from the previous page. |
| `schedule_id` | string | Yes | Unique identifier for the schedule |
| `filters_to_activity` | string | No | Filter activity links by successor activity IDs (bracket list syntax like [1,2]) |
| `filters_from_activity` | string | No | Filter activity links by predecessor activity IDs (bracket list syntax like [1,2]) |
| `filters_updated_at_gt` | string | No | Filter for activity links updated after this timestamp (ISO 8601) |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List all Actual Production Quantities

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_ALL_ACTUAL_PRODUCTION_QUANTITIES`

List all Actual Production Quantities. Source: https://developers.procore.com/reference/rest/actual-production-quantities?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `filters_id` | array | No | Return item(s) with the specified IDs. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `next_cursor` | string | No | Continuation cursor from the previous page. |
| `filters_date` | string | No | Returns item(s) within the specified ISO 8601 datetime range. |
| `filters_crew_id` | string | No | Crew ID. Returns item(s) with the specified Crew ID. |
| `filters_updated_at` | string | No | Return item(s) last updated within the specified ISO 8601 datetime range. Formats: `YYYY-MM-DD`...`YYYY-MM-DD` - Date `YYYY-MM-DDTHH:MM:SSZ`...`YYYY-MM-DDTHH:MM:SSZ` - DateTime with UTC Offset `YYYY-MM-DDTHH:MM:SS+XX:00`...`YYYY-MM-DDTHH:MM:SS+XX:00` - Datetime with Custom Offset |
| `filters_location_id` | array | No | Location ID. Returns item(s) with the specified Location ID or a range of Location IDs. |
| `filters_timesheet_id` | string | No | Timesheet ID. Returns item(s) with the specified Timesheet ID. |
| `filters_approval_status` | string ("pending" | "approved" | "rejected" | "locked") | No | Return Actual Production Quantities with the specified approval status. |
| `filters_unit_of_measure` | string | No | Return item(s) with the specified unit of measure. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List all Company Managed Equipment User Permissions

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_ALL_COMPANY_MANAGED_EQUIP_9638F74D`

Deprecated. List all Company Managed Equipment User Permissions. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/managed-equipment---company-level?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique identifier for the company. |
| `next_cursor` | string | No | Continuation cursor from the previous page. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List all equipment categories

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_ALL_EQUIPMENT_CATEGORIES`

Deprecated. List all equipment categories. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/equipment-category?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique identifier for the company. |
| `next_cursor` | string | No | Continuation cursor from the previous page. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List all equipment logs

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_ALL_EQUIPMENT_LOGS`

Deprecated. List all equipment logs. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/equipment-log?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique identifier for the company. |
| `next_cursor` | string | No | Continuation cursor from the previous page. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List all equipment makes

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_ALL_EQUIPMENT_MAKES`

Deprecated. List all equipment makes. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/equipment-make?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique identifier for the company. |
| `next_cursor` | string | No | Continuation cursor from the previous page. |
| `filters_updated_at` | string | No | Return item(s) last updated within the specified ISO 8601 datetime range. Formats: `YYYY-MM-DD`...`YYYY-MM-DD` - Date `YYYY-MM-DDTHH:MM:SSZ`...`YYYY-MM-DDTHH:MM:SSZ` - DateTime with UTC Offset `YYYY-MM-DDTHH:MM:SS+XX:00`...`YYYY-MM-DDTHH:MM:SS+XX:00` - Datetime with Custom Offset |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List all equipment models

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_ALL_EQUIPMENT_MODELS`

Deprecated. List all equipment models. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/equipment-model?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique identifier for the company. |
| `next_cursor` | string | No | Continuation cursor from the previous page. |
| `filters_updated_at` | string | No | Return item(s) last updated within the specified ISO 8601 datetime range. Formats: `YYYY-MM-DD`...`YYYY-MM-DD` - Date `YYYY-MM-DDTHH:MM:SSZ`...`YYYY-MM-DDTHH:MM:SSZ` - DateTime with UTC Offset `YYYY-MM-DDTHH:MM:SS+XX:00`...`YYYY-MM-DDTHH:MM:SS+XX:00` - Datetime with Custom Offset |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List all equipment types

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_ALL_EQUIPMENT_TYPES`

Deprecated. List all equipment types. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/equipment-type?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique identifier for the company. |
| `next_cursor` | string | No | Continuation cursor from the previous page. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List all maintenance logs attachment

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_ALL_MAINTENANCE_LOGS_ATTACHMENT`

Deprecated. List all maintenance logs attachment. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/company-managed-equipment-maintenance-log-attachment?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Identifier of the managed equipment maintenance log. |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List all Time And Material Entry Configurable Field Sets

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_ALL_TIME_AND_MATERIAL_ENT_21415889`

List all Time And Material Entry Configurable Field Sets. Source: https://developers.procore.com/reference/rest/time-and-material-entry?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `next_cursor` | string | No | Continuation cursor from the previous page. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List all Time And Material Entry matching the search keyword

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_ALL_TIME_AND_MATERIAL_ENT_A27EA05B`

List all Time And Material Entry matching the search keyword. Source: https://developers.procore.com/reference/rest/time-and-material-entry?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `search_keyword` | string | No | Keyword for looking up Time And Material Entries |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List all Time And Material Entry

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_ALL_TIME_AND_MATERIAL_ENTRY`

List all Time And Material Entry. Source: https://developers.procore.com/reference/rest/time-and-material-entry?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `next_cursor` | string | No | Continuation cursor from the previous page. |
| `filters_status` | array | No | Restricts results to entries whose status matches any of the supplied stringified integer values (`0` in_progress, `1` ready_for_review, `2` field_verified, `3` closed, `4` revise_and_resubmit, `5` rejected). Must be sent as an array (`filters[status][]=<value>`). A non-array value returns 422; a value outside the enum returns 422 with the invalid entries and the full valid set in the error body. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List all Timesheets

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_ALL_TIMESHEETS`

List all Timesheets. Source: https://developers.procore.com/reference/rest/timesheets?version=1.1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `next_cursor` | string | No | Continuation cursor from the previous page. |
| `filters_date` | string | No | Returns item(s) within the specified ISO 8601 datetime range. |
| `filters_deleted_at` | string | No | Returns item(s) deleted within the specified ISO 8601 datetime range. |
| `filters_updated_at` | string | No | Return item(s) last updated within the specified ISO 8601 datetime range. Formats: `YYYY-MM-DD`...`YYYY-MM-DD` - Date `YYYY-MM-DDTHH:MM:SSZ`...`YYYY-MM-DDTHH:MM:SSZ` - DateTime with UTC Offset `YYYY-MM-DDTHH:MM:SS+XX:00`...`YYYY-MM-DDTHH:MM:SS+XX:00` - Datetime with Custom Offset |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List all attachments

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_ATTACHMENTS_PROJECT_TIME_AB7FE9BA`

List all attachments. Source: https://developers.procore.com/reference/rest/time-and-material-attachment?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `time_and_material_entry_id` | integer | Yes | Time and material entry ID. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List calendar events

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_CALENDAR_EVENTS`

Deprecated. List calendar events. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/calendar-events?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `next_cursor` | string | No | Continuation cursor from the previous page. |
| `calendar_start_datetime` | string | No | Start date or date-time |
| `calendar_finish_datetime` | string | No | Finish date or date-time |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Calendar Items

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_CALENDAR_ITEMS`

List Calendar Items. Source: https://developers.procore.com/reference/rest/calendar-items?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `sort` | string ("id" | "name" | "start_date" | "finish_date" | "percent") | No | Return item(s) with the specified sort.  Prepend "-" to specify descending order. |
| `view` | string ("ids_only" | "total_count_only") | No | The view to use when serializing Calendar Item data. The ids_only view returns an array of Calendar Item IDs. The total_count_only view returns total count of Calendar Items. |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `start_date` | string | No | Calendar Items that occur after this date |
| `finish_date` | string | No | Calendar Items that occur before this date |
| `next_cursor` | string | No | Continuation cursor from the previous page. |
| `filters_date` | string | No | Returns task(s) existing on the specified ISO 8601 datetime |
| `filters_query` | string | No | Return item(s) containing search query |
| `filters_updated_at` | string | No | Return item(s) last updated within the specified ISO 8601 datetime range. Formats: `YYYY-MM-DD`...`YYYY-MM-DD` - Date `YYYY-MM-DDTHH:MM:SSZ`...`YYYY-MM-DDTHH:MM:SSZ` - DateTime with UTC Offset `YYYY-MM-DDTHH:MM:SS+XX:00`...`YYYY-MM-DDTHH:MM:SS+XX:00` - Datetime with Custom Offset |
| `filters_assigned_id` | array | No | Returns task(s) with specified assignee(s) |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Calendars (V2.1)

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_CALENDARS_V2_1`

List Calendars (V2.1). Source: https://developers.procore.com/reference/rest/calendars?version=2.1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | The page number to retrieve |
| `sort` | string ("calendar_id" | "name" | "is_global") | No | Sort by supported fields. Accepts comma separated values to sort by multiple fields. Order is ascending by default, prefix field with '-' for descending |
| `per_page` | integer | No | Number of records per page |
| `company_id` | string | Yes | Unique identifier for the company |
| `project_id` | string | Yes | Unique identifier for the project |
| `next_cursor` | string | No | Continuation cursor from the previous page. |
| `filters_name` | string | No | Filter calendars by name |
| `filters_is_global` | boolean | No | Filter calendars by global status |
| `filters_calendar_id` | string | No | Filter calendars by calendar_id |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Call Logs

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_CALL_LOGS`

List Call Logs. Source: https://developers.procore.com/reference/rest/call-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `end_date` | string | No | End date of specific logs desired in YYYY-MM-DD format (use together with start_date) |
| `log_date` | string | No | Date of specific logs desired in YYYY-MM-DD format |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `start_date` | string | No | Start date of specific logs desired in YYYY-MM-DD format (use together with end_date) |
| `next_cursor` | string | No | Continuation cursor from the previous page. |
| `filters_created_by_id` | integer | No | Return item(s) created by the specified User ID |
| `filters_daily_log_segment_id` | array | No | Daily Log Segment ID filter |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Change History for Timesheet

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_CHANGE_HISTORY_FOR_TIMESHEET`

List Change History for Timesheet. Source: https://developers.procore.com/reference/rest/timesheets?version=1.1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Cost Codes for Timesheets

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_COST_CODES_FOR_TIMESHEETS`

List Cost Codes for Timesheets. Source: https://developers.procore.com/reference/rest/timesheets?version=1.1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `sub_job_id` | integer | No | Sub Job ID |
| `next_cursor` | string | No | Continuation cursor from the previous page. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Cost Codes Ids for Timesheets

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_COST_CODES_IDS_FOR_TIMESHEETS`

List Cost Codes Ids for Timesheets. Source: https://developers.procore.com/reference/rest/timesheets?version=1.1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `sub_job_id` | integer | No | Sub Job ID |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Counts of Daily Logs

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_COUNTS_OF_DAILY_LOGS_DAIL_42729DC6`

Deprecated. List Counts of Daily Logs. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/daily-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `end_date` | string | No | End date of specific logs desired in YYYY-MM-DD format (use together with start_date) |
| `log_date` | string | No | Date of specific logs desired in YYYY-MM-DD format |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `start_date` | string | No | Start date of specific logs desired in YYYY-MM-DD format (use together with end_date) |
| `filters_status` | string | No | Filter on status for "pending" or "approved" or "all" |
| `filters_created_by_id` | array | No | Returns item(s) created by the specified User IDs. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Counts of Daily Logs

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_COUNTS_OF_DAILY_LOGS_DAIL_947B0AC1`

List Counts of Daily Logs. Source: https://developers.procore.com/reference/rest/daily-log-counts?version=1.1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `end_date` | string | No | End date of specific logs desired. Use together with start_date to specify a date range. Example formats YYYY-MM-DD, YYYY/MM/DD, DD-MM-YYYY, DD/MM/YYYY |
| `log_date` | string | No | Date of specific logs desired. Example formats YYYY-MM-DD, YYYY/MM/DD, DD-MM-YYYY, DD/MM/YYYY |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `start_date` | string | No | Start date of specific logs desired. Use together with end_date to specify a date range. Example formats YYYY-MM-DD, YYYY/MM/DD, DD-MM-YYYY, DD/MM/YYYY |
| `next_cursor` | string | No | Continuation cursor from the previous page. |
| `filters_status` | string ("all" | "approved" | "pending") | No | Filter on log status |
| `filters_created_by_id` | array | No | Returns item(s) created by the specified User IDs. |
| `filters_daily_log_segment_id` | array | No | Daily Log Segment ID filter |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Daily Construction Report Logs Vendor Options

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_DAILY_CONSTRUCTION_REPORT_9028267F`

List Daily Construction Report Logs Vendor Options. Source: https://developers.procore.com/reference/rest/daily-construction-report-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Daily Construction Report Logs

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_DAILY_CONSTRUCTION_REPORT_LOGS`

List Daily Construction Report Logs. Source: https://developers.procore.com/reference/rest/daily-construction-report-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `end_date` | string | No | End date of specific logs desired in YYYY-MM-DD format (use together with start_date) |
| `log_date` | string | No | Date of specific logs desired in YYYY-MM-DD format |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `start_date` | string | No | Start date of specific logs desired in YYYY-MM-DD format (use together with end_date) |
| `next_cursor` | string | No | Continuation cursor from the previous page. |
| `filters_status` | string | No | Filter on status for "pending" or "approved" or "all" |
| `filters_created_by_id` | integer | No | Return item(s) created by the specified User ID |
| `filters_daily_log_segment_id` | array | No | Daily Log Segment ID filter |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Delay Logs

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_DELAY_LOGS`

List Delay Logs. Source: https://developers.procore.com/reference/rest/delay-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `end_date` | string | No | End date of specific logs desired in YYYY-MM-DD format (use together with start_date) |
| `log_date` | string | No | Date of specific logs desired in YYYY-MM-DD format |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `start_date` | string | No | Start date of specific logs desired in YYYY-MM-DD format (use together with end_date) |
| `next_cursor` | string | No | Continuation cursor from the previous page. |
| `filters_location_id` | array | No | Return item(s) with the specified Location IDs. |
| `filters_created_by_id` | array | No | Returns item(s) created by the specified User IDs. |
| `filters_daily_log_segment_id` | array | No | Daily Log Segment ID filter |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Delay Log Types

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_DELAY_LOG_TYPES`

List Delay Log Types. Source: https://developers.procore.com/reference/rest/delay-log-types?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `next_cursor` | string | No | Continuation cursor from the previous page. |
| `filters_visible` | string ("true" | "false" | "false...true") | No | Filter Delay Log Types based on visible. Defaults to true, to query all types pass 'false...true' |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Delivery Logs

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_DELIVERY_LOGS`

List Delivery Logs. Source: https://developers.procore.com/reference/rest/delivery-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `end_date` | string | No | End date of specific logs desired in YYYY-MM-DD format (use together with start_date) |
| `log_date` | string | No | Date of specific logs desired in YYYY-MM-DD format |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `start_date` | string | No | Start date of specific logs desired in YYYY-MM-DD format (use together with end_date) |
| `next_cursor` | string | No | Continuation cursor from the previous page. |
| `filters_status` | string | No | Filter on status for "pending" or "approved" or "all" |
| `filters_created_by_id` | array | No | Returns item(s) created by the specified User IDs. |
| `filters_daily_log_segment_id` | array | No | Daily Log Segment ID filter |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Dumpster Logs

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_DUMPSTER_LOGS`

List Dumpster Logs. Source: https://developers.procore.com/reference/rest/dumpster-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `end_date` | string | No | End date of specific logs desired in YYYY-MM-DD format (use together with start_date) |
| `log_date` | string | No | Date of specific logs desired in YYYY-MM-DD format |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `start_date` | string | No | Start date of specific logs desired in YYYY-MM-DD format (use together with end_date) |
| `next_cursor` | string | No | Continuation cursor from the previous page. |
| `filters_vendor_id` | array | No | Return item(s) with the specified Vendor IDs. |
| `filters_created_by_id` | array | No | Returns item(s) created by the specified User IDs. |
| `filters_daily_log_segment_id` | array | No | Daily Log Segment ID filter |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List all Equipment

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_EQUIPMENT_COMPANY_MANAGED_5C0AEAB6`

Deprecated. List all Equipment. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/managed-equipment---company-level?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique identifier for the company. |
| `next_cursor` | string | No | Continuation cursor from the previous page. |
| `filters_year` | integer | No | Return item(s) with the specified year. |
| `filters_status` | array | No | Returns item(s) matching the specified status value. |
| `filters_updated_at` | string | No | Return item(s) last updated within the specified ISO 8601 datetime range. Formats: `YYYY-MM-DD`...`YYYY-MM-DD` - Date `YYYY-MM-DDTHH:MM:SSZ`...`YYYY-MM-DDTHH:MM:SSZ` - DateTime with UTC Offset `YYYY-MM-DDTHH:MM:SS+XX:00`...`YYYY-MM-DDTHH:MM:SS+XX:00` - Datetime with Custom Offset |
| `filters_company_visible` | boolean | No | If true, return item(s) with 'company visible' status. |
| `filters_last_service_date` | string | No | Return item(s) with a last service date within the specified ISO 8601 datetime range. |
| `filters_next_service_date` | string | No | Return item(s) with a next service date within the specified ISO 8601 datetime range. |
| `filters_current_project_id` | integer | No | Return item(s) with the specified current project ID. |
| `filters_managed_equipment_id` | integer | No | Return item(s) with the specified Managed Equipment ID. |
| `filters_managed_equipment_make_id` | integer | No | Return item(s) with the specified Managed Equipment Make ID. |
| `filters_managed_equipment_type_id` | integer | No | Return item(s) with the specified Managed Equipment Type ID. |
| `filters_managed_equipment_model_id` | integer | No | Return item(s) with the specified Managed Equipment Model ID. |
| `filters_managed_equipment_category_id` | integer | No | Return item(s) with the specified Managed Equipment Category ID. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Equipment Logs

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_EQUIPMENT_LOGS`

List Equipment Logs. Source: https://developers.procore.com/reference/rest/admin-equipment-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `end_date` | string | No | End date of specific logs desired in YYYY-MM-DD format (use together with start_date) |
| `log_date` | string | No | Date of specific logs desired in YYYY-MM-DD format |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `start_date` | string | No | Start date of specific logs desired in YYYY-MM-DD format (use together with end_date) |
| `next_cursor` | string | No | Continuation cursor from the previous page. |
| `filters_location_id` | integer | No | Return item(s) with the specified Location ID. |
| `filters_created_by_id` | integer | No | Return item(s) created by the specified User ID |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Equipment Maintenance Logs

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_EQUIPMENT_MAINTENANCE_LOGS`

Deprecated. List Equipment Maintenance Logs. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/equipment-maintenance-log?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique identifier for the company. |
| `next_cursor` | string | No | Continuation cursor from the previous page. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List all equipment

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_EQUIPMENT_PROJECT_MANAGED_422F804D`

Deprecated. List all equipment. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/managed-equipment---project-level?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `next_cursor` | string | No | Continuation cursor from the previous page. |
| `filters_year` | integer | No | Return item(s) with the specified year. |
| `filters_onsite` | array | No | Onsite Dates. Returns item(s) with the specified range of onsite dates. |
| `filters_status` | array | No | Returns item(s) matching the specified status value. |
| `filters_offsite` | array | No | Offsite Dates. Returns item(s) with the specified range of offsite dates. |
| `filters_ownership` | string ("Owned" | "Rented" | "Sub") | No | Returns only item(s) with the specified ownership value. Must be one of Owned, Rented, or Sub. |
| `filters_vendor_id` | integer | No | Return item(s) with the specified Vendor ID. |
| `filters_updated_at` | string | No | Return item(s) last updated within the specified ISO 8601 datetime range. Formats: `YYYY-MM-DD`...`YYYY-MM-DD` - Date `YYYY-MM-DDTHH:MM:SSZ`...`YYYY-MM-DDTHH:MM:SSZ` - DateTime with UTC Offset `YYYY-MM-DDTHH:MM:SS+XX:00`...`YYYY-MM-DDTHH:MM:SS+XX:00` - Datetime with Custom Offset |
| `filters_company_visible` | boolean | No | If true, return item(s) with 'company visible' status. |
| `filters_induction_status` | boolean | No | Returns item(s) with the specified inudction status. |
| `filters_last_service_date` | string | No | Return item(s) with a last service date within the specified ISO 8601 datetime range. |
| `filters_next_service_date` | string | No | Return item(s) with a next service date within the specified ISO 8601 datetime range. |
| `filters_current_project_id` | integer | No | Return item(s) with the specified current project ID. |
| `filters_managed_equipment_id` | integer | No | Return item(s) with the specified Managed Equipment ID. |
| `filters_managed_equipment_make_id` | integer | No | Return item(s) with the specified Managed Equipment Make ID. |
| `filters_managed_equipment_type_id` | integer | No | Return item(s) with the specified Managed Equipment Type ID. |
| `filters_managed_equipment_model_id` | integer | No | Return item(s) with the specified Managed Equipment Model ID. |
| `filters_managed_equipment_category_id` | integer | No | Return item(s) with the specified Managed Equipment Category ID. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List equipment timecard entries (Project)

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_EQUIPMENT_TIMECARD_ENTRIES_PROJECT`

Beta. List equipment timecard entries (Project). This Procore endpoint is beta and its contract may change. Source: https://developers.procore.com/reference/rest/equipment-timecard-entries?version=2.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `end_date` | string | No | The end of the date range for equipment timecard entries. (YYYY-MM-DD) End date is inclusive. |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique identifier for the company. |
| `filters_id` | array | No | Return item(s) with the specified IDs |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `start_date` | string | No | The beginning of the date range for equipment timecard entries. (YYYY-MM-DD) Start date is inclusive. |
| `next_cursor` | string | No | Continuation cursor from the previous page. |
| `serializer_view` | string ("default" | "compact" | "mobile" | "extended_costs") | No | Optional response blueprint view. Defaults to `compact`. `extended_costs` adds `cost` and `currency_iso_code` to the default payload when the caller can view timecard entry costs. Those keys are omitted when the caller cannot, or when Cost Calculator cannot be read. An unknown value is rejected.  |
| `filters_party_id` | array | No | Return item(s) matching the specified party ID(s). |
| `filters_created_at` | string | No | Return item(s) created within the specified ISO 8601 datetime range. Formats: `YYYY-MM-DD`...`YYYY-MM-DD` - Date `YYYY-MM-DDTHH:MM:SSZ`...`YYYY-MM-DDTHH:MM:SSZ` - DateTime with UTC Offset |
| `filters_updated_at` | string | No | Return item(s) last updated within the specified ISO 8601 datetime range. Formats: `YYYY-MM-DD`...`YYYY-MM-DD` - Date `YYYY-MM-DDTHH:MM:SSZ`...`YYYY-MM-DDTHH:MM:SSZ` - DateTime with UTC Offset |
| `filters_wbs_code_id` | array | No | Return item(s) matching the specified WBS code ID(s). |
| `filters_equipment_id` | array | No | Return item(s) matching the specified equipment identifier(s). |
| `filters_timesheet_id` | array | No | Return item(s) matching the specified timesheet ID(s). |
| `filters_timesheet_group_id` | array | No | Return item(s) belonging to the specified TimesheetGroup(s). |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Gps Positions

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_GPS_POSITIONS`

List Gps Positions. Source: https://developers.procore.com/reference/rest/gps-positions?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique identifier for the company. |
| `filters_id` | array | No | Return item(s) with the specified IDs. |
| `next_cursor` | string | No | Continuation cursor from the previous page. |
| `filters_updated_at` | string | No | Return item(s) last updated within the specified ISO 8601 datetime range. Formats: `YYYY-MM-DD`...`YYYY-MM-DD` - Date `YYYY-MM-DDTHH:MM:SSZ`...`YYYY-MM-DDTHH:MM:SSZ` - DateTime with UTC Offset `YYYY-MM-DDTHH:MM:SS+XX:00`...`YYYY-MM-DDTHH:MM:SS+XX:00` - Datetime with Custom Offset |
| `filters_created_by_id` | array | No | Returns item(s) created by the specified User IDs. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Inspection Logs

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_INSPECTION_LOGS`

List Inspection Logs. Source: https://developers.procore.com/reference/rest/inspection-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `end_date` | string | No | End date of specific logs desired in YYYY-MM-DD format (use together with start_date) |
| `log_date` | string | No | Date of specific logs desired in YYYY-MM-DD format |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `start_date` | string | No | Start date of specific logs desired in YYYY-MM-DD format (use together with end_date) |
| `next_cursor` | string | No | Continuation cursor from the previous page. |
| `filters_location_id` | array | No | Return item(s) with the specified Location IDs. |
| `filters_created_by_id` | array | No | Returns item(s) created by the specified User IDs. |
| `filters_daily_log_segment_id` | array | No | Daily Log Segment ID filter |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Instructions on a project

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_INSTRUCTIONS_ON_PROJECT`

List Instructions on a project. Source: https://developers.procore.com/reference/rest/instructions?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `next_cursor` | string | No | Continuation cursor from the previous page. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Instruction Types on a project

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_INSTRUCTION_TYPES_ON_PROJECT`

List Instruction Types on a project. Source: https://developers.procore.com/reference/rest/instruction-types?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `next_cursor` | string | No | Continuation cursor from the previous page. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Lookaheads

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_LOOKAHEADS`

List Lookaheads. Source: https://developers.procore.com/reference/rest/lookaheads?version=1.1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Lookaheads

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_LOOKAHEADS_V1_0`

List Lookaheads. Source: https://developers.procore.com/api/v1/resource_groups/full_oas?version=1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Manpower Logs

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_MANPOWER_LOGS`

List Manpower Logs. Source: https://developers.procore.com/reference/rest/manpower-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `end_date` | string | No | End date of specific logs desired in YYYY-MM-DD format (use together with start_date) |
| `log_date` | string | No | Date of specific logs desired in YYYY-MM-DD format |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `start_date` | string | No | Start date of specific logs desired in YYYY-MM-DD format (use together with end_date) |
| `next_cursor` | string | No | Continuation cursor from the previous page. |
| `filters_search` | string | No | Returns item(s) matching the specified search query string. |
| `filters_status` | string | No | Filter on status for "pending" or "approved" or "all" |
| `filters_vendor_id` | array | No | Return item(s) with the specified Vendor IDs. |
| `filters_location_id` | array | No | Return item(s) with the specified Location IDs. |
| `filters_created_by_id` | array | No | Returns item(s) created by the specified User IDs. |
| `filters_daily_log_segment_id` | array | No | Daily Log Segment ID filter |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Manpower Logs Contact Options

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_MANPOWER_LOGS_CONTACT_OPTIONS`

List Manpower Logs Contact Options. Source: https://developers.procore.com/reference/rest/manpower-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `next_cursor` | string | No | Continuation cursor from the previous page. |
| `filters_is_employee` | boolean | No | If provided, filters contacts by their is_employee status. When 'true', only return contacts that are employees. When 'false', only return contacts that are not employees. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Manpower Logs Vendor Options

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_MANPOWER_LOGS_VENDOR_OPTIONS`

List Manpower Logs Vendor Options. Source: https://developers.procore.com/reference/rest/manpower-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `next_cursor` | string | No | Continuation cursor from the previous page. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Materials

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_MATERIALS`

List Materials. Source: https://developers.procore.com/reference/rest/material?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `next_cursor` | string | No | Continuation cursor from the previous page. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Notes Logs

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_NOTES_LOGS`

List Notes Logs. Source: https://developers.procore.com/reference/rest/notes-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `end_date` | string | No | End date of specific logs desired in YYYY-MM-DD format (use together with start_date) |
| `log_date` | string | No | Date of specific logs desired in YYYY-MM-DD format |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `start_date` | string | No | Start date of specific logs desired in YYYY-MM-DD format (use together with end_date) |
| `next_cursor` | string | No | Continuation cursor from the previous page. |
| `filters_status` | string | No | Filter on status for "pending" or "approved" or "all" |
| `filters_location_id` | integer | No | Filters by specific location (Note: Use *either* this or location_id_with_sublocations, but not both) |
| `filters_created_by_id` | integer | No | Return item(s) created by the specified User ID |
| `filters_daily_log_segment_id` | array | No | Daily Log Segment ID filter |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List of Actual Production Quantity Ids

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_OF_ACTUAL_PRODUCTION_QUANTITY_IDS`

List of Actual Production Quantity Ids. Source: https://developers.procore.com/reference/rest/actual-production-quantities?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `next_cursor` | string | No | Continuation cursor from the previous page. |
| `filters_date` | string | No | Returns item(s) within the specified ISO 8601 datetime range. |
| `filters_crew_id` | string | No | Crew ID. Returns item(s) with the specified Crew ID. |
| `filters_updated_at` | string | No | Return item(s) last updated within the specified ISO 8601 datetime range. Formats: `YYYY-MM-DD`...`YYYY-MM-DD` - Date `YYYY-MM-DDTHH:MM:SSZ`...`YYYY-MM-DDTHH:MM:SSZ` - DateTime with UTC Offset `YYYY-MM-DDTHH:MM:SS+XX:00`...`YYYY-MM-DDTHH:MM:SS+XX:00` - Datetime with Custom Offset |
| `filters_location_id` | array | No | Location ID. Returns item(s) with the specified Location ID or a range of Location IDs. |
| `filters_timesheet_id` | string | No | Timesheet ID. Returns item(s) with the specified Timesheet ID. |
| `filters_approval_status` | string ("pending" | "approved" | "rejected" | "locked") | No | Return Actual Production Quantities with the specified approval status. |
| `filters_unit_of_measure` | string | No | Return item(s) with the specified unit of measure. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List of all Time and Material Equipment Logs

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_OF_ALL_TIME_AND_MATERIAL_C7E78514`

List of all Time and Material Equipment Logs. Source: https://developers.procore.com/reference/rest/time-and-material-equipment-log?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `next_cursor` | string | No | Continuation cursor from the previous page. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Plan Revision Logs

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_PLAN_REVISION_LOGS`

List Plan Revision Logs. Source: https://developers.procore.com/reference/rest/plan-revision-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `end_date` | string | No | End date of specific logs desired in YYYY-MM-DD format (use together with start_date) |
| `log_date` | string | No | Date of specific logs desired in YYYY-MM-DD format |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `start_date` | string | No | Start date of specific logs desired in YYYY-MM-DD format (use together with end_date) |
| `filters_created_by_id` | array | No | Returns item(s) created by the specified User IDs. |
| `filters_daily_log_segment_id` | array | No | Daily Log Segment ID filter |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Productivity Logs

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_PRODUCTIVITY_LOGS`

List Productivity Logs. Source: https://developers.procore.com/reference/rest/productivity-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `end_date` | string | No | End date of specific logs desired in YYYY-MM-DD format (use together with start_date) |
| `log_date` | string | No | Date of specific logs desired in YYYY-MM-DD format |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `start_date` | string | No | Start date of specific logs desired in YYYY-MM-DD format (use together with end_date) |
| `next_cursor` | string | No | Continuation cursor from the previous page. |
| `filters_created_by_id` | array | No | Returns item(s) created by the specified User IDs. |
| `filters_daily_log_segment_id` | array | No | Daily Log Segment ID filter |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Project Equipment Logs

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_PROJECT_EQUIPMENT_LOGS`

Deprecated. List Project Equipment Logs. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/equipment-log?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `next_cursor` | string | No | Continuation cursor from the previous page. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Project Equipment Maintenance Logs

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_PROJECT_EQUIPMENT_MAINTENANCE_LOGS`

Deprecated. List Project Equipment Maintenance Logs. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/equipment-maintenance-log?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `next_cursor` | string | No | Continuation cursor from the previous page. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Project WBS Task codes

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_PROJECT_WBS_TASK_CODES`

Beta. List Project WBS Task codes. This Procore endpoint is beta and its contract may change. Source: https://developers.procore.com/reference/rest/task-codes-field-productivity?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `type` | string ("labor (default)" | "equipment" | "all (returns both labor and equipment task codes in a single request)") | No | Type of task codes to return |
| `view` | string | No | Selects the response blueprint. Defaults to `task_code_entity` (full detail); `id_only` returns only identifiers. Ignored when `serializer_view` is also provided. |
| `filters` | string | No | Filter criteria for WBS task codes. |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `next_cursor` | string | No | Continuation cursor from the previous page. |
| `serializer_view` | string | No | Selects the response blueprint. Defaults to `task_code_entity` (full detail); `id_only` returns only identifiers. Takes precedence over the `view` parameter. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Quantity Logs

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_QUANTITY_LOGS`

List Quantity Logs. Source: https://developers.procore.com/reference/rest/quantity-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `end_date` | string | No | End date of specific logs desired in YYYY-MM-DD format (use together with start_date) |
| `log_date` | string | No | Date of specific logs desired in YYYY-MM-DD format |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `start_date` | string | No | Start date of specific logs desired in YYYY-MM-DD format (use together with end_date) |
| `next_cursor` | string | No | Continuation cursor from the previous page. |
| `filters_location_id` | array | No | Return item(s) with the specified Location IDs. |
| `filters_created_by_id` | array | No | Returns item(s) created by the specified User IDs. |
| `filters_daily_log_segment_id` | array | No | Daily Log Segment ID filter |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Requested Changes

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_REQUESTED_CHANGES`

Deprecated. List Requested Changes. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/requested-changes?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `view` | string | No | The `with_task` view includes an additional task data for correspondent requested changes |
| `task_id` | integer | No | The task for which all requested changes will be retrieved. |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `next_cursor` | string | No | Continuation cursor from the previous page. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List requested changes for a Schedule or a Task

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_REQUESTED_CHANGES_FOR_SCH_4B342F09`

List requested changes for a Schedule or a Task. Source: https://developers.procore.com/reference/rest/task-requested-changes?version=1.1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `view` | string | No | The `with_task` view includes an additional task data for correspondent requested changes |
| `task_id` | integer | No | Task ID |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `next_cursor` | string | No | Continuation cursor from the previous page. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Resources

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_RESOURCES`

List Resources. Source: https://developers.procore.com/reference/rest/schedule-resources?version=1.1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `next_cursor` | string | No | Continuation cursor from the previous page. |
| `filters_query` | string | No | Return item(s) containing search query |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Resources

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_RESOURCES_V1_0`

List Resources. Source: https://developers.procore.com/api/v1/resource_groups/full_oas?version=1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `next_cursor` | string | No | Continuation cursor from the previous page. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Safety Violation Logs

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_SAFETY_VIOLATION_LOGS`

List Safety Violation Logs. Source: https://developers.procore.com/reference/rest/safety-violation-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `end_date` | string | No | End date of specific logs desired in YYYY-MM-DD format (use together with start_date) |
| `log_date` | string | No | Date of specific logs desired in YYYY-MM-DD format |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `start_date` | string | No | Start date of specific logs desired in YYYY-MM-DD format (use together with end_date) |
| `next_cursor` | string | No | Continuation cursor from the previous page. |
| `filters_created_by_id` | array | No | Returns item(s) created by the specified User IDs. |
| `filters_daily_log_segment_id` | array | No | Daily Log Segment ID filter |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Schedule Imports

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_SCHEDULE_IMPORTS`

List Schedule Imports. Source: https://developers.procore.com/reference/rest/schedule-integration?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `next_cursor` | string | No | Continuation cursor from the previous page. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Schedules

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_SCHEDULES`

List Schedules. Source: https://developers.procore.com/reference/rest/schedules?version=2.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | The page number to retrieve |
| `sort` | string ("schedule_id" | "schedule_name" | "schedule_type" | "is_active" | "updated_at") | No | Sort by supported fields. Accepts comma separated values to sort by multiple fields. Order is ascending by default, prefix field with '-' for descending |
| `per_page` | integer | No | Number of records per page |
| `company_id` | string | Yes | Unique identifier for the company |
| `project_id` | string | Yes | Unique identifier for the project |
| `next_cursor` | string | No | Continuation cursor from the previous page. |
| `filters_is_active` | boolean | No | Filter schedules by active status |
| `filters_schedule_id` | string | No | Filter schedules by schedule_id |
| `filters_schedule_name` | string | No | Filter schedules by name |
| `filters_schedule_type` | string ("ONBOARDING" | "READONLY_PROJECT_SCHEDULE" | "LOOKAHEAD" | "READONLY_ONBOARDING" | "IMPORTED_READ_WRITE_ONBOARDING" | "IMPORTED_READ_WRITE_PROJECT_SCHEDULE" | "LOOKAHEAD_ONBOARDING") | No | Filter schedules by type. Values must exactly match a valid schedule type (case-sensitive) |
| `filters_updated_at_gt` | string | No | Filter for schedules updated after this timestamp (ISO 8601 instant) |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Signatures

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_SIGNATURES_TIME_AND_MATER_35DDFB9F`

List Signatures. Source: https://developers.procore.com/reference/rest/time-and-material-signature?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `next_cursor` | string | No | Continuation cursor from the previous page. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Signatures

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_SIGNATURES_TIMESHEETS_V1_1`

List Signatures. Source: https://developers.procore.com/reference/rest/timesheets?version=1.1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `next_cursor` | string | No | Continuation cursor from the previous page. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List tasks

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_TASKS`

List tasks. Source: https://developers.procore.com/reference/rest/tasks?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `view` | string ("compact" | "normal") | No | The compact view contains id, name, key, formatted_name, and task_name. The normal view contains the response shown below. The default view is normal. |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `next_cursor` | string | No | Continuation cursor from the previous page. |
| `filters_query` | string | No | Return item(s) containing search query |
| `filters_row_number` | integer | No | Returns Tasks with a row_number matching the given value. This endpoint supports single values of row_number,  a range of row_numbers (filters[row_number]=4...7) as well as multiple values  (filters[row_number][]=5&filters[row_number][]=6). Exclude the filter to fetch all Tasks.  |
| `filters_updated_at` | string | No | Return item(s) last updated within the specified ISO 8601 datetime range. Formats: `YYYY-MM-DD`...`YYYY-MM-DD` - Date `YYYY-MM-DDTHH:MM:SSZ`...`YYYY-MM-DDTHH:MM:SSZ` - DateTime with UTC Offset `YYYY-MM-DDTHH:MM:SS+XX:00`...`YYYY-MM-DDTHH:MM:SS+XX:00` - Datetime with Custom Offset |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Time And Material Timecards

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_TIME_AND_MATERIAL_TIMECARDS`

List Time And Material Timecards. Source: https://developers.procore.com/reference/rest/time-and-material-timecard?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `next_cursor` | string | No | Continuation cursor from the previous page. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Timecard Data

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_TIMECARD_DATA`

List Timecard Data. Source: https://developers.procore.com/reference/rest/timesheets?version=1.1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `end_date` | string | No | End date of specific timecards desired in YYYY-MM-DD format (use together with start_date) |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique identifier for the company. |
| `start_date` | string | No | Start date of specific timecards desired in YYYY-MM-DD format (use together with end_date) |
| `next_cursor` | string | No | Continuation cursor from the previous page. |
| `filters_deleted_at` | string | No | Returns item(s) deleted within the specified ISO 8601 datetime range. |
| `filters_updated_at` | string | No | Return item(s) last updated within the specified ISO 8601 datetime range. Formats: `YYYY-MM-DD`...`YYYY-MM-DD` - Date `YYYY-MM-DDTHH:MM:SSZ`...`YYYY-MM-DDTHH:MM:SSZ` - DateTime with UTC Offset `YYYY-MM-DDTHH:MM:SS+XX:00`...`YYYY-MM-DDTHH:MM:SS+XX:00` - Datetime with Custom Offset |
| `filters_custom_fields` | string | No | Returns timecard entries whose custom field values match the supplied JSON object. Keys are custom field definition identifiers as a plain numeric string (for example `"123"`); the `custom_field_` prefix is used only in serialized response payloads, not here. Matching is data-type aware: `decimal` fields are compared as numbers (so `"2"` matches a stored `2.0`); `string` and `rich_text` fields match on a case-insensitive substring (so `"match"` matches a stored `"match-me"`); all other data types (`lov_entry`, `lov_entries`, `boolean`, `datetime`, etc.) match on exact value. Applied to both the party-selection and row-selection paths, so pagination and the `Total` response header reflect the filtered result set. |
| `skip_saving_sticky_filters` | boolean | No | When true, the filters supplied on this request are not saved as the user's sticky Timesheets filters. Use this for background reads that should not change which filters the user sees the next time they open the Timesheets list. Has no effect on the response body. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List timecard entries

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_TIMECARD_ENTRIES`

List timecard entries. Source: https://developers.procore.com/reference/rest/timecard-entries?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `end_date` | string | No | The end of the date range for entries. (YYYY-MM-DD); if not provided, this will default to today |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `start_date` | string | No | The beginning of the date range for entries. (YYYY-MM-DD); if not provided, this will default to 1 week ago |
| `next_cursor` | string | No | Continuation cursor from the previous page. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List timecard entries (Company)

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_TIMECARD_ENTRIES_COMPANY`

List timecard entries (Company). Source: https://developers.procore.com/reference/rest/timecard-entries?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `end_date` | string | No | The ending of the date range for entries. (YYYY-MM-DD) |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique identifier for the company. |
| `filters_id` | array | No | Return item(s) with the specified IDs. |
| `start_date` | string | No | The beginning of the date range for entries. (YYYY-MM-DD) |
| `end_time_in` | string | No | The ending of the time_in range for entries (YYYY-MM-DDTHH:MM:SSZ). "Z" represents the timezone offset (i.e. -08:00, -0800). Optionally you may pass the literal "Z" which also means "UTC". |
| `next_cursor` | string | No | Continuation cursor from the previous page. |
| `start_time_in` | string | No | The beginning of the time_in range for entries (YYYY-MM-DDTHH:MM:SSZ). "Z" represents the timezone offset (i.e. -08:00, -0800). Optionally you may pass the literal "Z" which also means "UTC". |
| `use_filter_tz` | string | No | When passed as "true" the timezone from start_time_in or end_time_in will be used for all timestamps in the response. Otherwise they'll use UTC. |
| `serializer_view` | string ("ids_only" | "compact_with_date_range") | No | Changes what fields are included in the response. |
| `filters_party_id` | array | No | Return item(s) with the specified Party ID. |
| `filters_deleted_at` | string | No | Return item(s) that were deleted within the specified ISO 8601 datetime range. |
| `filters_updated_at` | string | No | Return item(s) last updated within the specified ISO 8601 datetime range. Formats: `YYYY-MM-DD`...`YYYY-MM-DD` - Date `YYYY-MM-DDTHH:MM:SSZ`...`YYYY-MM-DDTHH:MM:SSZ` - DateTime with UTC Offset `YYYY-MM-DDTHH:MM:SS+XX:00`...`YYYY-MM-DDTHH:MM:SS+XX:00` - Datetime with Custom Offset |
| `filters_in_progress_only` | boolean | No | Return work in progress item(s). |
| `filters_include_in_progress` | boolean | No | Return available and work in progress item(s). |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List timecard entries (Project)

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_TIMECARD_ENTRIES_PROJECT`

List timecard entries (Project). Source: https://developers.procore.com/reference/rest/timecard-entries?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `end_date` | string | No | The end of the date range for timecard entries. (YYYY-MM-DD) End date is inclusive. |
| `log_date` | string | No | Timecard entries at the specified date. (YYYY-MM-DD) |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `filters_id` | array | No | Return entries matching the specified entry ID(s). |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `start_date` | string | No | The beginning of the date range for timecard entries. (YYYY-MM-DD) Start date is inclusive. |
| `next_cursor` | string | No | Continuation cursor from the previous page. |
| `filters_date` | string | No | Filter by date. Accepts a single date (YYYY-MM-DD) or a date range (YYYY-MM-DD...YYYY-MM-DD). |
| `filters_search` | string | No | Text search filter for legacy search behavior. |
| `serializer_view` | string ("daily_log" | "extended" | "extended_costs" | "extended_daily_log" | "ids_only") | No | Changes what fields are included in the response. `extended_costs` adds `cost` and `currency_iso_code` to the extended permissions payload when the caller can view timecard entry costs. Those keys are omitted when the caller cannot, or when Cost Calculator cannot be read. An unknown value uses the default view.  |
| `filters_billable` | string | No | Return entries matching billable state. |
| `filters_party_id` | array | No | Return item(s) with the specified Party ID. |
| `filters_origin_id` | string | No | Return entries matching the specified origin ID. |
| `filters_sub_job_id` | integer | No | Return entries matching the specified sub job ID. |
| `filters_updated_at` | string | No | Return entries updated within the specified datetime/date range. Formats: YYYY-MM-DD...YYYY-MM-DD or YYYY-MM-DDTHH:MM:SSZ...YYYY-MM-DDTHH:MM:SSZ. |
| `filters_location_id` | integer | No | Return entries matching the specified location ID. |
| `filters_wbs_code_id` | integer | No | Return entries matching the specified WBS code ID. |
| `filters_cost_code_id` | integer | No | Return entries matching the specified cost code ID. |
| `filters_created_by_id` | array | No | Returns item(s) created by the specified User IDs. |
| `filters_approval_status` | string | No | Return entries matching the specified approval status. |
| `filters_in_progress_only` | boolean | No | Return work in progress item(s). |
| `filters_timesheet_group_id` | integer | No | Return entries belonging to the specified TimesheetGroup. |
| `filters_daily_log_header_id` | integer | No | Return entries matching the specified daily log header ID. |
| `filters_daily_log_segment_id` | array | No | Daily Log Segment ID filter |
| `filters_timecard_time_type_id` | integer | No | Return entries matching the specified timecard time type ID. |
| `filters_work_classification_id` | integer | No | Return entries matching the specified work classification ID. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Timecard Time Types

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_TIMECARD_TIME_TYPES_COMPA_77B88941`

List Timecard Time Types. Source: https://developers.procore.com/reference/rest/timecards?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Timecard Time Types

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_TIMECARD_TIME_TYPES_GLOBA_C78D17C5`

List Timecard Time Types. Source: https://developers.procore.com/reference/rest/time-types?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `next_cursor` | string | No | Continuation cursor from the previous page. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Timeline Events

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_TIMELINE_EVENTS`

List Timeline Events. Source: https://developers.procore.com/reference/rest/timeline-events?version=2.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | The page number to retrieve |
| `sort` | string ("timeline_event_id" | "timeline_event_name" | "start_date" | "finish_date") | No | Sort by supported fields. Accepts comma separated values to sort by multiple fields. Order is ascending by default, prefix field with '-' for descending |
| `per_page` | integer | No | Number of records per page |
| `company_id` | string | Yes | Unique identifier for the company |
| `project_id` | string | Yes | Unique identifier for the project |
| `next_cursor` | string | No | Continuation cursor from the previous page. |
| `schedule_id` | string | Yes | Unique identifier for the schedule |
| `filters_timeline_event_id` | string | No | Filter timeline events by timeline_event_id |
| `filters_timeline_event_name` | string | No | Filter timeline events by timeline_event_name |
| `filters_source_activity_deleted` | boolean | No | Filter timeline events by source activity deleted status |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Visitor Logs

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_VISITOR_LOGS`

List Visitor Logs. Source: https://developers.procore.com/reference/rest/visitor-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `end_date` | string | No | End date of specific logs desired in YYYY-MM-DD format (use together with start_date) |
| `log_date` | string | No | Date of specific logs desired in YYYY-MM-DD format |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `start_date` | string | No | Start date of specific logs desired in YYYY-MM-DD format (use together with end_date) |
| `next_cursor` | string | No | Continuation cursor from the previous page. |
| `filters_created_by_id` | array | No | Returns item(s) created by the specified User IDs. |
| `filters_daily_log_segment_id` | array | No | Daily Log Segment ID filter |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Waste Logs

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_WASTE_LOGS`

List Waste Logs. Source: https://developers.procore.com/reference/rest/waste-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `end_date` | string | No | End date of specific logs desired in YYYY-MM-DD format (use together with start_date) |
| `log_date` | string | No | Date of specific logs desired in YYYY-MM-DD format |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `start_date` | string | No | Start date of specific logs desired in YYYY-MM-DD format (use together with end_date) |
| `next_cursor` | string | No | Continuation cursor from the previous page. |
| `filters_vendor_id` | array | No | Return item(s) with the specified Vendor IDs. |
| `filters_created_by_id` | array | No | Returns item(s) created by the specified User IDs. |
| `filters_daily_log_segment_id` | array | No | Daily Log Segment ID filter |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Weather Logs

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_WEATHER_LOGS`

List Weather Logs. Source: https://developers.procore.com/reference/rest/weather-logs?version=1.1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `end_date` | string | No | End date of specific logs desired. Use together with start_date to specify a date range. Example formats YYYY-MM-DD, YYYY/MM/DD, DD-MM-YYYY, DD/MM/YYYY |
| `log_date` | string | No | Date of specific logs desired. Example formats YYYY-MM-DD, YYYY/MM/DD, DD-MM-YYYY, DD/MM/YYYY |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `start_date` | string | No | Start date of specific logs desired. Use together with end_date to specify a date range. Example formats YYYY-MM-DD, YYYY/MM/DD, DD-MM-YYYY, DD/MM/YYYY |
| `next_cursor` | string | No | Continuation cursor from the previous page. |
| `filters_status` | string ("all" | "approved" | "pending") | No | Filter on log status |
| `filters_created_by_id` | array | No | Returns item(s) created by the specified User IDs. |
| `filters_daily_log_segment_id` | array | No | Daily Log Segment ID filter |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Work Logs

**Slug:** `PROCORE_FIELD_OPERATIONS_LIST_WORK_LOGS`

List Work Logs. Source: https://developers.procore.com/reference/rest/work-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `end_date` | string | No | End date of specific logs desired in YYYY-MM-DD format (use together with start_date) |
| `log_date` | string | No | Date of specific logs desired in YYYY-MM-DD format |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `start_date` | string | No | Start date of specific logs desired in YYYY-MM-DD format (use together with end_date) |
| `next_cursor` | string | No | Continuation cursor from the previous page. |
| `filters_created_by_id` | array | No | Returns item(s) created by the specified User IDs. |
| `filters_daily_log_segment_id` | array | No | Daily Log Segment ID filter |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Remove signature from timecard entry (Project)

**Slug:** `PROCORE_FIELD_OPERATIONS_REMOVE_SIGNATURE_FROM_TIMECARD_00D6F73D`

Remove signature from timecard entry (Project). Source: https://developers.procore.com/reference/rest/timecard-entries?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | The ID of the timecard entry. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Restore a Time And Material Entry

**Slug:** `PROCORE_FIELD_OPERATIONS_RESTORE_TIME_AND_MATERIAL_ENTRY`

Restore a Time And Material Entry. Source: https://developers.procore.com/reference/rest/time-and-material-entry?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Unique identifier of the Time & Material entry. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Search all equipment

**Slug:** `PROCORE_FIELD_OPERATIONS_SEARCH_EQUIPMENT_COMPANY_MANAG_DE998B08`

Deprecated. Search all equipment. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/managed-equipment---company-level?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique identifier for the company. |
| `next_cursor` | string | No | Continuation cursor from the previous page. |
| `filters_year` | integer | No | Return item(s) with the specified year. |
| `filters_status` | array | No | Returns item(s) matching the specified status value. |
| `search_keyword` | string | No | Search keyword to search Project Managed Equipment. |
| `filters_updated_at` | string | No | Return item(s) last updated within the specified ISO 8601 datetime range. Formats: `YYYY-MM-DD`...`YYYY-MM-DD` - Date `YYYY-MM-DDTHH:MM:SSZ`...`YYYY-MM-DDTHH:MM:SSZ` - DateTime with UTC Offset `YYYY-MM-DDTHH:MM:SS+XX:00`...`YYYY-MM-DDTHH:MM:SS+XX:00` - Datetime with Custom Offset |
| `filters_company_visible` | boolean | No | If true, return item(s) with 'company visible' status. |
| `filters_last_service_date` | string | No | Return item(s) with a last service date within the specified ISO 8601 datetime range. |
| `filters_next_service_date` | string | No | Return item(s) with a next service date within the specified ISO 8601 datetime range. |
| `filters_current_project_id` | integer | No | Return item(s) with the specified current project ID. |
| `filters_managed_equipment_id` | integer | No | Return item(s) with the specified Managed Equipment ID. |
| `filters_managed_equipment_make_id` | integer | No | Return item(s) with the specified Managed Equipment Make ID. |
| `filters_managed_equipment_type_id` | integer | No | Return item(s) with the specified Managed Equipment Type ID. |
| `filters_managed_equipment_model_id` | integer | No | Return item(s) with the specified Managed Equipment Model ID. |
| `filters_managed_equipment_category_id` | integer | No | Return item(s) with the specified Managed Equipment Category ID. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Search all equipment

**Slug:** `PROCORE_FIELD_OPERATIONS_SEARCH_EQUIPMENT_PROJECT_MANAG_0E671A48`

Deprecated. Search all equipment. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/managed-equipment---project-level?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page |
| `per_page` | integer | No | Elements per page |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `next_cursor` | string | No | Continuation cursor from the previous page. |
| `filters_year` | integer | No | Return item(s) with the specified year. |
| `filters_onsite` | array | No | Onsite Dates. Returns item(s) with the specified range of onsite dates. |
| `filters_status` | array | No | Returns item(s) matching the specified status value. |
| `search_keyword` | string | No | Search keyword to search Project Managed Equipment. |
| `filters_offsite` | array | No | Offsite Dates. Returns item(s) with the specified range of offsite dates. |
| `filters_ownership` | string ("Owned" | "Rented" | "Sub") | No | Returns only item(s) with the specified ownership value. Must be one of Owned, Rented, or Sub. |
| `filters_vendor_id` | integer | No | Return item(s) with the specified Vendor ID. |
| `filters_updated_at` | string | No | Return item(s) last updated within the specified ISO 8601 datetime range. Formats: `YYYY-MM-DD`...`YYYY-MM-DD` - Date `YYYY-MM-DDTHH:MM:SSZ`...`YYYY-MM-DDTHH:MM:SSZ` - DateTime with UTC Offset `YYYY-MM-DDTHH:MM:SS+XX:00`...`YYYY-MM-DDTHH:MM:SS+XX:00` - Datetime with Custom Offset |
| `filters_company_visible` | boolean | No | If true, return item(s) with 'company visible' status. |
| `filters_induction_status` | boolean | No | Returns item(s) with the specified inudction status. |
| `filters_last_service_date` | string | No | Return item(s) with a last service date within the specified ISO 8601 datetime range. |
| `filters_next_service_date` | string | No | Return item(s) with a next service date within the specified ISO 8601 datetime range. |
| `filters_current_project_id` | integer | No | Return item(s) with the specified current project ID. |
| `filters_managed_equipment_id` | integer | No | Return item(s) with the specified Managed Equipment ID. |
| `filters_managed_equipment_make_id` | integer | No | Return item(s) with the specified Managed Equipment Make ID. |
| `filters_managed_equipment_type_id` | integer | No | Return item(s) with the specified Managed Equipment Type ID. |
| `filters_managed_equipment_model_id` | integer | No | Return item(s) with the specified Managed Equipment Model ID. |
| `filters_managed_equipment_category_id` | integer | No | Return item(s) with the specified Managed Equipment Category ID. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Sync Calendar Items

**Slug:** `PROCORE_FIELD_OPERATIONS_SYNC_CALENDAR_ITEMS`

Sync Calendar Items. Source: https://developers.procore.com/reference/rest/calendar-items?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Sync tasks

**Slug:** `PROCORE_FIELD_OPERATIONS_SYNC_TASKS`

Sync tasks. Source: https://developers.procore.com/reference/rest/tasks?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Sync ToDos

**Slug:** `PROCORE_FIELD_OPERATIONS_SYNC_TO_DOS`

Deprecated. Sync ToDos. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/todos?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Accident Log

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_ACCIDENT_LOG`

Update Accident Log. Source: https://developers.procore.com/reference/rest/accident-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Accident log ID |
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `attachments` | array | No | Accident Log Attachments. To upload attachments you must upload the entire payload as `multipart/form-data` content-type and specify each parameter as form-data together with `attachments[]` as files. |
| `accident_log` | object | No | Structured accident log data matching the documented Procore schema. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Actual Production Quantity

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_ACTUAL_PRODUCTION_QUANTITY`

Update Actual Production Quantity. Source: https://developers.procore.com/reference/rest/actual-production-quantities?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Unique identifier of the Actual Production Quantity. |
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Calendar Item

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_CALENDAR_ITEM`

Update Calendar Item. Source: https://developers.procore.com/reference/rest/calendar-items?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Calendar Item ID |
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Call Log

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_CALL_LOG`

Update Call Log. Source: https://developers.procore.com/reference/rest/call-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Call log ID |
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `call_log` | object | No | Structured call log data matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `attachments` | array | No | Call Log Attachments are not viewable or used on web. To upload attachments you must upload the entire payload as `multipart/form-data` content-type and specify each parameter as form-data together with `attachments[]` as files. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Daily Construction Report Log

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_DAILY_CONSTRUCTION_REPORT_LOG`

Update Daily Construction Report Log. Source: https://developers.procore.com/reference/rest/daily-construction-report-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Daily Construction Report Log ID |
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `attachments` | array | No | Daily Construction Report Log Attachments. To upload attachments you must upload the entire payload as `multipart/form-data` content-type and specify each parameter as form-data together with `attachments[]` as files. |
| `run_configurable_validations` | boolean | No | If true, validations are run for the corresponding Configurable Field Set. |
| `daily_construction_report_log` | object | No | Structured daily construction report log data matching the documented Procore schema. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Delay Log

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_DELAY_LOG`

Update Delay Log. Source: https://developers.procore.com/reference/rest/delay-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Delay log ID |
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `delay_log` | object | No | Structured delay log data matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `attachments` | array | No | Attachments pertaining the Log. To upload attachments you must upload the entire payload as `multipart/form-data` content-type and specify each parameter as form-data together with `attachments[]` as files. |
| `run_configurable_validations` | boolean | No | If true, validations are run for the corresponding Configurable Field Set. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update a Delay Log Type

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_DELAY_LOG_TYPE`

Update a Delay Log Type. Source: https://developers.procore.com/reference/rest/delay-log-types?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Delay Log Type ID |
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Deleted Equipment Serial Number

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_DELETED_EQUIPMENT_SERIAL_NUMBER`

Deprecated. Update Deleted Equipment Serial Number. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/managed-equipment---company-level?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Unique identifier of the managed equipment. |
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Delivery Log

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_DELIVERY_LOG`

Update Delivery Log. Source: https://developers.procore.com/reference/rest/delivery-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Delivery Log ID |
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `attachments` | array | No | Attachments are not viewable or used on web. To upload attachments you must upload the entire payload as `multipart/form-data` content-type and specify each parameter as form-data together with `attachments[]` as files. |
| `delivery_log` | object | No | Structured delivery log data matching the documented Procore schema. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Dumpster Log

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_DUMPSTER_LOG`

Update Dumpster Log. Source: https://developers.procore.com/reference/rest/dumpster-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Dumpster Log ID |
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `attachments` | array | No | Dumpster Log Attachments are not viewable or used on web To upload attachments you must upload the entire payload as `multipart/form-data` content-type and specify each parameter as form-data together with `attachments[]` as files. |
| `dumpster_log` | object | No | Structured dumpster log data matching the documented Procore schema. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Edit a Timecard Entry

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_EDIT_TIMECARD_ENTRY`

Edit a Timecard Entry. Source: https://developers.procore.com/reference/rest/timesheets?version=1.1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | ID of the Timecard Entry |
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Equipment Category

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_EQUIPMENT_CATEGORY`

Deprecated. Update Equipment Category. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/equipment-category?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | ID of the Equipment Category |
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Equipment

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_EQUIPMENT_COMPANY_MANAG_075D26EC`

Deprecated. Update Equipment. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/managed-equipment---company-level?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Unique identifier of the managed equipment. |
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Equipment Log

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_EQUIPMENT_LOG`

Update Equipment Log. Source: https://developers.procore.com/reference/rest/admin-equipment-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Equipment Log ID |
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `attachments` | array | No | Equipment Log Attachments. To upload attachments you must upload the entire payload as `multipart/form-data` content-type and specify each parameter as form-data together with `attachments[]` as files. |
| `equipment_log` | object | No | Structured equipment log data matching the documented Procore schema. |
| `run_configurable_validations` | boolean | No | If true, validations are run for the corresponding Configurable Field Set. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Equipment Maintenance Log

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_EQUIPMENT_MAINTENANCE_LOG`

Deprecated. Update Equipment Maintenance Log. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/equipment-maintenance-log?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Identifier of the equipment maintenance log. |
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update an equipment make

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_EQUIPMENT_MAKE`

Deprecated. Update an equipment make. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/equipment-make?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | ID of the equipment make |
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update an equipment model

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_EQUIPMENT_MODEL`

Deprecated. Update an equipment model. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/equipment-model?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Unique identifier of the equipment model. |
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update an equipment

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_EQUIPMENT_PROJECT_MANAG_A7EF6322`

Deprecated. Update an equipment. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/managed-equipment---project-level?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Unique identifier of the managed equipment. |
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update equipment timecard entry approval status

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_EQUIPMENT_TIMECARD_ENTR_0930AB8F`

Beta. Update equipment timecard entry approval status. This Procore endpoint is beta and its contract may change. Source: https://developers.procore.com/reference/rest/equipment-timecard-entries?version=2.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | string | Yes | Unique identifier for the company. |
| `project_id` | string | Yes | Unique identifier for the project. |
| `serializer_view` | string ("default" | "compact" | "mobile") | No | Optional response blueprint view. Defaults to `default`. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update equipment timecard entry (Project)

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_EQUIPMENT_TIMECARD_ENTRY_PROJECT`

Beta. Update equipment timecard entry (Project). This Procore endpoint is beta and its contract may change. Source: https://developers.procore.com/reference/rest/equipment-timecard-entries?version=2.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | ID of the equipment timecard entry |
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique identifier for the company. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update an equipment type

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_EQUIPMENT_TYPE`

Deprecated. Update an equipment type. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/equipment-type?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Unique identifier of the equipment type. |
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Inspection Log

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_INSPECTION_LOG`

Update Inspection Log. Source: https://developers.procore.com/reference/rest/inspection-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Inspection Log ID |
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `attachments` | array | No | Inspection Log Attachments are not viewable or used on web. To upload attachments you must upload the entire payload as `multipart/form-data` content-type and specify each parameter as form-data together with `attachments[]` as files. |
| `inspection_log` | object | No | Structured inspection log data matching the documented Procore schema. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Instruction

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_INSTRUCTION`

Update Instruction. When send_emails is true, this also sends notification emails and cannot be undone. Source: https://developers.procore.com/reference/rest/instructions?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Instruction ID |
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `send_emails` | boolean | No | Designates whether or not emails will be sent (default false) |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Instruction Type

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_INSTRUCTION_TYPE`

Update Instruction Type. Source: https://developers.procore.com/reference/rest/instruction-types?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Instruction ID |
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Lookahead Task

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_LOOKAHEAD_TASK`

Update Lookahead Task. Source: https://developers.procore.com/reference/rest/lookahead-tasks?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Lookahead Task ID |
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Manpower Log

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_MANPOWER_LOG`

Update Manpower Log. Source: https://developers.procore.com/reference/rest/manpower-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Manpower Log ID |
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `attachments` | array | No | Manpower Log Attachments. To upload attachments you must upload the entire payload as `multipart/form-data` content-type and specify each parameter as form-data together with `attachments[]` as files. |
| `manpower_log` | object | No | Structured manpower log data matching the documented Procore schema. |
| `run_configurable_validations` | boolean | No | If true, validations are run for the corresponding Configurable Field Set. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Material

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_MATERIAL`

Update Material. Source: https://developers.procore.com/reference/rest/material?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Unique identifier of the material. |
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Multiple Time And Material Entries

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_MULTIPLE_TIME_AND_MATER_F1C08E48`

Update Multiple Time And Material Entries. Source: https://developers.procore.com/reference/rest/time-and-material-entry?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `run_configurable_validations` | boolean | No | If true, validations are run for the corresponding Configurable Field Set. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Notes Log

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_NOTES_LOG`

Update Notes Log. Source: https://developers.procore.com/reference/rest/notes-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Notes Log ID |
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `notes_log` | object | No | Structured notes log data matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `attachments` | array | No | Notes Log Attachments. To upload attachments you must upload the entire payload as `multipart/form-data` content-type and specify each parameter as form-data together with `attachments[]` as files. |
| `run_configurable_validations` | boolean | No | If true, validations are run for the corresponding Configurable Field Set. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Plan Revision Log

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_PLAN_REVISION_LOG`

Update Plan Revision Log. Source: https://developers.procore.com/reference/rest/plan-revision-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Plan Revision Log ID |
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `attachments` | array | No | Plan Revision Log Attachments are not viewable or used on web. To upload attachments you must upload the entire payload as `multipart/form-data` content-type and specify each parameter as form-data together with `attachments[]` as files. |
| `plan_revision_log` | object | No | Structured plan revision log data matching the documented Procore schema. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Productivity Log

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_PRODUCTIVITY_LOG`

Update Productivity Log. Source: https://developers.procore.com/reference/rest/productivity-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Productivity Log ID |
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update an Project Equipment Log

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_PROJECT_EQUIPMENT_LOG`

Deprecated. Update an Project Equipment Log. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/equipment-log?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Identifier of the equipment log entry. |
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Project Equipment Maintenance Log

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_PROJECT_EQUIPMENT_MAINT_614459F6`

Deprecated. Update Project Equipment Maintenance Log. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/equipment-maintenance-log?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Identifier of the equipment maintenance log. |
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Quantity Log

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_QUANTITY_LOG`

Update Quantity Log. Source: https://developers.procore.com/reference/rest/quantity-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Quantity Log ID |
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `attachments` | array | No | Quantity Log Attachments. To upload attachments you must upload the entire payload as `multipart/form-data` content-type and specify each parameter as form-data together with `attachments[]` as files. |
| `quantity_log` | object | No | Structured quantity log data matching the documented Procore schema. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update resource

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_RESOURCE`

Update resource. Source: https://developers.procore.com/reference/rest/schedule-resources?version=1.1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | ID of the resource |
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update resource

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_RESOURCE_V1_0`

Update resource. Source: https://developers.procore.com/api/v1/resource_groups/full_oas?version=1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | ID of the resource |
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Restoring an equipment

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_RESTORING_EQUIPMENT`

Deprecated. Restoring an equipment. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/managed-equipment---project-level?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Unique identifier of the managed equipment. |
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Review Requested Changes

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_REVIEW_REQUESTED_CHANGE_12821089`

Review Requested Changes. Source: https://developers.procore.com/reference/rest/task-requested-changes?version=1.1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Review Requested Changes

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_REVIEW_REQUESTED_CHANGE_597454B4`

Deprecated. Review Requested Changes. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/requested-changes?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update rounding configuration

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_ROUNDING_CONFIGURATION`

Update rounding configuration. Source: https://developers.procore.com/reference/rest/rounding-configuration?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Safety Violation Log

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_SAFETY_VIOLATION_LOG`

Update Safety Violation Log. Source: https://developers.procore.com/reference/rest/safety-violation-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Safety Violation Log ID |
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `attachments` | array | No | Safety Violation Log Attachments. To upload attachments you must upload the entire payload as `multipart/form-data` content-type and specify each parameter as form-data together with `attachments[]` as files. |
| `safety_violation_log` | object | No | Structured safety violation log data matching the documented Procore schema. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update schedule integration type

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_SCHEDULE_INTEGRATION_TYPE`

Deprecated. Update schedule integration type. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/schedule-type?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Schedule Metadata

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_SCHEDULE_METADATA`

Update Schedule Metadata. Source: https://developers.procore.com/reference/rest/schedule?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update the state of a Daily Log Header

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_STATE_OF_DAILY_LOG_HEADER`

Update the state of a Daily Log Header. Source: https://developers.procore.com/reference/rest/daily-log-headers?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | No | The id of the requested Daily Log Header |
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `app_name` | string | No | The name of the app issuing this request. When set to 'web', the requesting user's saved Daily Log filters are applied to the PDF sent to the distribution list. |
| `log_date` | string | No | The log date for the requested Daily Log Header |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update task

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_TASK`

Update task. Source: https://developers.procore.com/reference/rest/tasks?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | ID of the task |
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update a Time And Material Entry

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_TIME_AND_MATERIAL_ENTRY`

Update a Time And Material Entry. Source: https://developers.procore.com/reference/rest/time-and-material-entry?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Unique identifier of the Time & Material entry. |
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `run_configurable_validations` | boolean | No | If true, validations are run for the corresponding Configurable Field Set. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update a Time And Material Equipment Log

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_TIME_AND_MATERIAL_EQUIPMENT_LOG`

Update a Time And Material Equipment Log. Source: https://developers.procore.com/reference/rest/time-and-material-equipment-log?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Unique identifier of the Time & Material equipment log. |
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `run_configurable_validations` | boolean | No | If true, validations are run for the corresponding Configurable Field Set. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update a Time And Material Notification

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_TIME_AND_MATERIAL_NOTIFICATION`

Update a Time And Material Notification. Source: https://developers.procore.com/reference/rest/time-and-material-notification?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `run_configurable_validations` | boolean | No | If true, validations are run for the corresponding Configurable Field Set. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Time And Material Timecard

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_TIME_AND_MATERIAL_TIMECARD`

Update Time And Material Timecard. Source: https://developers.procore.com/reference/rest/time-and-material-timecard?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Unique identifier of the Time & Material timecard. |
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `run_configurable_validations` | boolean | No | If true, validations are run for the corresponding Configurable Field Set. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Timecard Entries

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_TIMECARD_ENTRIES`

Update Timecard Entries. Source: https://developers.procore.com/reference/rest/timesheets?version=1.1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update timecard entry

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_TIMECARD_ENTRY`

Update timecard entry. Source: https://developers.procore.com/reference/rest/timecard-entries?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | ID of the timecard entry |
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update timecard entry (Company)

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_TIMECARD_ENTRY_COMPANY`

Update timecard entry (Company). Source: https://developers.procore.com/reference/rest/timecard-entries?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | ID of the timecard entry |
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update timecard entry (Project)

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_TIMECARD_ENTRY_PROJECT`

Update timecard entry (Project). Source: https://developers.procore.com/reference/rest/timecard-entries?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | ID of the timecard entry |
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `serializer_view` | string | No | Changes which fields are included in the serialized response. - `extended_daily_log` - Returns extended fields plus Daily Log segment associations - Default (not specified) - Returns the standard extended Daily Log field set  |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update timecard entry signature (Project)

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_TIMECARD_ENTRY_SIGNATURE_PROJECT`

Update timecard entry signature (Project). Source: https://developers.procore.com/reference/rest/timecard-entries?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | The ID of the timecard entry. |
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Timecard Time Type

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_TIMECARD_TIME_TYPE`

Update Timecard Time Type. Source: https://developers.procore.com/reference/rest/timecards?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | ID of the Timecard Time Type |
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Timeline Event

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_TIMELINE_EVENT`

Update Timeline Event. Source: https://developers.procore.com/reference/rest/timeline-events?version=2.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | string | Yes | Unique identifier for the company |
| `project_id` | string | Yes | Unique identifier for the project |
| `schedule_id` | string | Yes | Unique identifier for the schedule |
| `timeline_event_id` | string | Yes | Timeline Events ID |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Timesheet

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_TIMESHEET`

Update Timesheet. Source: https://developers.procore.com/reference/rest/timesheets?version=1.1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | ID of the Timesheet |
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update timesheet status

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_TIMESHEET_STATUS`

Update timesheet status. Source: https://developers.procore.com/reference/rest/timesheets?version=1.1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update timesheet to budget configuration

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_TIMESHEET_TO_BUDGET_CON_0A5B2C41`

Update timesheet to budget configuration. Source: https://developers.procore.com/reference/rest/timesheet-to-budget-configuration?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Timesheet

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_TIMESHEET_V1_0`

Update Timesheet. Source: https://developers.procore.com/api/v1/resource_groups/full_oas?version=1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | ID |
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update todo

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_TODO`

Deprecated. Update todo. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/todos?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | ID of the todo |
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update User Permission

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_USER_PERMISSION`

Deprecated. Update User Permission. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/managed-equipment---company-level?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique identifier for the company. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Visitor Log

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_VISITOR_LOG`

Update Visitor Log. Source: https://developers.procore.com/reference/rest/visitor-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Visitor Log ID |
| `body` | object | Yes | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `run_configurable_validations` | boolean | No | If true, validations are run for the corresponding Configurable Field Set. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Waste Log

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_WASTE_LOG`

Update Waste Log. Source: https://developers.procore.com/reference/rest/waste-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Waste Log ID |
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `waste_log` | object | No | Structured waste log data matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `attachments` | array | No | Waste Log Attachments are not viewable or used on web. To upload attachments you must upload the entire payload as `multipart/form-data` content-type and specify each parameter as form-data together with `attachments[]` as files. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Weather Log

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_WEATHER_LOG`

Update Weather Log. Source: https://developers.procore.com/reference/rest/weather-logs?version=1.1

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Weather Log ID |
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `attachments` | array | No | Weather Log Attachments. To upload attachments you must upload the entire payload as `multipart/form-data` content-type and specify each parameter as form-data together with `attachments[]` as files. |
| `weather_log` | object | No | Structured weather log data matching the documented Procore schema. |
| `run_configurable_validations` | boolean | No | If true, validations are run for the corresponding Configurable Field Set. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Work Log

**Slug:** `PROCORE_FIELD_OPERATIONS_UPDATE_WORK_LOG`

Update Work Log. Source: https://developers.procore.com/reference/rest/work-logs?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | Work Log ID |
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `work_log` | object | No | Structured work log data matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `attachments` | array | No | Scheduled Work Log Attachments are not viewable or used on web. To upload attachments you must upload the entire payload as `multipart/form-data` content-type and specify each parameter as form-data together with `attachments[]` as files. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Upload schedule file

**Slug:** `PROCORE_FIELD_OPERATIONS_UPLOAD_SCHEDULE_FILE_SCHEDULE_84539F67`

Deprecated. Upload schedule file. This Procore endpoint is deprecated; use it only for legacy workflows. Source: https://developers.procore.com/reference/rest/schedule-integration?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `schedule_integration` | object | No | Structured schedule integration data matching the documented Procore schema. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Upload schedule file

**Slug:** `PROCORE_FIELD_OPERATIONS_UPLOAD_SCHEDULE_FILE_SCHEDULE_9FD24DCD`

Upload schedule file. Source: https://developers.procore.com/reference/rest/schedule-integration?version=1.0

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `body` | object | No | Structured request body matching the documented Procore schema. |
| `company_id` | integer | Yes | Unique company identifier associated with the Procore User Account. |
| `project_id` | integer | Yes | Unique identifier for the project. |
| `schedule_integration` | object | No | Structured schedule integration data matching the documented Procore schema. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |
