Back to Catalog

CallForge - 02 - prep Gong calls with sheets & notion for AI summarization

Angel MenendezAngel Menendez
1607 views
2/3/2026
Official Page

callforgecompressed.png

CallForge - AI Gong Sales Call Processor

Streamline your sales call analysis with CallForge, an automated workflow that extracts, enriches, and refines Gong.io call data for AI-driven insights.

Who is This For?

This workflow is designed for:
Sales teams looking to automate sales call insights.
Revenue operations (RevOps) professionals optimizing call data processing.
Businesses using Gong.io to analyze and enhance sales call transcripts.

What Problem Does This Workflow Solve?

Manually analyzing sales calls is time-consuming and prone to inconsistencies. While Gong provides raw call data, interpreting these conversations and improving AI-generated summaries can be challenging.

With CallForge, you can:
✔️ Automate transcript extraction from Gong.io.
✔️ Enhance AI insights by adding product and competitor data.
✔️ Reduce errors from AI-generated summaries by correcting mispronunciations.
✔️ Eliminate duplicate calls to prevent redundant processing.

What This Workflow Does

1. Extracts Gong Call Data

  • Retrieves call recordings, metadata, meeting links, and duration from Gong.

2. Removes Duplicate Entries

  • Queries Notion to ensure that already processed calls are not duplicated.

3. Enriches Call Data

  • Fetches integration details from Google Sheets.
  • Retrieves competitor insights from Notion.
  • Merges data to provide AI with a more comprehensive context.

4. Prepares AI-Friendly Transcripts

  • Cleans up transcripts for structured AI processing.
  • Reduces prompt complexity for more accurate OpenAI outputs.

5. Sends Processed Data to an AI Call Processor

  • Delivers the cleaned and enriched transcript to an AI-powered workflow for generating structured call summaries.

How to Set Up This Workflow

1. Connect Your APIs

🔹 Gong API Access – Set up your Gong API credentials in n8n.
🔹 Google Sheets Credentials – Provide API access for retrieving integration data.
🔹 Notion API Setup – Connect Notion to fetch competitor insights and store processed data.
🔹 AI Processing Workflow – Ensure an OpenAI-powered workflow is in place for structured summaries.

2. Customize to Fit Your Needs

💡 Modify Data Sources – Update connections if using a different CRM, database, or analytics tool.
💡 Adjust AI Processing Logic – Optimize transcript formatting based on your preferred AI model.
💡 Expand Data Enrichment – Integrate CRM data, industry benchmarks, or other insights.

Why Use CallForge?

By automating Gong call processing, CallForge empowers sales teams to:
📈 Gain valuable AI-driven insights from calls.
Speed up decision-making with cleaner, structured data.
🛠 Improve sales strategies based on enriched, accurate transcripts.

🚀 Start automating your Gong call analysis today!

Workflow: Prep Gong Calls with Google Sheets & Notion for AI Summarization

This n8n workflow automates the preparation of Gong call data, enriching it with information from Google Sheets and then storing it in Notion, likely for further AI summarization or analysis. It acts as a bridge between your call recording platform and your knowledge management system.

What it does

This workflow performs the following key steps:

  1. Manual Trigger: The workflow can be initiated manually.
  2. Retrieve Gong Calls: It fetches a list of calls from Gong.
  3. Process Calls in Batches: Each Gong call is processed individually to handle potential rate limits or large datasets efficiently.
  4. Execute Sub-workflow: For each Gong call, it calls a sub-workflow to perform detailed processing. This modular approach allows for reusable logic.
  5. Retrieve Google Sheet Data: It reads data from a specified Google Sheet.
  6. Compare Datasets: It compares the Gong call data with the Google Sheet data, likely to identify new or updated calls, or to enrich Gong data with sheet information.
  7. Filter for New/Updated Records: Based on the comparison, it filters for relevant records (e.g., calls that need to be added or updated in Notion).
  8. Prepare Data for Notion: It manipulates and formats the data to fit the structure required by Notion.
  9. Create/Update Notion Pages: It creates new pages or updates existing ones in a Notion database using the prepared data.
  10. Aggregate Results: It collects the results from the Notion operations.
  11. No Operation (Placeholder): A placeholder node, possibly for future expansion or debugging.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running instance of n8n.
  • Gong Account: Credentials configured in n8n to access your Gong data.
  • Google Sheets Account: Credentials configured in n8n to access your Google Sheets. You'll need to specify the Spreadsheet ID and Sheet Name.
  • Notion Account: Credentials configured in n8n to access your Notion workspace. You'll need to specify the Database ID where the call data will be stored.
  • Sub-workflow: A separate n8n workflow that is executed by the "Execute Workflow" node. The JSON for this sub-workflow is not included here but is essential for the full functionality.

Setup/Usage

  1. Import the Workflow: Import the provided JSON into your n8n instance.
  2. Configure Credentials:
    • Set up your Gong credentials.
    • Set up your Google Sheets credentials.
    • Set up your Notion credentials.
  3. Configure Nodes:
    • Gong Node: Ensure the correct operation (e.g., "Get All Calls") and any necessary filters are configured.
    • Google Sheets Node: Specify the Spreadsheet ID and Sheet Name you wish to read from.
    • Execute Workflow Node: Ensure the Workflow ID points to your sub-workflow.
    • Notion Node: Configure the Database ID where the call data should be stored. Map the fields from the incoming data to your Notion database properties.
    • Edit Fields (Set) Node: Adjust the field transformations as needed to match your Notion database schema.
  4. Activate the Workflow: Once configured, activate the workflow. You can then trigger it manually to test.

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 Dutch Public Procurement Data Collection with TenderNed

TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch 🔗 LinkedIn – Wessel Bulte

Wessel BulteBy Wessel Bulte
247