HumationHuman + Automation
Back to Catalog

CallForge - 04 - AI workflow for Gong.io sales calls

Angel MenendezAngel Menendez
2756 views
2/3/2026
Lead ManagementHubSpotAutomationSalesforceCRM
Official Page

callforgecompressed.png

CallForge - AI Gong Sales Call Processing Workflow

Automate your Gong.io sales call analysis with AI-driven insights, real-time tracking, and structured CRM integration.

Who is This For?

This workflow is designed for:
✅ Sales teams looking to automate sales call processing.
✅ Revenue operations (RevOps) professionals managing high volumes of call data.
✅ AI-driven sales intelligence teams using Gong.io for data-driven insights.

What Problem Does This Workflow Solve?

Manually managing and analyzing large volumes of Gong call data is time-consuming and error-prone.

With CallForge, you can:
✔ Automate call processing to scale AI-driven insights.
✔ Integrate with Notion to track and organize sales call data efficiently.
✔ Get real-time Slack updates to stay informed on call processing progress.
✔ Handle API failures gracefully, allowing easy reruns if a rate limit is hit.
✔ Ensure AI-ready analysis, feeding structured call data into an AI-powered system.

What This Workflow Does

1. Triggers on New Gong Calls

  • Captures new Gong calls and retrieves metadata, call summaries, and participant details.

2. Compares Calls Against Notion Database

  • Checks whether the call has already been processed and stored in Notion.
  • Prevents duplicate entries from being added.

3. Creates a Parent Notion Record for AI Processing

  • Stores call details such as date, title, URL, company name, sales rep, and opportunity details in Notion.
  • Links calls to Salesforce Opportunity (SF Opp) data.
  • Assigns sales representatives and customer information to each call.

4. Loops Through Calls for Processing

  • Ensures resilience by allowing failed runs to restart where they left off.
  • Processes calls one at a time to prevent Notion rate limits.

5. Sends Call Data to an AI Processor

  • Extracts structured call details and sends them to an AI-powered analysis workflow.
  • Allows multiple AI agents to process and extract structured data from calls.

6. Provides Real-Time Slack Alerts

  • Posts a progress update in Slack when the queue starts processing.
  • Sends real-time call progress notifications.
  • Sends a completion alert once all calls are processed.

How to Set Up This Workflow

1. Connect Your APIs

🔹 Gong API Credentials – Ensure you have valid Gong API credentials in n8n.
🔹 Notion Database – Provide access to a Notion database for storing call insights.
🔹 Slack Integration – Configure a Slack channel for progress alerts.
🔹 AI Processing Workflow – Connect an AI-powered call processing workflow for final analysis.

How to Customize This Workflow

💡 Modify Call Storage – Swap Notion for a different CRM or database (e.g., HubSpot, Airtable, Salesforce).
💡 Change AI Processing – Integrate a custom AI model for analyzing sales conversations.
💡 Customize Slack Notifications – Adjust Slack messages or send alerts via email instead.
💡 Expand with More Integrations – Connect with Salesforce, Pipedrive, or HubSpot for further enrichment.

Why Use CallForge?

🚀 Automate Gong call tracking for seamless sales intelligence.
📊 Improve sales operations with structured, AI-powered insights.
⚡ Get real-time updates and keep your team informed instantly.

Start optimizing your Gong call processing today!

n8n Workflow: 3034-callforge---04---ai-workflow-for-gongio-sales-calls

This n8n workflow is a placeholder or a template, as its current JSON definition contains only core n8n nodes without any specific configuration or connections. It showcases a collection of fundamental n8n functionalities that could be used as building blocks for a more complex automation related to AI workflows for sales calls, potentially integrating with platforms like Gong.io, as suggested by the directory name.

What it does

Based on the provided JSON, this workflow currently includes the following core n8n nodes, indicating potential areas of functionality:

  1. Merge: For combining data from multiple sources or paths within the workflow.
  2. No Operation, do nothing: A placeholder node that passes data through without modification, often used for debugging or as a temporary endpoint.
  3. Edit Fields (Set): For adding, modifying, or removing fields (data properties) in the incoming items.
  4. Loop Over Items (Split in Batches): To process items in batches or iterate over a list of items, allowing for individual processing of each item.
  5. Slack: To interact with Slack, potentially sending messages, alerts, or notifications.
  6. Execute Sub-workflow: To call and execute another n8n workflow as a sub-process, promoting modularity.
  7. Notion: To interact with Notion, likely for creating, updating, or querying database items or pages.
  8. Sticky Note: A visual aid within the workflow for adding comments or documentation.
  9. Compare Datasets: To compare two sets of data, identifying differences or commonalities.
  10. Execute Workflow Trigger: A trigger node specifically designed to be activated by an "Execute Sub-workflow" node from another workflow.
  11. Aggregate: To combine multiple items into a single item or to perform aggregation operations on data.

Prerequisites/Requirements

While the workflow itself doesn't have explicit configurations, a fully functional version of this workflow would likely require:

  • n8n Instance: A running n8n instance to import and execute the workflow.
  • Slack Account: If the Slack node is configured to send messages or interact with channels.
  • Notion Account: If the Notion node is configured to interact with Notion databases or pages.
  • OpenAI API Key / AI Service Credentials: (Inferred from directory name "ai-workflow") If AI capabilities are to be integrated, credentials for an AI service (e.g., OpenAI, Google AI, etc.) would be necessary.
  • Gong.io API Access: (Inferred from directory name "gongio-sales-calls") If integrating with Gong.io, appropriate API access and credentials would be required.

Setup/Usage

  1. Import the workflow: Download the provided JSON and import it into your n8n instance.
  2. Configure Credentials: If you plan to use the Slack or Notion nodes, you will need to set up the respective credentials in n8n.
  3. Develop Specific Logic: This workflow currently serves as a blueprint. To make it functional for "AI workflow for Gong.io sales calls," you would need to:
    • Add a trigger node (e.g., Webhook, Schedule, or Gong.io specific trigger if available) to start the workflow.
    • Configure the "Edit Fields (Set)" and "Loop Over Items" nodes with the specific data transformation and iteration logic required for your use case.
    • Integrate AI nodes (e.g., OpenAI, Hugging Face) to process sales call data (e.g., transcription analysis, sentiment analysis, lead scoring).
    • Configure the "Slack" and "Notion" nodes to post results, notifications, or update records based on the AI analysis.
    • Utilize "Merge" and "Compare Datasets" for advanced data handling and synchronization if needed.
    • If using sub-workflows, ensure they are properly configured and linked via "Execute Sub-workflow" and "Execute Workflow Trigger" nodes.
  4. Activate the Workflow: Once configured, activate the workflow in n8n to enable its automation.

Related Templates

Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets

This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.

Ranjan DailataBy Ranjan Dailata
161

Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax

Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions

Daniel NkenchoBy Daniel Nkencho
601

Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation

PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.

Le NguyenBy Le Nguyen
942