Create Generic Tool Item
create_generic_tool_itemCreate a new item in a Procore project's custom generic tool, specifying details like title, status, due date, and assignees.
Instructions
Create a new Generic Tool Item in the specified Project and Generic Tool. For more information on Generic Tool and Correspondence Tool endpoints, see Working with the Correspondence Tool. Use this to create a new Custom - Configurable Tools in Procore. Creates a new Custom - Configurable Tools and returns the created object on success (HTTP 201). Required parameters: generic_tool_id, project_id. Procore API: Company Admin > Custom - Configurable Tools. Endpoint: POST /rest/v1.0/projects/{project_id}/generic_tools/{generic_tool_id}/generic_tool_items
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| generic_tool_id | Yes | URL path parameter — unique identifier for the Generic Tool | |
| project_id | Yes | URL path parameter — unique identifier for the project. | |
| view | No | Query string parameter — if supplied customize the response format | |
| description | No | JSON request body field — the description of the generic tool item. | |
| due_date | No | JSON request body field — the due date for the generic tool item. | |
| position | No | JSON request body field — the position/number of the generic tool item. | |
| private | No | JSON request body field — if this property is set to true, the generic tool item is private. If this property is set to false, the generic tool item is not private. | |
| skip_emails | No | JSON request body field — if true creating and updating the item will not send emails to the users on the item. | |
| schedule_impact | No | JSON request body field — the schedule impact status for the generic tool item. | |
| schedule_impact_value | No | JSON request body field — specifies a value for the schedue impact of the generic tool item. | |
| cost_impact | No | JSON request body field — the cost impact of the generic tool item. | |
| cost_impact_value | No | JSON request body field — specifies a value for the cost impact of the generic tool item. | |
| status | No | JSON request body field — the status of the generic tool item. | |
| title | No | JSON request body field — the title of the generic tool item. | |
| received_from_id | No | JSON request body field — the unique identifier for the Received From entity. | |
| location_id | No | JSON request body field — the location identifier for the generic tool item. | |
| cost_code_id | No | JSON request body field — the cost code identifier for the generic tool item. | |
| specification_section_id | No | JSON request body field — the specification section identifier for the generic tool item. | |
| trade_id | No | JSON request body field — the trade identifier for the generic tool item. | |
| distribution_member_ids | No | JSON request body field — an array of distribution member identifiers for the generic tool item. | |
| assignee_ids | No | JSON request body field — an array of assignee identifiers for the generic tool item. | |
| attachments | No | JSON request body field — specifies an array of generic tool item attachments. To upload attachments you must upload the entire payload as a `multipart/form-data` content-type and specify each parameter as form-data togethe... | |
| 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 ... | |
| drawing_revision_ids | No | JSON request body field — drawing Revisions to attach to the response | |
| file_version_ids | No | JSON request body field — file Versions to attach to the response | |
| form_ids | No | JSON request body field — forms to attach to the response | |
| image_ids | No | JSON request body field — images to attach to the response | |
| upload_ids | No | JSON request body field — uploads to attach to the response | |
| document_management_document_revision_ids | No | JSON request body field — pDM document to attach to the response |