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 → Win
AI-generatedSummary
Mark an existing Ploomes CRM deal as won by sending a POST request to /Deals({ID})/Win for each incoming item.
Inputs
- resourceId (required) — Required ID of the deal to mark as won.
Output shape
API response data on the Success output, or a success confirmation if the response is empty.
An API response containing a value array is split into separate items; otherwise the response is returned as one item. Empty responses produce success, resource, operation, and timestamp fields. HTTP 408 and 504 errors go to Timeout. Other errors go to Error when Continue On Fail is enabled; otherwise execution throws. Error items contain error, statusCode, isTimeout, resource, operation, and timestamp.