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
Order → Create
AI-generatedSummary
Create an order in Ploomes CRM by sending a JSON body to POST /Orders. Sends one request per incoming workflow item.
Inputs
- body — Order properties to send as JSON; defaults to {}. JSON strings are parsed before sending, while objects are used directly. The node does not define or validate individual order fields.
Output shape
API response data on the Success output, with separate Error and Timeout outputs.
If the response contains a value array, each element becomes a separate item; otherwise the response becomes one item. An empty response produces an item with success, resource, operation, and timestamp. Error items include error, statusCode, isTimeout, resource, operation, and timestamp. HTTP 408/504 errors go to Timeout; other errors go to Error only when Continue On Fail is enabled, otherwise execution throws.