HumationHuman + Automation
Back to Catalog

CallForge - 06 - Automate sales insights with Gong.io, Notion & AI

Angel MenendezAngel Menendez
1920 views
2/3/2026
Daily DigestEmail AutomationSales ReportShopifyE-commerce
Official Page

callforgecompressed.png

CallForge - AI-Powered Sales Call Data Processor

Automate sales call analysis and store structured insights in Notion with AI-powered intelligence.

Who is This For?

This workflow is ideal for:
✅ Sales teams looking to automate call insight processing.
✅ Sales operations managers managing AI-driven call analysis.
✅ Revenue teams using Gong, Fireflies.ai, Otter.ai, or similar transcription tools.

It streamlines sales call intelligence, ensuring that insights such as competitor mentions, objections, and customer pain points are efficiently categorized and stored in Notion for easy access.

🔍 What Problem Does This Workflow Solve?

Manually reviewing and documenting sales call takeaways is time-consuming and error-prone.

With CallForge, you can:
✔ Identify competitors mentioned in sales calls.
✔ Capture objections and customer pain points for follow-up.
✔ Track sales call outcomes and categorize insights automatically.
✔ Store structured sales intelligence in Notion for future reference.
✔ Improve sales strategy with AI-driven, automated call analysis.

📌 Key Features & Workflow Steps

🎙️ AI-Powered Call Data Processing

This workflow processes AI-generated sales call insights and structures them in Notion databases:

  1. Triggers automatically when AI call analysis data is received.
  2. Extracts competitor mentions from the call transcript and logs them in Notion.
  3. Identifies and categorizes sales objections for better follow-ups.
  4. Processes integration mentions, capturing tools or platforms referenced in the call.
  5. Extracts customer use cases, categorizing pain points and feature requests.
  6. Aggregates all extracted insights and updates relevant Notion databases.

📊 Notion Database Integration

  • Competitors → Logs mentioned competitors for sales intelligence.
  • Objections → Tracks and categorizes common objections from prospects.
  • Integrations → Captures third-party tools & platforms discussed in calls.
  • Use Cases → Stores customer challenges & product feature requests.

🛠 How to Set Up This Workflow

1. Prepare Your AI Call Analysis Data

  • Ensure AI-generated sales call data is passed into the workflow.
  • Compatible with Gong, Fireflies.ai, Otter.ai, and other AI transcription tools.

2. Connect Your Notion Database

  • Set up Notion databases for:
    🔹 Competitors (tracks competing products)
    🔹 Objections (logs customer objections & concerns)
    🔹 Integrations (captures mentioned platforms & tools)
    🔹 Use Cases (categorizes customer pain points & feature requests)

3. Configure n8n API Integrations

🔧 How to Customize This Workflow

💡 Modify Notion Data Structure – Adjust fields to match your company’s CRM setup.
💡 Enhance AI Data Processing – Align fields with different AI transcription providers.
💡 Expand with CRM Integration – Sync insights with HubSpot, Salesforce, or Pipedrive.
💡 Add Notifications – Send alerts via Slack, email, or webhook when key competitor mentions or objections are detected.

⚙️ Key Nodes Used in This Workflow

🔹 If Nodes – Checks if AI-generated data includes competitors, integrations, objections, or use cases.
🔹 Notion Nodes – Creates or updates entries in Notion databases.
🔹 Split Out & Aggregate Nodes – Processes multiple insights and consolidates AI outputs.
🔹 Wait Nodes – Ensures smooth sequencing of API calls and database updates.
🔹 HTTP Request Node – Sends AI-extracted insights to Notion for structured storage.

🚀 Why Use This Workflow?

✔ Eliminates manual data entry and speeds up sales intelligence processing.
✔ Ensures structured and categorized sales insights for decision-making.
✔ Improves team collaboration with AI-powered competitor tracking & objections logging.
✔ Seamlessly integrates with Notion to centralize and manage sales call insights.
✔ Scalable for teams using n8n Cloud or self-hosted deployments.

This workflow empowers sales teams with automated AI insights, streamlining sales strategy and follow-ups with minimal effort. 🚀

Automate Sales Insights with Gong.io, Notion & AI

This n8n workflow streamlines the process of extracting and summarizing key sales insights from Gong.io call transcripts, enriching them with AI, and organizing them in Notion. It helps sales teams quickly identify critical moments, understand customer sentiment, and track important details from their calls.

