Actions126
- Account Actions
- City Actions
- Contact Actions
- Contact Line of Business Actions
- Contact Number of Employees Actions
- Contact Origin Actions
- Contact Product Actions
- Contact Relationship Actions
- Contact Status Actions
- Contact Type Actions
- Country Actions
- Currency Actions
- Deal Actions
- Deal Loss Reason Actions
- Deal Pipeline Actions
- Deal Stage Actions
- Deal Status Actions
- Department Actions
- Document Actions
- Document Template Actions
- Field Actions
- Field Entity Actions
- Field Options Table Actions
- Field Options Table Option Actions
- Field Type Actions
- Interaction Record Actions
- Operation Actions
- Order Actions
- Order Stage Actions
- Phone Type Actions
- Product Actions
- Product Family Actions
- Product Group Actions
- Product Part Actions
- Quote Actions
- Quote Approval Status Actions
- Relative Date Actions
- Role Actions
- State Actions
- Tag Actions
- Task Actions
- Task Email Reminder Actions
- Task Repeat Interval Unit Actions
- Task Type Actions
- Team Actions
- User Actions
- User Profile Actions
- Webhook Actions
- Webhook Action Actions
Product Part → Delete
AI-generatedSummary
Delete a product part in Ploomes CRM by ID. Send one DELETE request to /Products@Parts(ID) for each incoming workflow item.
Inputs
- resourceId (required) — ID of the product part to delete.
Output shape
Success items containing a confirmation object or the API response, with separate Error and Timeout outputs.
An empty response produces success, resource, operation, and timestamp fields. Otherwise, the API response is returned, with any value array split into individual items. HTTP 408 and 504 errors go to Timeout; other errors go to Error only when Continue On Fail is enabled, otherwise execution throws. Error items contain error, statusCode, isTimeout, resource, operation, and timestamp.