Ploomes CRMInstall

Summary

Marks a Ploomes deal as lost by sending a POST to the deal's Lose action endpoint (https://api2.ploomes.com/Deals()/Lose).

Inputs

• ID (required) — The ID of the deal to mark as lost (resourceId). Interpolated into the URL as /Deals()/Lose. Evaluated per input item, so it can be set by an expression to process many deals.

Output shape

One output item per input item on the Success output. If the API returns a JSON body (a single object, or an OData value array that is split into one item per element), that is emitted as-is. If the API returns an empty body, the item is {success: true, resource, operation, timestamp}.

The node has three outputs: Success, Error, and Timeout. Failures emit {error, statusCode, isTimeout, resource, operation, timestamp} on Error, or on Timeout for HTTP 408/504. A non-timeout error stops the workflow unless Continue On Fail is enabled. The operation sends no request body, so no loss reason or other data can be passed. Only the ID is used. Whether Ploomes requires or accepts additional data for Lose is not shown in the source.

Examples

Example 1: Close a deal as lost after a CRM-triggered event, such as a customer declining a proposal.

Resource: Deal, Operation: Lose, ID: {{ $json.dealId }}

Example 2: Mark a fixed deal as lost from a manual test run.

Resource: Deal, Operation: Lose, ID: 12345678

Links

• n8n community nodes installation guide