What it does

  1. Triggers on Demand: The workflow is manually executed or called by another workflow, allowing for flexible integration into existing processes.
  2. Fetches Call Data from Gong.io: It makes an API request to Gong.io to retrieve details about a specific call, including its transcript.
  3. Extracts Key Information: It processes the Gong.io response to isolate the call ID, transcript, and other relevant metadata.
  4. Generates AI Summary: It sends the call transcript to an AI service (like OpenAI, though not explicitly defined in this JSON, implied by the "AI" in the directory name) to generate a concise summary of the call.
  5. Extracts Action Items: It uses AI to identify and list any action items mentioned in the call transcript.
  6. Extracts Next Steps: It uses AI to determine and list the next steps discussed during the call.
  7. Extracts Sentiment: It uses AI to analyze the overall sentiment of the call (e.g., positive, negative, neutral).
  8. Extracts Objections: It uses AI to identify and list any objections raised by the customer during the call.
  9. Creates Notion Page: It then creates a new page in a specified Notion database, populating it with the call details, AI-generated summary, action items, next steps, sentiment, and objections.
  10. Waits for Processing: Includes a "Wait" step, likely to ensure Notion has time to process the initial page creation before any subsequent updates or to pace API requests.
  11. Aggregates Data (if multiple items): If multiple items are processed (e.g., multiple calls), it aggregates them into a single structure.
  12. Splits Out Data (if needed): If the aggregated data needs to be processed individually again, it splits it out.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance.
  • Gong.io API Key: Access to the Gong.io API for fetching call data.
  • Notion Integration: A Notion integration with appropriate permissions to create pages in your desired database.
  • AI Service API Key: An API key for an AI service (e.g., OpenAI, Anthropic, etc.) capable of summarization, entity extraction, and sentiment analysis. (This is inferred from the directory name and common use cases, not explicitly defined in the JSON).

Setup/Usage

  1. Import the workflow: Import the provided JSON into your n8n instance.
  2. Configure Credentials:
    • Set up your Gong.io API credentials in n8n.
    • Set up your Notion API credentials in n8n.
    • Set up your AI service API credentials (e.g., OpenAI) in n8n.
  3. Configure Nodes:
    • HTTP Request (Gong.io): Update the URL and headers for your specific Gong.io API endpoint and authentication. Ensure it fetches the correct call ID and transcript.
    • Edit Fields (AI Processing): Configure the AI service calls (e.g., using an "HTTP Request" node to an AI API or a dedicated AI node if available) to perform summarization, action item extraction, next steps, sentiment, and objection identification. The current JSON only shows Edit Fields which would be used to prepare data for these AI calls or structure their responses.
    • Notion: Configure the Notion node to connect to your desired Notion database and map the extracted data (call ID, summary, action items, etc.) to the correct properties in your Notion database.
  4. Execute the Workflow:
    • This workflow is designed to be triggered by another workflow or manually. You would typically pass a callId or similar identifier to the initial Execute Workflow Trigger node.
    • Run the workflow to see it in action.

Related Templates

Auto-create TikTok videos with VEED.io AI avatars, ElevenLabs & GPT-4

💥 Viral TikTok Video Machine: Auto-Create Videos with Your AI Avatar --- 🎯 Who is this for? This workflow is for content creators, marketers, and agencies who want to use Veed.io’s AI avatar technology to produce short, engaging TikTok videos automatically. It’s ideal for creators who want to appear on camera without recording themselves, and for teams managing multiple brands who need to generate videos at scale. --- ⚙️ What problem this workflow solves Manually creating videos for TikTok can take hours — finding trends, writing scripts, recording, and editing. By combining Veed.io, ElevenLabs, and GPT-4, this workflow transforms a simple Telegram input into a ready-to-post TikTok video featuring your AI avatar powered by Veed.io — speaking naturally with your cloned voice. --- 🚀 What this workflow does This automation links Veed.io’s video-generation API with multiple AI tools: Analyzes TikTok trends via Perplexity AI Writes a 10-second viral script using GPT-4 Generates your voiceover via ElevenLabs Uses Veed.io (Fabric 1.0 via FAL.ai) to animate your avatar and sync the lips to the voice Creates an engaging caption + hashtags for TikTok virality Publishes the video automatically via Blotato TikTok API Logs all results to Google Sheets for tracking --- 🧩 Setup Telegram Bot Create your bot via @BotFather Configure it as the trigger for sending your photo and theme Connect Veed.io Create an account on Veed.io Get your FAL.ai API key (Veed Fabric 1.0 model) Use HTTPS image/audio URLs compatible with Veed Fabric Other APIs Add Perplexity, ElevenLabs, and Blotato TikTok keys Connect your Google Sheet for logging results --- 🛠️ How to customize this workflow Change your Avatar: Upload a new image through Telegram, and Veed.io will generate a new talking version automatically. Modify the Script Style: Adjust the GPT prompt for tone (educational, funny, storytelling). Adjust Voice Tone: Tweak ElevenLabs stability and similarity settings. Expand Platforms: Add Instagram, YouTube Shorts, or X (Twitter) posting nodes. Track Performance: Customize your Google Sheet to measure your most successful Veed.io-based videos. --- 🧠 Expected Outcome In just a few seconds after sending your photo and theme, this workflow — powered by Veed.io — creates a fully automated TikTok video featuring your AI avatar with natural lip-sync and voice. The result is a continuous stream of viral short videos, made without cameras, editing, or effort. --- ✅ Import the JSON file in n8n, add your API keys (including Veed.io via FAL.ai), and start generating viral TikTok videos starring your AI avatar today! 🎥 Watch This Tutorial --- 📄 Documentation: Notion Guide Need help customizing? Contact me for consulting and support : Linkedin / Youtube

