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
Activity → Update
AI-generatedSummary
Updates an existing LLW CRM activity by ID with a PUT to /activities/{id}, sending only the field/value pairs you choose. It can optionally attach, detach, or sync associations afterward.
Inputs
- resourceId (required) — ID of the activity to update. Used in the request path /activities/{id}.
- fieldsToUpdate — Repeatable list of Field Name and Field Value pairs. Field names are title, activity_type_id, due_date, due_time, description, is_completed, user_id, contacts, companies and deals. Each value is first parsed as JSON, so true, 12 or [1,2] become a boolean, number or array. If parsing fails, the raw string is sent. Empty values are skipped. Unlike create, comma-separated IDs for contacts, companies and deals are not split into arrays. Pass them as JSON, e.g. [1,2].
- manageAssociations — Boolean, default false. When true, a second association request is sent after the update.
- associationOperation — Attach, Detach or Sync. Shown only when Manage Associations is on. Default is attach.
- associations — JSON object of IDs, e.g. {"companies":[1,2],"contacts":[1,2]}. It is sent as the body of the association request.
Output shape
One item per input item, containing the JSON response from the activity update request.
The association call's response is discarded, so the output shows only the update response. Association calls go to /activities/{id}/associations/{attach|detach|sync}. Detach uses DELETE and the others use POST. With Continue On Fail enabled, a failed item returns {error: message}. Otherwise the node throws.
Examples
Example 1: Mark an activity as completed
ID = 42; Fields to Update: is_completed = true
Example 2: Reschedule and retitle an activity
ID from an earlier node; fields: due_date = 2026-11-01, due_time = 14:30:00, title = Follow-up call
Example 3: Link an activity to extra contacts and a deal without removing existing links
ID = 42; Manage Associations on; Association Operation = Attach; Associations = {"contacts":[5,6],"deals":[9]}