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
User → Create
AI-generatedSummary
Create a Ploomes CRM user by posting the supplied JSON properties to /Users, once per incoming workflow item.
Inputs
- body — JSON containing the user properties to send. Defaults to {}; accepts a JSON string or object. The node does not define or validate individual user fields.
Output shape
API response data on the Success output, with each entry in a response value array emitted as a separate item; otherwise, a single response item.
An empty response produces 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.