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 → Create
AI-generatedSummary
Create a deal in Ploomes CRM by posting the supplied JSON to /Deals, once per incoming item.
Inputs
- body — Body (JSON) containing the deal properties to send. Defaults to {}. JSON strings are parsed; objects are sent directly. The node does not declare or validate individual deal fields.
Output shape
API response data on the Success output, as one item or multiple items if the response contains a value array.
A value array is unwrapped into separate items; other responses are returned directly. An empty response produces success, resource, operation, and timestamp fields. HTTP 408 and 504 errors go to Timeout. Other failures go to Error when Continue On Fail is enabled; otherwise execution throws. Error items contain error, statusCode, isTimeout, resource, operation, and timestamp.