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 Type → Update
AI-generatedSummary
Updates an existing document type in LLW CRM by sending a PUT request to /document-types/{id} with the selected field values, and returns the API's response.
Inputs
- ID (required) — The ID of the document type to update. Used in the request path /document-types/{ID}.
- Fields to Update — Repeatable list of Field Name / Field Value pairs. The only selectable field is 'name'. Each value is sent as a string, but the node first tries JSON.parse on it (so a value like 123 or true is sent as a number or boolean). Pairs with an empty value are skipped. If none are provided, an empty body is sent.
Output shape
One item per input item, containing the JSON response from the LLW CRM API (typically the updated document type record).
Each output item is paired to its input item. With Continue On Fail enabled, a failed item returns {error: message} instead of stopping the workflow. The Manage Associations options are not offered for this resource, so no association calls are made.
Examples
Example 1: Rename a document type 'Contract' to 'Signed Contract'.
Resource: Document Type; Operation: Update; ID: 12; Fields to Update: Field Name = name, Field Value = Signed Contract.