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 Origin → Update
AI-generatedSummary
Update an existing contact origin in Ploomes CRM by sending a PATCH request to /Contacts@Origins(ID) with the supplied JSON properties.
Inputs
- resourceId (required) — ID of the contact origin to update.
- body — JSON properties to send in the update request. Defaults to {}; JSON strings are parsed before sending. The node does not define individual entity fields.
Output shape
API response data on the Success output, or a success confirmation when the response has no body.
An API value array is emitted as separate items; other response data is emitted 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 stops. Error items include error, statusCode, isTimeout, resource, operation, and timestamp.