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
Document → Update
AI-generatedSummary
Updates an existing Ploomes document by ID using a PATCH request.
Inputs
- ID (required) — The ID of the document to update in Ploomes CRM.
- Body (JSON) — JSON object containing the document fields to change. Sent as the PATCH request body.
Output shape
API response from Ploomes CRM
For each incoming item, the node sends a PATCH request to https://api2.ploomes.com/Documents(ID). If the API response has a value array, each element is emitted as a separate output item; otherwise the response object is emitted. If the response body is empty, a success object with success:true is returned.