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
Contact Number of Employees → Update
AI-generatedSummary
Updates an existing Contact Number of Employees record in Ploomes CRM by sending a PATCH request to /Contacts@NumbersOfEmployees(ID).
Inputs
None.
Output shape
The API response JSON from the PATCH request is emitted on the Success output. If the API returns an empty body, the node emits a JSON object with success: true, resource, operation, and timestamp. Non-timeout errors are routed to the Error output; HTTP 408 and 504 responses are routed to the Timeout output.
This operation does not use OData query options or cache settings; those only apply to GetAll. The node does not validate the body fields, so use valid Ploomes fields for the Contact Number of Employees resource.