Actions134
- Activity Actions
- Activity Type Actions
- Call Actions
- Call Outcome Actions
- Comment Actions
- Company Actions
- Contact Actions
- Country Actions
- Currency Actions
- Deal Actions
- Document Actions
- Document Type Actions
- Industry Actions
- Note Actions
- Pipeline Actions
- Pipeline Stage Actions
- Product Actions
- Role Actions
- Source Actions
- Team Actions
- Timezone Actions
- Trashed Record Actions
- User Actions
Document → Update
AI-generatedSummary
Updates an existing LLW CRM document by ID via PUT /documents/{id}, sending only the field/value pairs you choose, and optionally attaches, detaches, or syncs associations with contacts, companies and deals.
Inputs
- ID (required) — ID of the document to update (resourceId). Used in the request path /documents/{id}.
- Fields to Update — Repeatable list of Field Name / Field Value pairs. Field Name is one of title, document_type_id, description, user_id, contacts, companies, deals. Each value is tried as JSON first (so numbers, arrays like [1,2] and booleans are parsed) and otherwise sent as a plain string. Empty values are skipped. Unlike create, comma-separated ID strings are not converted to arrays, so use JSON arrays such as [1,2] for contacts, companies and deals.
- Manage Associations — Toggle (default false). When on, a second API call is made after the update to change associations.
- Association Operation — Attach (add without removing), Detach (remove the listed ones) or Sync (replace all). Shown only when Manage Associations is on.
- Associations — JSON object of IDs by type, e.g. {"companies":[1,2],"contacts":[1,2]}. It is sent as the request body to /documents/{id}/associations/{operation}. Shown only when Manage Associations is on.
Output shape
One item per input item, containing the JSON response of the document PUT request (the updated document record as returned by the API).
The association call's response is discarded, so the output reflects only the field update. Detach uses the DELETE method and attach/sync use POST. If no fields are given, an empty body is still sent. With Continue On Fail enabled, a failed item outputs {error: message}. Otherwise the node throws.
Examples
Example 1: Rename a document and change its description
ID = 42; Fields to Update: title = "Q3 Proposal", description = "Revised pricing"; Manage Associations off.
Example 2: Link a document to extra contacts without removing existing links
ID = 42; Manage Associations on; Association Operation = Attach; Associations = {"contacts":[5,6]}.
Example 3: Reassign a document to another user and replace its deals
ID from the previous node; Fields to Update: user_id = 3; Manage Associations on; Operation = Sync; Associations = {"deals":[10]}.