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
Company → Update
AI-generatedSummary
Updates an existing company in LLW CRM by sending a PUT to /companies/{id} with the selected field/value pairs, and can optionally attach, detach or sync associations afterwards.
Inputs
- ID (required) — ID of the company to update (resourceId); used in the request path /companies/{id}.
- Fields to Update — Repeatable list of Field Name / Field Value pairs. Field names: name, email, domain, phones, industry_id, source_id, user_id, employees. Values are entered as strings; each is first parsed as JSON (so numbers, arrays or objects such as a phones array work) and falls back to the raw string. Empty values are skipped, so a field can't be cleared this way.
- Manage Associations — Toggle (default false). When on, an extra association request is sent after the update.
- Association Operation — Attach (add without removing), Detach (remove specific) or Sync (replace all). Shown only when Manage Associations is on. Default is attach.
- Associations — JSON object of IDs by type, e.g. {"companies":[1,2],"contacts":[1,2]}. Shown only when Manage Associations is on. Sent as the body of the association request.
Output shape
One item per input item, containing the JSON response from the company update call (the updated company record as returned by the API).
If associations are managed, the association call is made to /companies/{id}/associations/{attach|detach|sync} (DELETE for detach, POST otherwise), but its response is discarded. The output is only the update response. Association is skipped if the update fails. With Continue On Fail enabled, errors are returned as {error: message} for that item. If no valid fields are provided, an empty body is still sent.
Examples
Example 1: Change a company's domain and employee count
ID = 42; Fields to Update: domain = example.com, employees = 250.
Example 2: Replace a company's phone numbers
ID = 42; Field Name phones, Field Value [{"type":"work","number":"+15551234567"}].
Example 3: Update owner and link contacts
ID from the previous node; user_id = 7; Manage Associations on, Association Operation Attach, Associations {"contacts":[11,12]}.