Drive-to-store lead generation (with coupon) with Google Sheets & SuiteCRM
Drive-to-Store is a multi-channel marketing strategy that includes both the web and the physical context, with the aim of increasing the number of customers and sales in physical stores. This strategy guides potential customers from the online world to the physical point of sale through the provision of a coupon that can be spent in the store or on an e-commerce site.
The basic idea is to have a landing page with a form and a series of unique coupons to assign to leads as a "reward" for filling out the form.
This workflow is ideal for businesses looking to automate lead generation and management, especially when integrating with CRM systems like SuiteCRM and using Google Sheets for data tracking.
How It Works
-
Form Submission:
- The workflow starts with the On form submission node, which triggers when a user submits a form on a landing page. The form collects the user's name, surname, email, and phone number.
-
Form Data Processing:
- The Form Fields node extracts and sets the form data (name, surname, email, and phone) for use in subsequent steps.
-
Duplicate Lead Check:
- The Duplicate Lead? node checks if the submitted email already exists in a Google Sheets document. If the email is found, the workflow responds with a "duplicate lead" message (Respond KO node) and stops further processing.
-
Coupon Retrieval:
- If the email is not a duplicate, the Get Coupon node retrieves a coupon code from the Google Sheets document based on the lead's email.
-
Lead Creation in SuiteCRM:
- The Create Lead SuiteCRM node creates a new lead in SuiteCRM using the form data and the retrieved coupon code. The lead includes:
- First name, last name, email, phone number, and coupon code.
- The Create Lead SuiteCRM node creates a new lead in SuiteCRM using the form data and the retrieved coupon code. The lead includes:
-
Google Sheets Update:
- The Update Sheet node updates the Google Sheets document with the newly created lead's details, including:
- Name, surname, email, phone, coupon code, lead ID, and the current date and time.
- The Update Sheet node updates the Google Sheets document with the newly created lead's details, including:
-
Response to Webhook:
- The Respond OK node sends a success response back to the webhook, indicating that the lead was created successfully.
Set Up Steps
-
Configure Form Trigger:
- Set up the On form submission node to collect user data (name, surname, email, and phone) via a web form.
-
Set Up Google Sheets Integration:
- Configure the Duplicate Lead?, Get Coupon, and Update Sheet nodes to interact with the Google Sheets document. Ensure the document contains columns for email, coupon, lead ID, and other relevant fields.
-
Set Up SuiteCRM Authentication:
- Configure the Token SuiteCRM node with the appropriate client credentials (client ID and client secret) to obtain an access token from SuiteCRM.
-
Set Up Lead Creation in SuiteCRM:
- Configure the Create Lead SuiteCRM node to send a POST request to SuiteCRM's API to create a new lead. Include the form data and coupon code in the request body.
-
Set Up Webhook Responses:
- Configure the Respond OK and Respond KO nodes to send appropriate JSON responses back to the webhook based on whether the lead was created or if it was a duplicate.
-
Test the Workflow:
- Submit a test form to ensure the workflow correctly checks for duplicates, retrieves a coupon, creates a lead in SuiteCRM, and updates the Google Sheets document.
-
Activate the Workflow:
- Once tested, activate the workflow to automate the process of handling form submissions and lead creation.
Key Features
- Duplicate Lead Check: Prevents duplicate leads by checking if the email already exists in the Google Sheets document.
- Coupon Assignment: Retrieves a coupon code from Google Sheets and assigns it to the new lead.
- SuiteCRM Integration: Automatically creates a new lead in SuiteCRM with the form data and coupon code.
- Data Logging: Logs all lead details in a Google Sheets document for tracking and analysis.
- Webhook Responses: Provides immediate feedback on whether the lead was created successfully or if it was a duplicate.
n8n Workflow: Drive-to-Store Lead Generation with Coupon and CRM Integration
This n8n workflow automates a lead generation process for "drive-to-store" campaigns, specifically designed to capture leads via a form, offer a coupon, and integrate these leads into a CRM (SuiteCRM, based on the directory name hint) while also logging them in Google Sheets.
What it does
This workflow streamlines the following steps:
- Captures Lead Information: It starts by listening for submissions from an n8n Form, which is likely used to collect lead details for a "drive-to-store" campaign.
- Records Lead in Google Sheets: Immediately upon form submission, the collected lead data is appended as a new row in a specified Google Sheet, ensuring a comprehensive log of all leads.
- Applies Data Transformation: It then prepares the data for the CRM by setting and renaming specific fields to match the expected format of the CRM system.
- Creates Lead in CRM (SuiteCRM): The transformed lead data is sent to a CRM system (implied to be SuiteCRM) via an HTTP Request to create a new lead record.
- Conditional Coupon Delivery:
- Success Path: If the CRM lead creation is successful (HTTP Request returns a 2xx status code), the workflow generates a success message including a coupon code.
- Failure Path: If the CRM lead creation fails, it generates an error message.
- Responds to Webhook: Finally, it responds to the initial webhook trigger (from the n8n form) with either the success message (including the coupon) or the error message, providing immediate feedback to the user who submitted the form.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running n8n instance.
- Google Sheets Account: Configured n8n credentials for Google Sheets with access to the target spreadsheet.
- CRM (e.g., SuiteCRM) API Access: An API endpoint and credentials for your CRM system to create new leads. This will be configured in the HTTP Request node.
- n8n Form: An n8n Form setup to trigger this workflow.
Setup/Usage
- Import the Workflow: Import the provided JSON into your n8n instance.
- Configure Credentials:
- Google Sheets: Set up your Google Sheets credentials (OAuth2 recommended) and link them to the "Google Sheets" node. Specify the Spreadsheet ID and Sheet Name where leads should be logged.
- CRM (HTTP Request): Configure the "HTTP Request" node with the appropriate URL, HTTP Method (likely POST), Headers (for authentication, e.g., API Key or OAuth token), and Body (JSON or form-data) required by your CRM's API to create a new lead. Map the fields from the "Edit Fields" node to your CRM's expected fields.
- Configure n8n Form Trigger:
- Activate the "On form submission" node. This will generate a webhook URL.
- Embed or link this n8n Form URL wherever you intend to collect leads (e.g., on your website, landing page).
- Activate the Workflow: Once all credentials and configurations are in place, activate the workflow.
When a user submits the n8n form, the workflow will automatically process the lead, log it, attempt to add it to your CRM, and provide an instant response with a coupon if successful.
Related Templates
Generate Funny AI Videos with Sora 2 and Auto-Publish to TikTok
This automation creates a fully integrated pipeline to generate AI-powered videos, store them, and publish them on TikTok — all automatically. It connects OpenAI Sora 2, and Postiz (for TikTok publishing) to streamline content creation. --- Key Benefits ✅ Full Automation – From text prompt to TikTok upload, everything happens automatically with no manual intervention once set up. ✅ Centralized Control – Google Sheets acts as a simple dashboard to manage prompts, durations, and generated results. ✅ AI-Powered Creativity – Uses OpenAI Sora 2 for realistic video generation and GPT-5 for optimized titles. ✅ Social Media Integration – Seamlessly posts videos to TikTok via Postiz, ready for your audience. ✅ Scalable & Customizable – Can easily be extended to other platforms like YouTube, Instagram, or LinkedIn. ✅ Time-Saving – Eliminates repetitive steps like manual video uploads or caption writing. --- How it works This workflow automates the end-to-end process of generating AI videos and publishing them to TikTok. It is triggered either manually or on a recurring schedule. Trigger & Data Fetch: The workflow starts by checking a specified Form for new entries. It looks for rows where a video has been requested (a "PROMPT" is filled) but not yet generated (the "VIDEO" column is empty). AI Video Generation: For each new prompt found, the workflow sends a request to the Fal.ai Sora 2 model to generate a video. It then enters a polling loop, repeatedly checking the status of the generation request every 60 seconds until the video is "COMPLETED". Post-Processing & Upload: Once the video is ready, the workflow performs several actions in parallel: Fetch Video & Store: It retrieves the final video URL, downloads the video file Generate Title: It uses the OpenAI GPT-4o-mini model to analyze the original prompt and generate an optimized, engaging title for the video. Publish to TikTok: The video file is uploaded to Postiz, a social media scheduling tool, which then automatically publishes it to a connected TikTok channel, using the AI-generated title as the post's caption. --- Set up steps To make this workflow functional, you need to complete the following configuration steps: Prepare the Google Sheet: Create a Form with at least "PROMPT", "DURATION", and "VIDEO" fields. Configure Fal.ai for Video Generation: Create an account at Fal.ai and obtain your API key. In both the "Create Video" and "Get status" HTTP Request nodes, set up the "Header Auth" credential. Set the Name to Authorization and the Value to Key YOURAPIKEY. Set up TikTok Publishing via Postiz: Create an account on Postiz and connect your TikTok account to get a Channel ID. Obtain your Postiz API key. In the "Upload Video to Postiz" and "TikTok" (Postiz) nodes, configure the API credentials. In the "TikTok" node, replace the placeholder "XXX" in the integrationId field with your actual TikTok Channel ID from Postiz. (Optional) Configure AI Title Generation: The "Generate title" node uses OpenAI. Ensure you have valid OpenAI API credentials configured in n8n for this node to work. --- Need help customizing? Contact me for consulting and support or add me on Linkedin. Header 2
AI meeting summary & action item tracker with Notion, Slack, and Gmail
How it Works This workflow accepts meeting transcripts via webhook (Zoom, Google Meet, Teams, Otter.ai, or manual notes), immediately processing them through an intelligent pipeline that eliminates post-meeting admin work. The system parses multiple input formats (JSON, form data, transcription outputs), extracting meeting metadata including title, date, attendees, transcript content, duration, and recording URLs. OpenAI analyzes the transcript to extract eight critical dimensions: executive summary, key decisions with ownership, action items with assigned owners and due dates, discussion topics, open questions, next steps, risks/blockers, and follow-up meeting requirements—all returned as structured JSON. The intelligence engine enriches each action item with unique IDs, priority scores (weighing urgency + owner assignment + due date), status initialization, and meeting context links, then calculates a completeness score (0-100) that penalizes missing owners and undefined deadlines. Multi-channel distribution ensures visibility: Slack receives formatted summaries with emoji categorization for decisions (✅), action items (🎯) with priority badges and owner assignments, and completeness scores (📊). Notion gets dual-database updates—meeting notes with formatted decisions and individual task cards in your action item database with full filtering and kanban capabilities. Task owners receive personalized HTML emails with priority color-coding and meeting context, while Google Calendar creates due-date reminders as calendar events. Every meeting logs to Google Sheets for analytics tracking: attendee count, duration, action items created, priority distribution, decision count, completeness score, and follow-up indicators. The workflow returns a JSON response confirming successful processing with meeting ID, action item count, and executive summary. The entire pipeline executes in 8-12 seconds from submission to full distribution. --- Who is this for? Product and engineering teams drowning in scattered action items across tools Remote-first companies where verbal commitments vanish after calls Executive teams needing auditable decision records without dedicated note-takers Startups juggling 10+ meetings daily without time for manual follow-up Operations teams tracking cross-functional initiatives requiring accountability --- Setup Steps Setup time: 25-35 minutes Requirements: OpenAI API key, Slack workspace, Notion account, Google Workspace (Calendar/Gmail/Sheets), optional transcription service Webhook Trigger: Automatically generates URL, configure as POST endpoint accepting JSON with title, date, attendees, transcript, duration, recording_url, organizer Transcription Integration: Connect Otter.ai/Fireflies.ai/Zoom webhooks, or create manual submission form OpenAI Analysis: Add API credentials, configure GPT-4 or GPT-3.5-turbo, temperature 0.3, max tokens 1500 Intelligence Synthesis: JavaScript calculates priority scores (0-40 range) and completeness metrics (0-100), customize thresholds Slack Integration: Create app with chat:write scope, get bot token, replace channel ID placeholder with your meeting-summaries channel Notion Databases: Create "Meeting Notes" database (title, date, attendees, summary, action items, completeness, recording URL) and "Action Items" database (title, assigned to, due date, priority, status, meeting relation), share both with integration, add token Email Notifications: Configure Gmail OAuth2 or SMTP, customize HTML template with company branding Calendar Reminders: Enable Calendar API, creates events on due dates at 9 AM (adjustable), adds task owner as attendee Analytics Tracking: Create Google Sheet with columns for MeetingID, Title, Date, Attendees, Duration, ActionItems, HighPriority, Decisions, Completeness, UnassignedTasks, FollowUpNeeded Test: POST sample transcript, verify Slack message, Notion entries, emails, calendar events, and Sheets logging --- Customization Guidance Meeting Types: Daily standups (reduce tokens to 500, Slack-only), sprint planning (add Jira integration), client calls (add CRM logging), executive reviews (stricter completeness thresholds) Priority Scoring: Add urgency multiplier for <48hr due dates, owner seniority weights, customer impact flags AI Prompt: Customize to emphasize deadlines, blockers, or technical decisions; add date parsing for phrases like "by end of week" Notification Routing: Critical priority (score >30) → Slack DM + email, High (20-30) → channel + email, Medium/Low → email only Tool Integrations: Add Jira/Linear for ticket creation, Asana/Monday for project management, Salesforce/HubSpot for CRM logging, GitHub for issue creation Analytics: Build dashboards for meeting effectiveness scores, action item velocity, recurring topic clustering, team productivity metrics Cost Optimization: ~1,200 tokens/meeting × $0.002/1K (GPT-3.5) = $0.0024/meeting, use batch API for 50% discount, cache common patterns --- Once configured, this workflow becomes your team's institutional memory—capturing every commitment and decision while eliminating hours of weekly admin work, ensuring accountability is automatic and follow-through is guaranteed. --- Built by Daniel Shashko Connect on LinkedIn
WhatsApp customer support bot with GPT-4 Mini, Google Sheets & Rapiwa API
Who Is This For? This n8n automation workflow is designed for customer support teams, business owners, or service providers who want to automate customer interactions on WhatsApp. If you regularly receive customer queries about your products, services, or technical issues — and need a system that can instantly respond, fetch data from Google Sheets or Docs, log support tickets, and send human-like replies — this workflow is for you. It’s perfect for teams using Rapiwa, Google Sheets, and Google Docs who want to provide a smart, AI-driven, yet personal support experience. What This Workflow Does This workflow is structured around a single intelligent AI assistant called Rapiwa that interacts with customers in real time through WhatsApp. Key Features AI-Driven Support Assistant (Rapiwa) WhatsApp Integration via Rapiwa API Dynamic Data Access (Google Sheets + Docs) Knowledge Base Search Conversation Memory Automatic Logging Multi-Product Support Workflow Overview Rapiwa Trigger (Start Node) Starts the workflow automatically whenever a new WhatsApp message is received in your Rapiwa account. Example: When a customer sends a message like “What’s the price of SocialVibe?” or “I can’t access my dashboard”, this node triggers the workflow. If (Check Text) Detects if the incoming message contains text (not just images, videos, or audio). If it’s text, the workflow continues; otherwise, it stops or handles it differently. AI Agent – Customer Support Agent This is the brain of the system — your AI Assistant (Rapiwa). Interprets the user’s question, retrieves information, and replies in a clear, WhatsApp-friendly format. Reads product details and company info from Google Sheets/Docs. Fetches documentation links from the connected “Support Desk” and product-specific HTTP tools. Logs customer issues to the support sheet for tracking and analysis. Memory (Session Context) Stores chat history per user session so Rapiwa remembers context during a conversation. Research (AI Support Tool) Acts as Rapiwa’s research assistant — gathers and organizes information from multiple sources. Sources: Google Sheets, Google Docs, HTTP Tools, and Support Desk. Replay (Rapiwa Send Message) Sends the AI’s final message back to the customer on WhatsApp using the Rapiwa API. WhatsApp-optimized plain text messages only. Data & Integrations 🔹 Google Sheets (Database) Product Data Sheet: Holds product names, descriptions, and pricing. Service Data Sheet: Lists offered services with details. Support Log Sheet: Records each issue (Issue, Category, Solution). 🔹 Google Docs Provides company information when a user asks about your organization. Example Use Case User Message: > “Hi, I’m having a problem with my Faculty login.” Rapiwa’s AI Response: > “I’m sorry you’re having trouble logging in to Faculty. Please try resetting your password here: https://faculty.spagreen.net/docs/reset-password > If the issue continues, I can log this for support. Would you like me to do that?” Useful Links install process: how to install rapiwa 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