Update Company Folder
update_company_folderUpdate an existing company folder in Procore, modifying only the provided fields. Requires the folder ID and company ID; errors like 404 indicate an invalid ID, so list folders first.
Instructions
Updates an existing company folder for the specified Procore company. 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. company_id defaults to the value set by procore_set_config when omitted, and id must identify an existing parent record — resolve it with the matching list tool first. Returns the modified company 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: company_id, id, name. Procore API: Core > Documents. Endpoint: PATCH /rest/v1.0/companies/{company_id}/folders/{id}
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | URL path parameter — unique identifier of the Documents resource | |
| name | Yes | JSON request body field — the Name of the folder | |
| parent_id | No | JSON request body field — the ID of the parent folder to create the folder in. If not set the folder will be created under the root folder. | |
| company_id | Yes | URL path parameter — unique identifier for the company. | |
| is_tracked | No | JSON request body field — status if a folder should be tracked (true/false) | |
| 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 ... |