Back to Catalog

Auto-generate sales presentations from Claap calls with GPT-4o and Google Slides

Robin BonduelleRobin Bonduelle
171 views
2/3/2026
Official Page

Template presentation

  • This template generates a sales follow-up presentation in Google Slides after a sales call recorded in Claap.
  • The workflow is simplified to showcase the main use case.
  • You can customize and enrich this workflow by connecting to the CRM, researching data online or adding more files in the presentation.
  • The presentation template used in this workflow is available here.

Workflow configuration

  • Create a webhook in Claap, by following this article.
  • Edit the labels that trigger the workflow and route on the relevant presentation.
  • Fill your Open AI credentials by creating an API Key in OpenAI Platform
  • Edit the presentation personalization details (user set as editor, content, title)
  • Fill your Slack credentials by following steps in this video.

n8n Workflow: Auto-Generate Sales Presentations from Claap Calls with GPT-4o and Google Slides

This n8n workflow automates the process of generating sales presentations. It's designed to be triggered by an external system (e.g., a Claap call summary webhook) and then uses AI to create presentation content, which can then be used to generate a Google Slides presentation. It also includes steps for HubSpot integration and Slack notifications.

What it does

This workflow streamlines the creation of sales presentations by:

  1. Receiving a Webhook Trigger: It starts by listening for incoming data via a webhook, likely containing details about a sales call or a request to generate a presentation.
  2. Filtering Data: It uses an "If" node to conditionally process the incoming data, potentially based on certain criteria present in the webhook payload.
  3. Editing Fields: A "Set" node is used to manipulate or transform the data received, preparing it for subsequent steps.
  4. Conditional Routing (Switch): A "Switch" node provides further conditional logic, allowing the workflow to branch into different paths based on specific data values.
  5. Generating Content with OpenAI: In one branch, it leverages the OpenAI node to generate presentation content, likely using a large language model (LLM) like GPT-4o to create summaries, bullet points, or full slide content.
  6. Custom Code Execution: A "Code" node allows for custom JavaScript logic to be executed, which could be used for advanced data manipulation, formatting, or integration with other services.
  7. Making HTTP Requests: An "HTTP Request" node enables interaction with external APIs, which could be used to fetch additional data, trigger other services, or interact with a Google Slides API to create or update presentations.
  8. Updating HubSpot: It integrates with HubSpot, potentially creating or updating deals, contacts, or other CRM records based on the presentation generation event.
  9. Sending Slack Notifications: It sends notifications to a Slack channel, informing relevant team members about the presentation generation status or any issues.
  10. Sticky Note: A sticky note is included for documentation or temporary notes within the workflow.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance to import and execute the workflow.
  • Webhook Source: An external system configured to send data to the n8n webhook (e.g., a Claap call summary system, a CRM, or a custom application).
  • OpenAI API Key: Credentials for OpenAI to access its language models (e.g., GPT-4o).
  • HubSpot Account: Credentials for HubSpot to interact with your CRM data.
  • Slack Account: Credentials for Slack to send notifications.
  • Google Slides API Access (Implicit): While not explicitly shown as a direct node, the "HTTP Request" node or "Code" node would likely interact with the Google Slides API. Therefore, you would need appropriate Google Cloud credentials and API access configured.

Setup/Usage

  1. Import the Workflow: Download the workflow JSON and import it into your n8n instance.
  2. Configure Credentials:
    • Set up your OpenAI credentials in n8n.
    • Set up your HubSpot credentials in n8n.
    • Set up your Slack credentials in n8n.
  3. Configure Webhook:
    • Copy the webhook URL from the "Webhook" node.
    • Configure your external system (e.g., Claap call summary tool) to send POST requests to this URL with the relevant sales call data.
  4. Customize Nodes:
    • If Node: Adjust the conditions in the "If" node to match your specific filtering logic.
    • Edit Fields (Set) Node: Modify the fields being set or transformed to align with your data structure.
    • Switch Node: Define the conditions and outputs for the "Switch" node to handle different presentation scenarios.
    • OpenAI Node: Configure the prompt and model parameters for the OpenAI node to generate the desired presentation content.
    • Code Node: If used for Google Slides API interaction or complex logic, customize the JavaScript code.
    • HTTP Request Node: Configure the URL, headers, and body for any external API calls, especially if interacting with Google Slides directly.
    • HubSpot Node: Specify the HubSpot object (e.g., "Contact", "Deal") and the properties to create or update.
    • Slack Node: Customize the Slack channel and message content for notifications.
  5. Activate the Workflow: Once configured, activate the workflow in n8n.

