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
Deal Pipeline → Create
AI-generatedSummary
Creates a new deal pipeline in Ploomes CRM by sending the supplied JSON body as a POST to the /Deals@Pipelines endpoint of the Ploomes API (api2.ploomes.com).
Inputs
- Body (JSON) (required) — JSON object with the pipeline's entity properties, sent as the POST request body. Defaults to
{}, which sends an empty object, so you must fill in the fields the Ploomes API expects for a pipeline. The node doesn't validate the contents. A string value is parsed with JSON.parse, and invalid JSON causes an error for that item.
Output shape
One output item per input item on the 'Success' output, containing the JSON response from Ploomes (normally the created pipeline record). If the API response has a value array, each element is emitted as a separate item. If the response body is empty, the item is { success: true, resource, operation, timestamp }.
The node has three outputs: Success, Error and Timeout. Failed requests produce an item with
error,statusCode,isTimeout,resource,operationandtimestamp. HTTP 408 and 504 go to the Timeout output, and all other failures go to Error. The node throws on non-timeout errors unless 'Continue On Fail' is enabled. Requests use the requiredploomesApicredential. Caching doesn't apply to create.
Examples
Example 1: Create a new sales pipeline with a fixed name
Resource: Deal Pipeline; Operation: Create; Body (JSON): {"Name": "Enterprise Sales"}. Check the Ploomes API docs for the exact pipeline fields.
Example 2: Create a pipeline whose name comes from an upstream node
Resource: Deal Pipeline; Operation: Create; Body (JSON) set as an expression, e.g. {"Name": "{{ $json.pipelineName }}"}. One pipeline is created for each incoming item.
