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
Call → Update
AI-generatedSummary
Updates an existing call record in LLW CRM by sending a PUT request to /calls/{ID} with only the fields you choose to change.
Inputs
- ID (required) — ID of the call record to update (used in the URL /calls/{ID}).
- Fields to Update — Repeatable list of Field Name / Field Value pairs. Field Name options: body, call_outcome_id, date, user_id, contacts, companies. Field Value is entered as a string. Pairs with an empty value are skipped. Each value is first parsed as JSON (so numbers, arrays like [1,2] or objects are sent as such) and falls back to the raw string if parsing fails. Unlike the Log operation, contacts/companies are not split from comma-separated text, so a value like 1,2 is sent as a string. Use JSON array syntax such as [1,2] instead.
Output shape
A single item containing the JSON response from the LLW CRM API for the updated call, paired to the input item.
If no fields are supplied, an empty body is still sent. Runs once per input item. With Continue On Fail enabled, a failed item returns {error: message} instead of stopping the workflow. The Manage Associations options do not apply to the Call resource, so no association calls are made.
Examples
Example 1: Change the outcome and notes of a logged call
ID = 42; Fields to Update: call_outcome_id = 3, body = 'Customer asked for a callback next week'.
Example 2: Reassign a call to a different contact
ID = {{$json.callId}}; Fields to Update: contacts = [15].