Update Project Folder
update_project_folderUpdate a Procore project folder's properties—name, parent, tracking, private status, or custom fields—using the folder ID and project ID. Send only the fields you want to change.
Instructions
Update the specified folder. Send only the fields you intend to change; omitted fields keep their current values. Pass the record's fields as top-level arguments — they are nested under "folder" in the request payload for you. id must identify an existing parent record — resolve it with the matching list tool first. Returns the modified project folder on success. Failures come back as an error payload carrying the HTTP status — commonly 401 when the token has expired, 403 without tool permission, and 404 when an id does not resolve. Required parameters: id, project_id. Procore API: Core > Documents. Endpoint: PATCH /rest/v1.0/folders/{id}
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | URL path parameter — unique identifier of the Documents resource | |
| name | No | JSON request body field — the Name of the folder | |
| parent_id | No | JSON request body field — the ID of the parent folder to move the folder to. | |
| is_tracked | No | JSON request body field — status if a folder should be tracked (true/false) | |
| project_id | Yes | Query string parameter — unique identifier for the project. | |
| explicit_permissions | No | JSON request body field — set folder to private (true/false) | |
| custom_field_%{custom_field_definition_id} | No | JSON request body field — value of the custom field. The data type of the value passed in corresponds with the data_type of the Custom Field Definition. For a lov_entry data_type the value passed in should be the ID of one ... |