Dr. FirasBy Dr. Firas
39510

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

Automated weekly security audit reports with Gmail delivery

🔒 N8N Security Audit Report - Automated Weekly Email 🎯 What does this workflow do? This workflow automatically generates and emails a comprehensive security audit report for your N8N instance every week. It identifies potential security risks related to: Credentials 🔑 : Exposed or insecure credentials Nodes 🧩 : Sensitive nodes (Code, HTTP Request, SSH, FTP, etc.) Instance settings 🏢 : Global security configuration Community nodes 📦 : Third-party nodes that may pose risks The report includes direct links to affected workflows, execution statuses, and actionable recommendations. --- ✨ Key Features 📊 Smart Risk Assessment Calculates overall risk level: 🟩 Low / 🟧 Moderate / 🟥 High Tracks unique credentials (not just total occurrences) Provides detailed breakdown by node type 🔗 Direct Workflow Links Clickable links to each workflow mentioned Shows last execution status (🟢 success / 🔴 failed) Displays execution timestamps 🌍 Bilingual Support Full support for French and English Switch language with a single variable 📧 Beautiful HTML Email Clean, professional formatting Color-coded risk levels Emoji icons for easy scanning --- 🚀 Quick Setup (5 minutes) 1️⃣ Configure Credentials N8N API: Generate an API key in your N8N settings Gmail OAuth2: Set up OAuth2 for Gmail sending 2️⃣ Set Your Variables Edit the "Set Config Variables" node: javascript { "email_to": "your.email@domain.com", "project_name": "My-N8N-Project", "server_url": "https://n8n.yourdomain.com", // NO trailing slash! "Language": "EN" // or "FR" } 3️⃣ Test & Activate Click "Execute Workflow" to test Check your email inbox Activate for weekly automation --- 📧 Example Report Output Subject: 🔒 Audit Report My-Project – Risk 🟧 Moderate Content: 📊 Summary • Credentials involved: 8 (5 unique) • Nodes involved: 12 💻 code: 4 🌐 httpRequest: 3 🔐 ssh: 2 • Community nodes: 1 • Overall risk level: 🟧 Moderate 🔐 Credentials Risk Report 🔹 Credentials with full access 🔑 My AWS Credentials 🔑 Database Admin 📋 Workflow: Data Processing Pipeline 🟢 (25-10-2024 06:15 → 06:16) 💻 Process Data 🌐 API Call 🧩 Nodes Risk Report [...detailed node analysis...] --- 🎨 Customization Options Change Schedule Modify the "Schedule Trigger" node to run: Daily at 8 AM Monthly on the 1st Custom cron expression Add Recipients Add multiple emails in the Gmail node's toList parameter Adjust Risk Thresholds Edit the JavaScript in "Format Audit Report" nodes to customize when risk levels change Use Different Email Service Replace Gmail node with: SMTP Microsoft Outlook SendGrid Any email service N8N supports --- 💡 Use Cases ✅ Compliance Monitoring: Track security posture for audits ✅ Team Awareness: Keep your team informed of security status ✅ Change Detection: Notice when new risky nodes are added ✅ Best Practices: Get recommendations to improve security ✅ Multi-Environment: Run separate instances for dev/staging/prod --- 🔧 Technical Details Nodes Used: 8 Credentials Required: 2 (N8N API + Gmail OAuth2) External Dependencies: None N8N Version: Compatible with latest N8N versions Execution Time: ~10-20 seconds --- 📋 Requirements N8N instance with API access Gmail account (or other email service) N8N API key with audit permissions Valid SSL certificate for workflow links (recommended) --- 🐛 Troubleshooting Empty report? → Check your N8N API key has audit permissions Workflow links don't work? → Verify server_url is correct and has no trailing slash No execution status shown? → Workflows must have been executed at least once Wrong language displayed? → Set Language to exactly "FR" or "EN" (uppercase) --- 🌟 Why This Template? Unlike basic monitoring tools, this workflow: ✅ Provides context-aware security analysis ✅ Links directly to affected workflows ✅ Shows real execution data (not just theoretical risks) ✅ Calculates unique credential exposure (not just counts) ✅ Supports bilingual reports ✅ Delivers actionable recommendations --- 🤝 Feedback & Support Found this helpful? Please rate the template! Have suggestions? Drop a comment below. Pro tip: Combine this with N8N's native alerting for real-time incident response! --- Tags: security audit monitoring compliance automation email reporting credentials governance --- 📜 License MIT - Feel free to modify and share!

MatthieuBy Matthieu
389