CallForge - 02 - Prep Gong Calls with Sheets & Notion for AI Summarization

CallForge AI Sales Call Processor Workflow Overview This workflow automates the entire pipeline of processing sales calls from Gong for AI analysis. It begins by fetching recent calls from Gong, then enriches this data with supplementary information about company integrations (from Google Sheets) and competitors (from a Notion database). A key feature is its deduplication process; the workflow cross-references a Notion database of previously analyzed calls to ensure it only processes new ones, preventing redundant work and data duplication. Finally, it loops through each new, enriched call and passes it to a series of sub-workflows that use AI to clean the transcript and extract structured insights. Technologies Used - Gong: The source for sales call recordings and transcripts. - Google Sheets: Used as a simple database to store and retrieve a list of product integrations. - Notion: Serves two purposes: 1) as a database of company competitors to enrich AI prompts, and 2) as the destination/log for previously processed calls to prevent duplicates. - n8n (Sub-workflows): The workflow executes other n8n workflows to handle specific, modular tasks like transcript cleaning and the final AI processing. Automation Value This workflow provides significant value by creating a fully automated, "hands-off" system for deriving intelligence from sales calls. It eliminates the hours of manual work required for sales managers, product teams, or marketers to listen to calls. The automation ensures: - Consistency: Every call is processed using the same logic and criteria. - Efficiency: Calls are automatically fetched, prepared, and analyzed without human intervention. - Data Integrity: By checking against a log in Notion, it guarantees that no call is processed more than once. - Actionable Insights: It transforms unstructured call transcripts into structured data, ready for review and action. AI Integration The AI is the core processing engine of this system, operating within the "Process All Call Transcripts" sub-workflow. Its integration is highly strategic: 1.