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
Team → Update or Create
AI-generatedSummary
Selectable for the Team resource in the UI, but the node's execute logic only implements Update or Create for the Contact resource. For Team it matches no branch, so no API call is made and the item is passed through with an empty result.
Inputs
- Resource / Operation (required) — Team with Update or Create. No operation-specific parameters are shown for this combination. The Name field is only displayed for Create, and ID/Fields to Update only for Update.
- Manage Associations — Shown in the UI only for contact, company, deal, activity and document resources, so it is not offered for Team.
Output shape
No meaningful data. No request is sent to the CRM, and the responseData variable is never assigned for this combination. Each input item yields an output item with an undefined/empty json, paired to its input item.
The operation fails silently. Nothing is created or updated in LLW CRM. To manage teams, use the Team Create operation (POST /teams with Name) or Update (PUT /teams/{id} with Fields to Update). The Update or Create logic exists only for Contact, where it searches by email, name or phone.
Examples
Example 1: Attempting to upsert a team by name
Resource: Team, Operation: Update or Create. The node makes no API call and does nothing. Use Create or Update instead.