Related Templates

Two-way property repair management system with Google Sheets & Drive

This workflow automates the repair request process between tenants and building managers, keeping all updates organized in a single spreadsheet. It is composed of two coordinated workflows, as two separate triggers are required — one for new repair submissions and another for repair updates. A Unique Unit ID that corresponds to individual units is attributed to each request, and timestamps are used to coordinate repair updates with specific requests. General use cases include: Property managers who manage multiple buildings or units. Building owners looking to centralize tenant repair communication. Automation builders who want to learn multi-trigger workflow design in n8n. --- ⚙️ How It Works Workflow 1 – New Repair Requests Behind the Scenes: A tenant fills out a Google Form (“Repair Request Form”), which automatically adds a new row to a linked Google Sheet. Steps: Trigger: Google Sheets rowAdded – runs when a new form entry appears. Extract & Format: Collects all relevant form data (address, unit, urgency, contacts). Generate Unit ID: Creates a standardized identifier (e.g., BUILDING-UNIT) for tracking. Email Notification: Sends the building manager a formatted email summarizing the repair details and including a link to a Repair Update Form (which activates Workflow 2). --- Workflow 2 – Repair Updates Behind the Scenes:\ Triggered when the building manager submits a follow-up form (“Repair Update Form”). Steps: Lookup by UUID: Uses the Unit ID from Workflow 1 to find the existing row in the Google Sheet. Conditional Logic: If photos are uploaded: Saves each image to a Google Drive folder, renames files consistently, and adds URLs to the sheet. If no photos: Skips the upload step and processes textual updates only. Merge & Update: Combines new data with existing repair info in the same spreadsheet row — enabling a full repair history in one place. --- 🧩 Requirements Google Account (for Forms, Sheets, and Drive) Gmail/email node connected for sending notifications n8n credentials configured for Google API access --- ⚡ Setup Instructions (see more detail in workflow) Import both workflows into n8n, then copy one into a second workflow. Change manual trigger in workflow 2 to a n8n Form node. Connect Google credentials to all nodes. Update spreadsheet and folder IDs in the corresponding nodes. Customize email text, sender name, and form links for your organization. Test each workflow with a sample repair request and a repair update submission. --- 🛠️ Customization Ideas Add Slack or Telegram notifications for urgent repairs. Auto-create folders per building or unit for photo uploads. Generate monthly repair summaries using Google Sheets triggers. Add an AI node to create summaries/extract relevant repair data from repair request that include long submissions.

Matt@VeraisonLabsBy Matt@VeraisonLabs
208

Send WooCommerce cross-sell offers to customers via WhatsApp using Rapiwa API

