HumationHuman + Automation
Back to Catalog

Automate service package recommendations with Google Workspace sales pipeline tracking

Xavier TaiXavier Tai
17 views
2/3/2026
notificationemailautomationfilterimap
Official Page

💰 Package Recommender with Sales Pipeline Tracking

What It Does

Automatically recommends the right service package based on budget, sends beautifully formatted proposal emails with case studies, logs everything to a sales pipeline tracker, and schedules your follow-up reminders. Converts inquiries into booked calls without manual proposal writing.

How It Works

  1. Form Trigger → Lead submits budget and challenge details
  2. Log to Pipeline → All inquiry data saved to tracking sheet
  3. Budget Router → Directs to Basic ($0-3K), Standard ($3-6K), or Premium ($6K+)
  4. Set Package Variables → Loads appropriate features, pricing, case study
  5. Send Proposal Email → Gorgeous HTML email with personalized package details
  6. Update Pipeline → Marks "Package Sent" and sets follow-up date (+3 days)
  7. Calendar Reminder → Creates event in 3 days reminding you to follow up

🚀 SETUP INSTRUCTIONS

Step 1: Create Sales Pipeline Sheet

  • Create Google Sheet with tab "Package Inquiries"
  • Add columns: Timestamp | Name | Email | Phone | Budget | Timeline | Challenge | Package Recommended | Package Price | Status | Date Sent | Follow-Up Date
  • Update YOUR_GOOGLE_SHEET_ID in nodes 2, 7, and calendar description

Step 2: Customize Package Details

  • Edit nodes 4, 5, 6 (Set Package Details nodes)
  • Update pricing, features, and case studies for your services
  • Replace booking links with your actual Calendly/scheduling URLs
  • Adjust package names if needed

Step 3: Configure Email Template

  • Edit node 7 email design/branding
  • Update "Your Name" and signature
  • Customize colors (currently: purple gradient, green CTA)
  • Test email rendering across devices

Step 4: Setup Calendar Integration

  • Add Google Calendar OAuth2 credentials
  • Verify follow-up timing (currently +3 days)
  • Customize reminder description with your workflow
  • Update Google Sheet link in calendar event

Automate Service Package Recommendations & Sales Pipeline Tracking

This n8n workflow streamlines the process of recommending service packages to potential clients and tracking their progress through the sales pipeline. It starts by capturing form submissions, then uses conditional logic to determine the appropriate follow-up actions, including sending personalized emails and scheduling internal calendar events.

What it does

  1. Listens for new form submissions: The workflow is triggered whenever a new entry is submitted via an n8n form.
  2. Processes form data: It takes the submitted information, likely including client details and their expressed needs.
  3. Applies conditional logic for recommendations: A Switch node evaluates the form data to determine which service package recommendation is most suitable for the client.
  4. Sends personalized email recommendations: Based on the Switch node's output, a Gmail node sends an email to the client with the tailored service package recommendation.
  5. Updates a Google Sheet for sales pipeline tracking: A Google Sheets node records the client's information and their current stage in the sales pipeline, providing a centralized tracking system.
  6. Schedules internal follow-up events: For certain conditions (likely when a specific recommendation is made or a follow-up is needed), a Google Calendar node creates an event for the sales team to follow up with the client.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n instance: A running n8n instance to host and execute the workflow.
  • Google Sheets Account: Configured n8n credentials for Google Sheets to update your sales pipeline spreadsheet.
  • Gmail Account: Configured n8n credentials for Gmail to send recommendation emails.
  • Google Calendar Account: Configured n8n credentials for Google Calendar to schedule internal follow-up events.
  • n8n Form: A pre-configured n8n form that collects client information and triggers this workflow.

Setup/Usage

  1. Import the workflow: Download the provided JSON and import it into your n8n instance.
  2. Configure Credentials:
    • Set up your Google Sheets credentials.
    • Set up your Gmail credentials.
    • Set up your Google Calendar credentials.
  3. Configure the "On form submission" node: Ensure this node is linked to your desired n8n form.
  4. Configure the "Edit Fields" node: Adjust this node to map the incoming form data to the fields you need for your recommendations and tracking.
  5. Configure the "Switch" node: Customize the conditions in the Switch node to match your service package logic and criteria.
  6. Configure the "Gmail" nodes: Update the email templates and recipient information for each recommendation path.
  7. Configure the "Google Sheets" node: Specify the spreadsheet ID, sheet name, and the columns where you want to record client data and pipeline status.
  8. Configure the "Google Calendar" nodes: Define the event details (summary, description, attendees, start/end times) for internal follow-up meetings.
  9. Activate the workflow: Once configured, activate the workflow to start automating your service package recommendations and sales pipeline tracking.

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