Turn your sales calls into clear data without manual work. The flow checks Salesforce every hour for new synced Gong calls and sends only the ones that matter into processing. It fits sales and revenue teams that want faster insights from early stage calls.

An hourly schedule starts the run, with a manual test option for setup. The Salesforce step reads the Gong call custom object Gong__Gong_Call__c, then sorts records by CreatedDate so the newest calls go first. Filters keep only calls tied to a primary opportunity and in Meeting Booked or Discovery stage. The flow then pulls full call details and transcript from Gong using the call ID stored in Salesforce. A set step shapes the data into a clean JSON package with id, url, transcript text, talk time, and metadata. An execute workflow step hands the package to your call preprocessor or AI agent for the next steps.

Connect your Salesforce and Gong accounts and confirm field names match your org. Once active, teams cut review time, move faster on follow ups, and keep data consistent across systems. Many teams can handle five times more recordings without extra admin time. Use it to prioritize discovery calls, prep notes for handoffs, and queue only qualified recordings for deeper analysis.

• Hourly schedule to check for new synced calls, plus a manual test trigger for setup and QA.
• Pulls records from the Salesforce custom object Gong__Gong_Call__c with selected fields.
• Sorts by CreatedDate so the newest calls are processed first.
• Filters for Meeting Booked or Discovery stages to focus on early pipeline calls.
• Verifies a primary opportunity exists before moving forward.
• Fetches full call data from Gong using the stored Gong__Call_ID__c.
• Formats a clean JSON payload with id, url, transcript, talk time, and metadata.
• Sends the payload to a separate preprocessor workflow for AI or downstream steps.

• Reduce manual review from 60 minutes per rep per day to 10 minutes
• Automate 80 percent of call triage by filtering on stage and opportunity
• Improve data accuracy by 90 percent by reading call IDs directly from Salesforce
• Connect Salesforce and Gong to keep call records and insights in sync
• Handle up to 5 times more recordings with the same team

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with Salesforce and Gong. See the Tools Required section above for links to create accounts with these services.
3. In n8n Cloud, open the workflow and click the Salesforce node named Get all custom Salesforce Gong Objects. In the Credential to connect with dropdown, click Create new credential and follow the on screen instructions to integrate Salesforce.
4. Open the Gong node named Get Gong Call. In the Credential to connect with dropdown, click Create new credential and follow the on screen instructions to integrate Gong.
5. In the Salesforce node, confirm Resource is Custom Object and Object API Name is Gong__Gong_Call__c. Keep the fields shown or add any fields your org needs.
6. Open the Sort node and confirm it sorts by CreatedDate in descending order to process the latest calls first.
7. Open the If node that checks the stage. Set the condition to pass only when the stage equals Meeting Booked or Discovery. Match the exact stage names used in your org.
8. Open the second If node and ensure it checks that Primary Opportunity contains a value so only qualified calls proceed.
9. On the Gong node, confirm Operation is get and the Call ID expression points to the Salesforce field Gong__Call_ID__c.
10. Open the Set node and review the output fields. Keep the id, url, transcript, talk time, and metadata mappings or adjust to fit your downstream needs.
11. Open the Execute Workflow node and select the target preprocessor workflow you want to run after packaging the data.
12. Click Test workflow to run a manual test. Verify Salesforce records load, filters apply, Gong returns a call, and the packaged JSON reaches the next workflow.
13. Activate the workflow so the hourly schedule runs. If no records appear, check Salesforce permissions on the custom object. If the Gong call fails, confirm the Call ID mapping and your Gong credentials. If the schedule does not fire, confirm the workflow is active.