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 Outcome → Update or Create
AI-generatedSummary
Selectable for Call Outcome in the UI, but the node's execute logic has no handler for it. The updateOrCreate branch runs only for the Contact resource, so no API request is made and the output is probably not useful.
Inputs
- (none) — No operation-scoped parameters are declared for Call Outcome + Update or Create. The Name field is only shown for the create and log operations, and the Fields to Update collection only for update. The Manage Associations options are not shown for Call Outcome.
Output shape
One output item per input item, with json set to an undefined response. In practice this is an empty item, since no API call is made.
The execute code only implements updateOrCreate when resource is contact (search by email, name or phone, then PUT or POST). For callOutcome none of the operation branches match, so responseData stays undefined. Use the Create or Update operations for call outcomes instead (endpoint /call-outcomes).
Examples
Example 1: Upsert a call outcome by name
Not supported. Use Search to check whether the outcome exists, then Create or Update (with the record ID) on Call Outcome.