CallForge - 08 - AI Product Insights from Sales Calls with Notion

CallForge - AI Sales Call Insights Processor Workflow Overview This workflow acts as a data processor and router for insights extracted from sales calls by a separate AI analysis workflow. Its primary function is to receive structured AI-generated data about a sales call, evaluate what kind of information is present (product feedback, AI use cases), and then systematically log that information into specific Notion databases. This automation creates a powerful, centralized repository of customer intelligence directly from sales conversations. It saves product, sales, and engineering teams countless hours of manual review and data entry by ensuring that valuable feedback and new use cases are captured, categorized, and linked to the original call record automatically. Technologies Used - n8n: The core automation platform coordinating the data flow. - Notion: Used as the target database system to store and organize the extracted insights. How AI Integrates into the Flow This workflow is entirely dependent on AI-generated data provided by a preceding workflow (likely one that processes Gong call transcripts). The AI's role is to analyze the sales call and structure its findings into a JSON object. This workflow receives that JSON and uses its contents to make decisions. The AI is responsible for: - Identifying Product Feedback: Extracting specific comments about the product and classifying their sentiment. - Detecting AI/ML Use Cases: Recognizing when a customer discusses a potential use case for AI, and extracting key details like the department, development status, and technical requirements (e.g., RAG, agents). - Summarizing Context: Providing a summary of the AI-related discussion. This workflow takes the structured intelligence from the AI and translates it into actionable, organized records in a knowledge base (Notion). Node-by-Node Analysis H2: Trigger and Initial Routing The workflow begins by receiving data and immediately splits into three parallel paths to check for different types of insights. H3: Execute Workflow Trigger - Purpose: This is the entry point. It's triggered by another n8n workflow, receiving a payload of data.