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 → Delete
AI-generatedSummary
Deletes a single Product in Ploomes CRM by ID by sending an HTTP DELETE to https://api2.ploomes.com/Products(
Inputs
- ID (resourceId) (required) — The ID of the product to delete. It is inserted into the URL as /Products(
). It is a string, so it can come from an expression such as an earlier Get Many result.
Output shape
One item on the Success output per input item. Ploomes usually returns an empty body for DELETE, so the item is a synthetic confirmation: { success: true, resource: "product", operation: "delete", timestamp:
The node has three outputs: Success, Error and Timeout. A failed request produces an item on the Error output with error, statusCode, isTimeout, resource, operation and timestamp. HTTP 408 and 504 go to the Timeout output instead. Unless Continue On Fail is enabled, a non-timeout error stops the workflow. Timeout errors never stop it. Deletion is permanent as far as the node is concerned: it has no confirmation step and no undo. Caching options apply only to Get Many and are ignored here. The request is authenticated with the ploomesApi credential.
Examples
Example 1: Remove a discontinued product whose ID is already known.
Resource: Product, Operation: Delete, ID: 12345
Example 2: Delete products returned by an earlier Ploomes Get Many step, one per item.
Resource: Product, Operation: Delete, ID: {{ $json.Id }}. Enable Continue On Fail and route the Error output to a logging step.
