The flow
Starts it 1Logic 13Service 4
The steps in the order they run, from what starts it.
- 1Execute Workflow TriggerExecute Workflow triggerStarts it
- 2Get transcriptHttp RequestService
- 3Retrieve detailed call dataHttp RequestService
- 4Join Transcript to StringSetLogic
- 5Extract Call DataSplit OutLogic
- 6Merge call and transcript DataMergeLogic
- 7Join AffiliationCodeLogic
- 8Join conversationCodeLogic
- 9Get External Attendees EmailsSetLogic
- 10Aggregate Gong Call TranscriptAggregateLogic
- 11Get Opp DataSalesforceService
- 12Merge Enriched Transcript DataMergeLogic
- 13Extract SF Opp DataSetLogic
- 14Get account dataSalesforceService
- 15Isolate Notion DataSetLogic
- 16Combine Salesforce Opp DataMergeLogic
- 17Extract SF Opp Data1SetLogic
- 18Aggregate Salesforce dataAggregateLogic
How it's built
- Starts on
- An event in a connected app
- Steps
- 18
- Size
- Medium: a working afternoon
- Connects to
- Salesforce
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Salesforce account. You connect your own accounts after importing it; none are included.
What starts it?
It starts on an event in a connected app.
Does it use AI?
No. Every step is fixed logic or a call to a service, so it does the same thing every time.
How long does it take to set up?
Plan an afternoon. 18 steps is enough that you should read each one before running it.
How do I import it?
Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.
Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 18 steps before you point it at anything that matters.