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
Source → Update or Create
AI-generatedSummary
Offered in the UI for the Source resource, but the source code has no handler for it. The execute logic only implements Update or Create for the Contact resource, so running it on Source makes no API call and returns the item with an empty or undefined json.
Inputs
- Name — No Source-specific fields are declared for this operation. The Name field is only shown for the Create operation, since Update or Create is only wired up for Contact. The shared 'Manage Associations' options are shown only for contact, company, deal, activity and document, not Source.
Output shape
No meaningful data. For Source, no branch in execute matches, so responseData stays undefined. The node pushes one item per input with json set to undefined, which n8n may reject or show as empty.
No HTTP request is sent to /sources. To upsert sources, use Create or Update with a record ID, or a Search followed by an IF node. Enabling Continue On Fail does not help, because nothing throws.
Examples
Example 1: Attempting to upsert a lead source by name
Resource: Source, Operation: Update or Create. Don't use this. Combine Search (Source) with Create or Update instead.