CallForge - 03 - Gong transcript processor and Salesforce enricher
CallForge - AI Gong Transcript PreProcessor
Transform your Gong.io call transcripts into structured, enriched, and AI-ready data for better sales insights and analytics.
Who is This For?
This workflow is designed for:
✅ Sales teams looking to automate call transcript formatting.
✅ Revenue operations (RevOps) professionals optimizing AI-driven insights.
✅ Businesses using Gong.io that need structured, enriched call transcripts for better decision-making.
What Problem Does This Workflow Solve?
Manually processing raw Gong call transcripts is inefficient and often lacks essential context for AI-driven insights.
With CallForge, you can:
✔ Extract and format Gong call transcripts for structured AI processing.
✔ Enhance metadata using sales data from Salesforce.
✔ Classify speakers as internal (sales team) or external (customers).
✔ Identify external companies by filtering out free email domains (e.g., Gmail, Yahoo).
✔ Enrich customer profiles using PeopleDataLabs to identify company details and locations.
✔ Prepare transcripts for AI models by structuring conversations and removing unnecessary noise.
What This Workflow Does
1. Retrieves Gong Call Data
- Calls the Gong API to extract call metadata, speaker interactions, and collaboration details.
- Fetches call transcripts for AI processing.
2. Processes and Cleans Transcripts
- Converts call transcripts into structured, speaker-based dialogues.
- Assigns each speaker as either Internal (Sales Team) or External (Customer).
3. Extracts Company Information
- Retrieves Salesforce data to match customers with existing sales opportunities.
- Filters out free email domains to determine the customer’s actual company domain.
- Calls the PeopleDataLabs API to retrieve additional company data and location details.
4. Merges and Enriches Data
- Combines Gong metadata, Salesforce customer details and insights.
- Ensures all necessary data is available for AI-driven sales insights.
5. Final Formatting for AI Processing
- Merges all call transcript data into a single structured format for AI analysis.
- Extracts the final cleaned, enriched dataset for further AI-powered insights.
How to Set Up This Workflow
1. Connect Your APIs
🔹 Gong API Access – Set up your Gong API credentials in n8n.
🔹 Salesforce Setup – Ensure API access if you want customer enrichment.
🔹 PeopleDataLabs API – Required to retrieve company and location details based on email domains.
🔹 Webhook Integration – Modify the webhook call to push enriched call data to an internal system.
- CallForge - 01 - Filter Gong Calls Synced to Salesforce by Opportunity Stage
- CallForge - 02 - Prep Gong Calls with Sheets & Notion for AI Summarization
- CallForge - 03 - Gong Transcript Processor and Salesforce Enricher
- CallForge - 04 - AI Workflow for Gong.io Sales Calls
- CallForge - 05 - Gong.io Call Analysis with Azure AI & CRM Sync
- CallForge - 06 - Automate Sales Insights with Gong.io, Notion & AI
- CallForge - 07 - AI Marketing Data Processing with Gong & Notion
- CallForge - 08 - AI Product Insights from Sales Calls with Notion
How to Customize This Workflow
💡 Modify Data Sources – Connect different CRMs (e.g., HubSpot, Zoho) instead of Salesforce.
💡 Expand AI Analysis – Add another AI model (e.g., OpenAI GPT, Claude) for advanced conversation insights.
💡 Change Speaker Classification Rules – Adjust internal vs. external speaker logic to match your team’s structure.
💡 Filter Specific Customers – Modify the free email filtering logic to better fit your company’s needs.
Why Use CallForge?
🚀 Automate Gong call transcript processing to save time.
📊 Improve AI accuracy with enriched, structured data.
🛠 Enhance sales strategy by extracting actionable insights from calls.
Start optimizing your Gong transcript analysis today!
Gong Transcript Processor and Salesforce Enricher
This n8n workflow processes Gong call transcripts, extracts relevant information, and enriches Salesforce records. It's designed to automate the post-call analysis and CRM update process, ensuring sales data is consistently updated with valuable insights from customer interactions.
What it does
This workflow is triggered by an external system (likely another n8n workflow or a webhook) that provides Gong call data. It then performs the following key steps:
- Receives Gong Call Data: Listens for incoming data, specifically expecting a
transcriptfield containing the call's full transcript and acallIdfor identification. - Extracts Key Information: Uses a Code node to process the raw transcript. This node is responsible for extracting structured data such as:
customerPainPoints: Identified pain points mentioned by the customer.customerNeeds: Specific needs expressed by the customer.nextSteps: Agreed-upon next steps from the call.sentiment: The overall sentiment of the call.summary: A concise summary of the call.actionItems: Any action items arising from the discussion.
- Transforms Data:
- The
Edit Fields (Set)node likely standardizes or renames fields for consistency. - The
Split Outnode prepares the extracted data for individual processing or merging.
- The
- Aggregates Data: The
Aggregatenode combines various pieces of extracted and transformed data into a unified structure. - Enriches Salesforce: The final
Salesforcenode takes the processed and aggregated data to update or create records in Salesforce, linking the call insights to relevant opportunities, contacts, or accounts.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running instance of n8n.
- Gong Integration (External): An external mechanism (e.g., another n8n workflow, a webhook from Gong) that triggers this workflow with Gong call transcript data. This workflow expects
transcriptandcallIdfields. - Salesforce Account: Access to a Salesforce instance with appropriate permissions to create/update records.
- Salesforce n8n Credential: An n8n credential configured for your Salesforce account.
- Custom Code Logic: The
Codenode requires custom JavaScript logic to parse and extract specific information from the Gong transcript. This logic needs to be tailored to your specific extraction requirements (e.g., using regex, NLP libraries, or external AI services if integrated within the code).
Setup/Usage
- Import the Workflow: Import the provided JSON into your n8n instance.
- Configure Credentials:
- Set up your Salesforce credential within n8n.
- Customize Code Node:
- Open the
Codenode and review its JavaScript logic. You will need to implement the actual parsing and extraction ofcustomerPainPoints,customerNeeds,nextSteps,sentiment,summary, andactionItemsfrom the incomingtranscriptdata. This might involve calling an external AI service (like OpenAI) or using local string processing.
- Open the
- Configure Salesforce Node:
- Open the
Salesforcenode and configure the operation (e.g., "Update Record", "Create Record"). - Map the fields from the previous nodes (e.g.,
customerPainPoints,summary,callId) to the corresponding fields in your Salesforce objects (e.g., Opportunity, Task, Call Log). Ensure thecallIdis used to identify or link to the correct Salesforce record.
- Open the
- Activate the Workflow: Once configured, activate the workflow.
- Trigger the Workflow: Ensure your external Gong integration is set up to send call transcript data to this workflow's
Execute Workflow Triggernode. The incoming data should contain at least atranscriptand acallIdfield.
Related Templates
Send WooCommerce cross-sell offers to customers via WhatsApp using Rapiwa API
Who Is This For? This n8n workflow enables automated cross-selling by identifying each WooCommerce customer's most frequently purchased product, finding a related product to recommend, and sending a personalized WhatsApp message using the Rapiwa API. It also verifies whether the user's number is WhatsApp-enabled before sending, and logs both successful and unsuccessful attempts to Google Sheets for tracking. What This Workflow Does Retrieves all paying customers from your WooCommerce store Identifies each customer's most purchased product Finds the latest product in the same category as their most purchased item Cleans and verifies customer phone numbers for WhatsApp compatibility Sends personalized WhatsApp messages with product recommendations Logs all activities to Google Sheets for tracking and analysis Handles both verified and unverified numbers appropriately Key Features Customer Segmentation: Automatically identifies paying customers from your WooCommerce store Product Analysis: Determines each customer's most purchased product Smart Recommendations: Finds the latest products in the same category as customer favorites WhatsApp Integration: Uses Rapiwa API for message delivery Phone Number Validation: Verifies WhatsApp numbers before sending messages Dual Logging System: Tracks both successful and failed message attempts in Google Sheets Rate Limiting: Uses batching and wait nodes to prevent API overload Personalized Messaging: Includes customer name and product details in messages Requirements WooCommerce store with API access Rapiwa account with API access for WhatsApp verification and messaging Google account with Sheets access Customer phone numbers in WooCommerce (stored in billing.phone field) How to Use — Step-by-Step Setup Credentials Setup WooCommerce API: Configure WooCommerce API credentials in n8n (e.g., "WooCommerce (get customer)" and "WooCommerce (get customer data)") Rapiwa Bearer Auth: Create an HTTP Bearer credential with your Rapiwa API token Google Sheets OAuth2: Set up OAuth2 credentials for Google Sheets access Configure Google Sheets Ensure your sheet has the required columns as specified in the Google Sheet Column Structure section Verify Code Nodes Code (get paying_customer): Filters customers to include only those who have made purchases Get most buy product id & Clear Number: Identifies the most purchased product and cleans phone numbers Configure HTTP Request Nodes Get customer data: Verify the WooCommerce API endpoint for retrieving customer orders Get specific product data: Verify the WooCommerce API endpoint for product details Get specific product recommend latest product: Verify the WooCommerce API endpoint for finding latest products by category Check valid WhatsApp number Using Rapiwa: Verify the Rapiwa endpoint for WhatsApp number validation Rapiwa Sender: Verify the Rapiwa endpoint for sending messages Google Sheet Required Columns You’ll need two Google Sheets (or two tabs in one spreadsheet): A Google Sheet formatted like this ➤ sample The workflow uses a Google Sheet with the following columns to track coupon distribution: Both must have the following headers (match exactly): | name | number | email | address1 | price | suk | title | product link | validity | staus | | ---------- | ------------- | ----------------------------------------------- | ----------- | ----- | --- | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------- | -------- | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | unverified | not sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | Important Notes Phone Number Format: The workflow cleans phone numbers by removing all non-digit characters. Ensure your WooCommerce phone numbers are in a compatible format. API Rate Limits: Rapiwa and WooCommerce APIs have rate limits. Adjust batch sizes and wait times accordingly. Data Privacy: Ensure compliance with data protection regulations when sending marketing messages. Error Handling: The workflow logs unverified numbers but doesn't have extensive error handling. Consider adding error notifications for failed API calls. Product Availability: The workflow recommends the latest product in a category, but doesn't check if it's in stock. Consider adding stock status verification. Testing: Always test with a small batch before running the workflow on your entire customer list. Useful Links Dashboard: https://app.rapiwa.com Official Website: https://rapiwa.com Documentation: https://docs.rapiwa.com Support & Help WhatsApp: Chat on WhatsApp Discord: SpaGreen Community Facebook Group: SpaGreen Support Website: https://spagreen.net Developer Portfolio: Codecanyon SpaGreen
Track SDK documentation drift with GitHub, Notion, Google Sheets, and Slack
📊 Description Automatically track SDK releases from GitHub, compare documentation freshness in Notion, and send Slack alerts when docs lag behind. This workflow ensures documentation stays in sync with releases, improves visibility, and reduces version drift across teams. 🚀📚💬 What This Template Does Step 1: Listens to GitHub repository events to detect new SDK releases. 🧩 Step 2: Fetches release metadata including version, tag, and publish date. 📦 Step 3: Logs release data into Google Sheets for record-keeping and analysis. 📊 Step 4: Retrieves FAQ or documentation data from Notion. 📚 Step 5: Merges GitHub and Notion data to calculate documentation drift. 🔍 Step 6: Flags SDKs whose documentation is over 30 days out of date. ⚠️ Step 7: Sends detailed Slack alerts to notify responsible teams. 🔔 Key Benefits ✅ Keeps SDK documentation aligned with product releases ✅ Prevents outdated information from reaching users ✅ Provides centralized release tracking in Google Sheets ✅ Sends real-time Slack alerts for overdue updates ✅ Strengthens DevRel and developer experience operations Features GitHub release trigger for real-time monitoring Google Sheets logging for tracking and auditing Notion database integration for documentation comparison Automated drift calculation (days since last update) Slack notifications for overdue documentation Requirements GitHub OAuth2 credentials Notion API credentials Google Sheets OAuth2 credentials Slack Bot token with chat:write permissions Target Audience Developer Relations (DevRel) and SDK engineering teams Product documentation and technical writing teams Project managers tracking SDK and doc release parity Step-by-Step Setup Instructions Connect your GitHub account and select your SDK repository. Replace YOURGOOGLESHEETID and YOURSHEET_GID with your tracking spreadsheet. Add your Notion FAQ database ID. Configure your Slack channel ID for alerts. Run once manually to validate setup, then enable automation.
Automate Gmail responses with GPT and human-in-the-loop verification
Try It Out! This n8n template uses AI to automatically respond to your Gmail inbox by drafting response for your approval via email. How it works Gmail Trigger monitors your inbox for new emails AI Analysis determines if a response is needed based on your criteria Draft Generation creates contextually appropriate replies using your business information Human Approval sends you the draft for review before sending Auto-Send replies automatically once approved Setup Connect your Gmail account to the Gmail Trigger node Update the "Your Information" node with: Entity name and description Approval email address Resource guide (FAQs, policies, key info) Response guidelines (tone, style, formatting preferences) Configure your LLM provider (OpenAI, Claude, Gemini, etc.) with API credentials Test with a sample email Requirements n8n instance (self-hosted or cloud) Gmail account with API access LLM provider API key Need Help? Email Nick @ nick@tropicflare.com