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 Type → Update
AI-generatedSummary
Updates an existing activity type in LLW CRM by sending a PUT request to /activity-types/{id} with the selected name and/or icon values.
Inputs
- ID (required) — ID of the activity type to update. It is placed in the request path (/activity-types/{ID}).
- Fields to Update — Repeatable list of field/value pairs. Field Name is either 'name' or 'icon'. Field Value is a string. Pairs with an empty value are skipped. Each value is parsed as JSON where possible and otherwise sent as a plain string, so a value like 123 or true is sent as a number or boolean.
Output shape
A single item containing the JSON response from the LLW CRM API, which is normally the updated activity type record.
The response is passed through unchanged. If no valid field pairs are given, an empty body is sent. If Continue On Fail is enabled, a failed item returns {error: message} instead of stopping the run. The same node also shows 'Manage Associations' options for some resources, but the source only applies them to contact, company, deal, activity and document, so they have no effect for activity types.
Examples
Example 1: Rename an activity type
ID = 5; Fields to Update: Field Name = name, Field Value = 'Site Visit'.
Example 2: Change name and icon together
ID from a previous node via expression; add two field entries: name = 'Demo', icon = 'video'.