Who Is This For? This n8n workflow enables automated cross-selling by identifying each WooCommerce customer's most frequently purchased product, finding a related product to recommend, and sending a personalized WhatsApp message using the Rapiwa API. It also verifies whether the user's number is WhatsApp-enabled before sending, and logs both successful and unsuccessful attempts to Google Sheets for tracking. What This Workflow Does Retrieves all paying customers from your WooCommerce store Identifies each customer's most purchased product Finds the latest product in the same category as their most purchased item Cleans and verifies customer phone numbers for WhatsApp compatibility Sends personalized WhatsApp messages with product recommendations Logs all activities to Google Sheets for tracking and analysis Handles both verified and unverified numbers appropriately Key Features Customer Segmentation: Automatically identifies paying customers from your WooCommerce store Product Analysis: Determines each customer's most purchased product Smart Recommendations: Finds the latest products in the same category as customer favorites WhatsApp Integration: Uses Rapiwa API for message delivery Phone Number Validation: Verifies WhatsApp numbers before sending messages Dual Logging System: Tracks both successful and failed message attempts in Google Sheets Rate Limiting: Uses batching and wait nodes to prevent API overload Personalized Messaging: Includes customer name and product details in messages Requirements WooCommerce store with API access Rapiwa account with API access for WhatsApp verification and messaging Google account with Sheets access Customer phone numbers in WooCommerce (stored in billing.phone field) How to Use — Step-by-Step Setup Credentials Setup WooCommerce API: Configure WooCommerce API credentials in n8n (e.g., "WooCommerce (get customer)" and "WooCommerce (get customer data)") Rapiwa Bearer Auth: Create an HTTP Bearer credential with your Rapiwa API token Google Sheets OAuth2: Set up OAuth2 credentials for Google Sheets access Configure Google Sheets Ensure your sheet has the required columns as specified in the Google Sheet Column Structure section Verify Code Nodes Code (get paying_customer): Filters customers to include only those who have made purchases Get most buy product id & Clear Number: Identifies the most purchased product and cleans phone numbers Configure HTTP Request Nodes Get customer data: Verify the WooCommerce API endpoint for retrieving customer orders Get specific product data: Verify the WooCommerce API endpoint for product details Get specific product recommend latest product: Verify the WooCommerce API endpoint for finding latest products by category Check valid WhatsApp number Using Rapiwa: Verify the Rapiwa endpoint for WhatsApp number validation Rapiwa Sender: Verify the Rapiwa endpoint for sending messages Google Sheet Required Columns You’ll need two Google Sheets (or two tabs in one spreadsheet): A Google Sheet formatted like this ➤ sample The workflow uses a Google Sheet with the following columns to track coupon distribution: Both must have the following headers (match exactly): | name | number | email | address1 | price | suk | title | product link | validity | staus | | ---------- | ------------- | ----------------------------------------------- | ----------- | ----- | --- | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------- | -------- | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | unverified | not sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | Important Notes Phone Number Format: The workflow cleans phone numbers by removing all non-digit characters. Ensure your WooCommerce phone numbers are in a compatible format. API Rate Limits: Rapiwa and WooCommerce APIs have rate limits. Adjust batch sizes and wait times accordingly. Data Privacy: Ensure compliance with data protection regulations when sending marketing messages. Error Handling: The workflow logs unverified numbers but doesn't have extensive error handling. Consider adding error notifications for failed API calls. Product Availability: The workflow recommends the latest product in a category, but doesn't check if it's in stock. Consider adding stock status verification. Testing: Always test with a small batch before running the workflow on your entire customer list. Useful Links Dashboard: https://app.rapiwa.com Official Website: https://rapiwa.com Documentation: https://docs.rapiwa.com Support & Help WhatsApp: Chat on WhatsApp Discord: SpaGreen Community Facebook Group: SpaGreen Support Website: https://spagreen.net Developer Portfolio: Codecanyon SpaGreen

RapiwaBy Rapiwa
183

Track SDK documentation drift with GitHub, Notion, Google Sheets, and Slack

📊 Description Automatically track SDK releases from GitHub, compare documentation freshness in Notion, and send Slack alerts when docs lag behind. This workflow ensures documentation stays in sync with releases, improves visibility, and reduces version drift across teams. 🚀📚💬 What This Template Does Step 1: Listens to GitHub repository events to detect new SDK releases. 🧩 Step 2: Fetches release metadata including version, tag, and publish date. 📦 Step 3: Logs release data into Google Sheets for record-keeping and analysis. 📊 Step 4: Retrieves FAQ or documentation data from Notion. 📚 Step 5: Merges GitHub and Notion data to calculate documentation drift. 🔍 Step 6: Flags SDKs whose documentation is over 30 days out of date. ⚠️ Step 7: Sends detailed Slack alerts to notify responsible teams. 🔔 Key Benefits ✅ Keeps SDK documentation aligned with product releases ✅ Prevents outdated information from reaching users ✅ Provides centralized release tracking in Google Sheets ✅ Sends real-time Slack alerts for overdue updates ✅ Strengthens DevRel and developer experience operations Features GitHub release trigger for real-time monitoring Google Sheets logging for tracking and auditing Notion database integration for documentation comparison Automated drift calculation (days since last update) Slack notifications for overdue documentation Requirements GitHub OAuth2 credentials Notion API credentials Google Sheets OAuth2 credentials Slack Bot token with chat:write permissions Target Audience Developer Relations (DevRel) and SDK engineering teams Product documentation and technical writing teams Project managers tracking SDK and doc release parity Step-by-Step Setup Instructions Connect your GitHub account and select your SDK repository. Replace YOURGOOGLESHEETID and YOURSHEET_GID with your tracking spreadsheet. Add your Notion FAQ database ID. Configure your Slack channel ID for alerts. Run once manually to validate setup, then enable automation.

Rahul JoshiBy Rahul Joshi
31