by Growth AI
Advanced Form Submission to CRM Automation with International Phone Support Who's it for Sales teams, marketing professionals, and business owners who need sophisticated lead management with international phone number support, automated CRM record creation, intelligent duplicate detection, and multi-channel team notifications. What it does This advanced workflow automatically processes form submissions from your website and creates a complete, intelligent CRM structure in Pipedrive. It transforms raw form data into organized sales records including companies, contacts, deals, and relevant notes while handling international phone number formatting and providing real-time team notifications via Discord and WhatsApp messaging. How it works The workflow follows an intelligent automation process with four distinct scenarios: Form Trigger: Captures form submissions from your website (Webflow in this example) Advanced Phone Processing: Automatically detects and formats international phone numbers with proper country codes for 20+ countries including France, Belgium, Switzerland, Germany, Spain, Italy, Morocco, Algeria, Tunisia, and more Intelligent CRM Logic: Uses a sophisticated 4-scenario approach: Scenario A: Existing Organization + Existing Person - Links records and creates new deal Scenario B: Existing Organization + New Person - Creates person, links to organization, creates deal Scenario C: New Organization + Existing Person - Creates organization, links person, creates deal Scenario D: New Organization + New Person - Creates complete new structure from scratch Enhanced Data Management: Adds lead source tracking, custom properties, and conditional data enhancement Multi-Channel Communication: Sends formatted alerts to Discord and personalized WhatsApp messages to leads Requirements Webflow account (or any platform that supports webhook triggers) Pipedrive CRM account with proper API credentials Team notification service: Discord, Slack, Microsoft Teams, email service, or any webhook-compatible notification tool WhatsApp Business API access for lead messaging International phone number handling capability How to set up Step 1: Configure your form trigger Default setup: The template uses Webflow Form Trigger with site ID configuration Alternative platforms: Replace with webhook trigger for other platforms (WordPress, custom websites, etc.) Webhook configuration: Set up your website's form to send data to the n8n webhook URL Form fields: Ensure your form captures the necessary fields: Prénom (First Name) Nom (Last Name) Entreprise (Company) Mail professionnel (Professional Email) Téléphone pro (Professional Phone) URL du site internet (Website URL) Message Step 2: Configure API credentials Set up the following credentials in n8n: Webflow OAuth2: For form trigger authentication (or webhook authentication for other platforms) Pipedrive API: For CRM record creation and management - ensure proper permissions for organizations, persons, deals, and notes Discord Bot API: For team notifications with guild and channel access WhatsApp Business API: For automated lead messaging with phone number ID configuration Step 3: Customize international phone formatting The "international dialing code" node automatically handles: European countries: France (+33), Belgium (+32), Switzerland (+41), Germany (+49), Spain (+34), Italy (+39), Portugal (+351) North African countries: Morocco (+212), Algeria (+213), Tunisia (+216) Global coverage: US/Canada (+1), UK (+44), and many Asian countries Fallback handling: Defaults to French formatting for unrecognized patterns Error management: Uses +330000000000 as fallback for invalid numbers Step 4: Configure Pipedrive settings Adjust Pipedrive-specific settings in deal creation nodes: Deal pipeline stage: Currently set to default stage (customize for your pipeline) Deal ownership: Configure owner_id for appropriate team member assignment Currency settings: Adjust currency code for your business region Custom properties: Lead source automatically set to "Growth AI" (customize as needed) Step 5: Set up team notifications Configure your preferred notification system: Discord (default): Set guild ID: 1377297267014504520, channel ID: 1380469490139009106 Alternative platforms: Replace Discord node with Slack, Teams, email, or custom webhook Message formatting: Customize notification content and structure Multi-channel setup: Add multiple notification nodes for different channels Step 6: Configure WhatsApp messaging Set up automated lead engagement: Phone number ID: Configure WhatsApp Business API phone number (currently: 752773604591912) Message personalization: Uses prospect's first name and customizable content International compatibility: Works with formatted international phone numbers Message templates: Customize welcome messages and follow-up content How to customize the workflow Form platform integration Webflow: Use the existing Webflow trigger with site ID configuration WordPress: Replace with webhook trigger and configure Contact Form 7, Gravity Forms, or WPForms Custom websites: Set up webhook trigger with your form's POST endpoint Landing page builders: Configure webhook integration (Unbounce, Leadpages, Instapage, etc.) Form field mapping: Adjust the "Data refinement" node for your specific form structure Advanced CRM customization Pipeline management: Configure different stage IDs for various lead sources Lead scoring: Add conditional logic for deal values based on form responses Custom fields: Map additional form fields to Pipedrive custom properties Multiple pipelines: Route different form types to different sales pipelines Ownership rules: Implement round-robin or territory-based assignment logic International phone number expansion The phone formatting system supports extensive customization: Additional countries: Add new country patterns to the JavaScript code Regional preferences: Modify default formatting rules for specific regions Validation rules: Implement stricter phone number validation Carrier detection: Add mobile vs. landline detection logic Notification enhancements Multi-platform notifications: Send to Discord, Slack, Teams, and email simultaneously Conditional notifications: Route different lead types to different channels Rich formatting: Add embeds, attachments, or rich text formatting Escalation rules: Implement priority-based notification routing Integration expansion: Connect to internal tools or third-party notification services Data validation and enrichment Email validation: Add email verification steps before CRM creation Company enrichment: Integrate with data enrichment services (Clearbit, ZoomInfo, Apollo) Duplicate detection: Enhanced logic to check for existing contacts across multiple fields Lead qualification: Implement sophisticated scoring based on form responses and external data Data cleaning: Add standardization for company names, job titles, and other fields Advanced conditional logic features Intelligent scenario routing The workflow uses sophisticated logic to determine the correct processing path: Organization detection: Exact matching search for existing companies Person identification: Full name matching within relevant organization contexts Relationship preservation: Maintains proper links between organizations, persons, and deals Data consistency: Ensures no duplicate records while preserving historical relationships Smart data handling Enhanced conditional processing includes: Phone number intelligence: Automatic international formatting with country detection Message processing: Creates deal notes only when message field contains meaningful content URL handling: Adds website URLs as separate notes when provided Empty field management: Gracefully handles incomplete form submissions Custom property management: Adds lead source tracking and other metadata Error handling and resilience Graceful failures: Workflow continues even if individual steps fail Data validation: Comprehensive checks for required fields before processing Notification reliability: Ensures team is notified even if some CRM operations fail Logging capabilities: Detailed error tracking for troubleshooting Rollback mechanisms: Ability to handle partial failures without data corruption Results interpretation CRM structure created For each form submission, the workflow creates: Organization record: Complete company information with proper formatting Person record: Contact information linked to correct organization with phone formatting Deal record: Sales opportunity with appropriate stage, owner, and metadata Enhanced notes: Separate notes for messages and website URLs when provided Proper relationships: Full linking between organization, person, and deal records Custom tracking: Lead source attribution and other custom properties Team notifications and engagement Comprehensive communication includes: Discord notifications: Formatted team alerts with complete prospect information WhatsApp engagement: Personalized messages to leads with international number support Immediate alerts: Real-time notifications for instant follow-up capability Formatted display: Clean, organized presentation of all prospect data Multi-channel flexibility: Easy adaptation to any notification platform Advanced use cases International lead generation Global forms: Handle submissions from multiple countries with proper phone formatting Multi-language support: Process forms in different languages with consistent data structure Regional routing: Route leads to appropriate regional sales teams based on phone country codes Currency handling: Automatic currency assignment based on detected country Sophisticated lead management Lead scoring: Advanced qualification based on company size, industry, and message content Progressive profiling: Build complete prospect profiles over multiple interactions Engagement tracking: Monitor response rates and optimize messaging Attribution analysis: Track lead sources and optimize marketing spend Enterprise integration Custom CRM fields: Map to complex Pipedrive custom field structures Multiple pipelines: Route leads to different sales processes based on criteria Team assignment: Intelligent routing based on territory, expertise, or workload Compliance handling: Ensure data processing meets regional privacy requirements Workflow architecture details Processing phases Form capture and data extraction: Webflow trigger processes submitted data International phone formatting: Advanced JavaScript processing for global numbers Organization discovery: Intelligent search and creation logic Person management: Sophisticated duplicate detection and relationship management Deal creation: Context-aware opportunity generation with proper associations Enhanced communication: Multi-channel notifications and lead engagement Performance characteristics Processing time: Typically completes within 10-15 seconds for complex scenarios Reliability: Built-in error handling ensures high success rates Scalability: Handles high-volume form submissions without performance degradation Flexibility: Easy customization for different business requirements and CRM configurations Limitations and considerations Platform dependencies: Currently optimized for Webflow and Pipedrive but adaptable Phone number coverage: Supports 20+ countries but may need expansion for specific regions CRM limitations: Requires proper Pipedrive API permissions and rate limit considerations Form structure: Field mapping requires customization for different form designs Language considerations: Currently configured for French field names but easily adaptable Notification dependencies: Requires proper configuration of Discord and WhatsApp APIs for full functionality
by Kirill Khatkevich
This workflow transforms your Meta Ads creatives into a rich dataset of actionable insights. It's designed for data-driven marketers, performance agencies, and analysts who want to move beyond basic metrics and understand the specific visual and textual elements that drive ad performance. By automatically analyzing every video and image with Google's powerful AI (Video Intelligence and Vision APIs), it systematically deconstructs your creatives into labeled data, ready for correlation with campaign results. Use Case You know some ads perform better than others, but do you know why? Is it the presence of a person, a specific object, the on-screen text, or the spoken words in a video? Answering these questions manually is nearly impossible at scale. This workflow automates the deep analysis process, allowing you to: Automate Creative Analysis:** Stop guessing and start making data-backed decisions about your creative strategy. Uncover Hidden Performance Drivers:** Identify which objects, themes, text, or spoken phrases correlate with higher engagement and conversions. Build a Structured Creative Database:** Create a detailed, searchable log of every element within your ads for long-term analysis and trend-spotting. Save Countless Hours:** Eliminate the tedious manual process of watching, tagging, and logging creative assets. How it Works The workflow is triggered on a schedule and follows a clear, structured path: 1. Configuration & Ad Ingestion: The workflow begins on a schedule (e.g., weekly on Monday at 10 AM). It starts by fetching all active ads from a specific Meta Ads Campaign, which you define in the Set Campaign ID node. 2. Intelligent Branching (Video vs. Image): An IF node inspects each creative to determine its type. Video creatives** are routed to the Google Video Intelligence API pipeline. Image creatives** are routed to the Google Vision API pipeline. 3. The Video Analysis Pipeline: For each video, the workflow gets a direct source URL, downloads the file, and converts it to a Base64 string. It then initiates an asynchronous analysis job in the Google Video Intelligence API, requesting LABEL_DETECTION, SPEECH_TRANSCRIPTION, and TEXT_DETECTION. A loop with a wait timer periodically checks the job status until the analysis is complete. Finally, a Code node parses the complex JSON response, structuring the annotations (like detected objects with timestamps or full speech transcripts) into clean rows. 4. The Image Analysis Pipeline: For each image, the file is downloaded, converted to Base64, and sent to the Google Vision API. It requests a wide range of features, including label, text, logo, and object detection. A Code node parses the response and formats the annotations into a standardized structure. 5. Data Logging & Robust Error Handling: All successfully analyzed data from both pipelines is appended to a primary Google Sheet. The workflow is built to be resilient. If an error occurs (e.g., a video fails to be processed by the API, or an image URL is missing), a detailed error report is logged to a separate errors sheet in your Google Sheet, ensuring no data is lost and problems are easy to track. Setup Instructions To use this template, you need to configure a few key nodes. 1. Credentials: Connect your Meta Ads account. Connect your Google account. This account needs access to Google Sheets and must have the Google Cloud Vision API and Google Cloud Video Intelligence API enabled in your GCP project. 2. The Set Campaign ID Node: This is the primary configuration step. Open this Set node and replace the placeholder value with the ID of the Meta Ads campaign you want to analyze. 3. Google Sheets Nodes: You need to configure two Google Sheets nodes: Add Segments data:** Select your spreadsheet and the specific sheet where you want to save the successful analysis results. Ensure your sheet has the following headers: campaign_id, ad_id, creative_id, video_id, file_name, image_url, source, annotation_type, label_or_text, category, full_transcript, confidence, start_time_s, end_time_s, language_code, processed_at_utc. Add errors:** Select your spreadsheet and the sheet you want to use for logging errors (e.g., a sheet named "errors"). Ensure this sheet has headers like: error_type, error_message, campaign_id, ad_id, creative_id, file_name, processed_at_utc. 4. Activate the Workflow: Set your desired frequency in the Run Weekly on Monday at 10 AM (Schedule Trigger) node. Save and activate the workflow. Further Ideas & Customization This workflow provides the "what" inside your creatives. The next step is to connect it to performance. Build a Performance Analysis Workflow:** Create a second workflow that reads this Google Sheet, fetches performance data (spend, clicks, conversions) for each ad_id from the Meta Ads API, and merges the two datasets. This will allow you to see which labels correlate with the best performance. Create Dashboards:** Use the structured data in your Google Sheet as a source for a Looker Studio or Tableau dashboard to visualize creative trends. Incorporate Generative AI:** Add a final step that sends the combined performance and annotation data to an LLM (like in the example you provided) to automatically generate qualitative summaries and recommendations for each creative. Add Notifications:** Use the Slack or Email nodes to send a summary after each run, reporting how many creatives were analyzed and if any errors occurred.
by Cheng Siong Chin
Introduction Automate price monitoring for e-commerce competitors—ideal for retailers, analysts, and pricing teams. Scrapes competitor sites, extracts pricing/stock data via AI, detects changes, and sends instant alerts for dynamic pricing strategies. How It Works Scrapes competitor URLs via Firecrawl and Apify, extracts data with AI, detects price/stock changes, logs to Google Sheets, and sends Telegram alerts. Workflow Template Trigger → Scrape URL → AI Extract → Parse → Merge Historical → Detect Changes → Update Sheets + Send Telegram Alert Workflow Steps Trigger & Scrape → Manual/scheduled trigger → Firecrawl + Apify fetch competitor data AI Processing → Claude extracts product details → Parses and structures data Change Detection → Reads historical prices → Merges with current data → Identifies updates Output → Logs alerts to Sheets → Updates historical data → Sends Telegram notification Setup Instructions 1. Firecrawl API Get key from dashboard → Add to n8n 2. Apify API Get key from console → Add to n8n → Configure actors 3. AI Model (Claude/OpenAI) Get API key → Add to n8n 4. Google Sheets OAuth2 Create OAuth2 in Google Cloud Console → Authorize in n8n → Enable API 5. Telegram Bot Create via BotFather → Get token & chat ID → Add to n8n 6. Spreadsheet Setup Create Sheet with required columns → Copy ID → Paste in workflow Prerequisites Self-hosted n8n, Firecrawl account, Apify account, Claude/OpenAI API key, Google account (Sheets OAuth2),Telegram bot Customization Add more URLs, adjust scraping intervals, change detection thresholds, switch to Slack/email alerts, integrate databases Benefits Saves 2+ hours daily, real-time tracking, automated alerts, historical analysis, multi-source scraping
by Jitesh Dugar
👤 Who’s it for This workflow is designed for employees who need to submit expense claims for business trips. It automates the process of extracting data from receipts/invoices, logging it to a Google Sheet, and notifying the finance team via email. Ideal users: Employees submitting business trip expense claims HR or Admins reviewing travel-related reimbursements Finance teams responsible for processing claims ⚙️ How it works / What it does Employee submits a form with trip information (name, department, purpose, dates) and uploads one or more receipts/invoices (PDF). Uploaded files are saved to Google Drive for record-keeping. Each PDF is passed to a DocClaim Assistant agent, which uses GPT-4o and a structured parser to extract structured invoice data. The data is transformed and formatted into a standard JSON structure. Two parallel paths are followed: Invoice records are appended to a Google Sheet for centralized tracking. A detailed HTML email summarizing the trip and expenses is generated and sent to the finance department for claim processing. 🛠 How to set up Create a form to capture: Employee Name Department Trip Purpose From Date / To Date Receipt/Invoice File Upload (multiple PDFs) Configure file upload node to store files in a specific Google Drive folder. Set up DocClaim Agent using: GPT-4o or any LLM with document analysis capability Output parser for standardizing extracted receipt data (e.g., vendor, total, tax, date) Transform extracted data into a structured claim record (Code Node). Path 1: Save records to a Google Sheet (one row per expense). Path 2: Format the employee + claim data into a dynamic HTML email Use Send Email node to notify the finance department (e.g., finance@yourcompany.com) ✅ Requirements Jotform account with expense form setup Sign up for free here n8n running with access to: Google Drive API (for file uploads) Google Sheets API (for logging expenses) Email node (SMTP or Gmail for sending) GPT-4o or equivalent LLM with document parsing ability PDF invoices with clear formatting Shared Google Sheet for claim tracking Optional: Shared inbox for finance team 🧩 How to customize the workflow Add approval steps**: route the email to a manager before finance Attach original PDFs**: include uploaded files in the email as attachments Localize for other languages**: adapt form labels, email content, or parser prompts Sync to ERP or accounting system**: replace Google Sheet with QuickBooks, Xero, etc. Set limits/validation**: enforce max claim per trip or required fields before submission Auto-tag expenses**: add categories (e.g., travel, accommodation) for better reporting
by Oneclick AI Squad
Analyzes influencer profiles and scores authenticity before brand partnership approval. Detects fake followers, bot accounts, and suspicious engagement patterns using AI-powered behavioral analysis. 🎯 How It Works Simple 7-Node Workflow: Input → Submit influencer username and platform (Instagram/Twitter/TikTok) Fetch → Retrieve complete profile data and engagement metrics Analyze → Examine follower patterns, ratios, growth velocity, engagement AI Check → Deep behavioral analysis with Claude AI Report → Generate comprehensive fraud assessment Notify → Send detailed email report to partnership team Log → Save to database for tracking 📊 Detection Capabilities Follower Authenticity**: Analyzes follower-to-following ratio (red flag if < 0.5) Engagement Quality**: Calculates engagement rate (industry avg: 1-5%) Growth Patterns**: Detects suspicious rapid follower spikes Content Consistency**: Evaluates posting frequency and regularity Profile Completeness**: Checks verification, bio, activity AI Behavioral Analysis**: Deep pattern recognition for sophisticated fraud ⚙️ Setup Instructions 1. Configure API Access Social Platform APIs: Instagram**: Get Graph API access token from Meta for Developers Twitter**: OAuth 2.0 credentials from Twitter Developer Portal TikTok**: Business API credentials (optional) AI Analysis: Anthropic Claude API**: Get key from console.anthropic.com Used for advanced behavioral fraud detection 2. Setup Notifications Configure SMTP in "Send Report" node Update recipient email (partnerships@company.com) Customize HTML template if needed 3. Database (Optional) Create PostgreSQL table (schema below) Add database credentials to final node Skip if you don't need historical tracking Database Schema CREATE TABLE partnerships.influencer_fraud_reports ( id SERIAL PRIMARY KEY, report_id VARCHAR(255) UNIQUE, username VARCHAR(255), platform VARCHAR(50), profile_url TEXT, followers BIGINT, following BIGINT, posts INTEGER, verified BOOLEAN, authenticity_score INTEGER, risk_level VARCHAR(50), final_decision TEXT, partnership_recommendation VARCHAR(100), ai_verdict VARCHAR(50), ai_confidence VARCHAR(20), red_flags JSONB, fake_follower_estimate VARCHAR(20), detailed_analysis JSONB, created_at TIMESTAMP ); 🚀 How to Use Webhook Endpoint: POST /webhook/influencer-fraud-check Request Body: { "username": "influencer_handle", "platform": "instagram" // or "twitter", "tiktok" } Example: curl -X POST https://your-n8n.com/webhook/influencer-fraud-check \ -H "Content-Type: application/json" \ -d '{"username":"example_user","platform":"instagram"}' 📈 Scoring System Overall Authenticity Score (0-100): 80-100**: LOW RISK → Approved for partnership 60-79**: MEDIUM RISK → Requires manual review 40-59**: HIGH RISK → Caution advised 0-39**: CRITICAL RISK → Rejected Weighted Components: Follower Quality (25%) Engagement Quality (35%) Content Consistency (15%) Growth Pattern (15%) Profile Completeness (10%) Final Score = 70% Automated + 30% AI Analysis 🚩 Red Flags Detected Following-to-follower ratio > 2:1 Engagement rate < 0.5% Rapid growth (>50K followers/month) Large following with <10 posts No verification with >100K followers Bot-like comment patterns Suspicious audience demographics 💰 Cost Estimate Instagram/Twitter API**: Free tier usually sufficient Claude AI**: ~$0.10-0.20 per analysis Estimated**: $5-10/month for 50 checks 💡 Best Practices Always verify HIGH and MEDIUM risk profiles manually Cross-reference with other influencer databases Request media kit and past campaign results Trial campaigns before large commitments Monitor performance metrics post-partnership Update detection thresholds based on your findings 🎯 What You Get Detailed Report Includes: Overall authenticity score (0-100) Risk level classification Partnership recommendation (APPROVE/REVIEW/REJECT) Engagement quality analysis Fake follower percentage estimate AI behavioral insights Specific red flags and concerns Next steps and recommendations
by Hassan
Quick overview When a buyer misses a scheduled viewing, this workflow automatically sends an AI-personalized follow-up by email and WhatsApp using Google Gemini, then logs the outcome to Google Sheets, recovering leads that would otherwise go cold. How it works Triggers every 15 minutes when a Google Calendar event is updated in the selected viewings calendar. Checks the event title/summary and continues only if it contains the tag “no-show”. Extracts the lead’s name, email, phone, property address, and scheduled viewing time from the calendar event details. Sends the lead and viewing context to Google Gemini to generate an email message and a WhatsApp message in JSON format. Parses and cleans the AI output into safe HTML for email and a trimmed plain-text WhatsApp message. Sends the re-engagement email via Gmail and appends the follow-up outcome to a Google Sheets log. If a phone number is available, sends the WhatsApp message and updates a Google Sheets status field to record that WhatsApp was sent. Setup Connect credentials for Google Calendar, Gmail, Google Sheets, and a Google Gemini (PaLM) API key. Select the correct Google Calendar (viewings calendar) and ensure missed appointments are consistently tagged with “no-show” in the event summary. Create or choose a Google Sheets document and sheet, then fill in the document ID/URL, sheet name, and the columns expected by the append/update logging steps. Configure WhatsApp credentials in n8n (or disable the WhatsApp branch) and ensure lead phone numbers are stored in the calendar event description in the expected format (e.g., Name: ... | Email: ... | Phone: ... |). Requirements Before running this workflow, create a Google Sheet with these exact column headers: Record ID | Lead Name | Email | Phone | Property Address | Original Viewing Time | Email Sent | WhatsApp Sent | Email Message Text | WhatsApp Message Text | Timestamp Customization Edit the AI prompt in "Draft Re-Engagement Messages" to change tone or language Add SMS or other channels by duplicating the WhatsApp branch pattern Adjust the "no-show" tag keyword if your calendar uses different terminology Additional info WhatsApp is optional. If you don't have WhatsApp Business Cloud API credentials, disable that branch — the email follow-up will still send normally. This template assumes calendar events are tagged with "no-show" in the title and include lead contact info in the event description (Name: ... | Email: ... | Phone: ... |).
by DigiMetaLab
How it works: Daily Trigger: Every morning at 8 AM, the workflow is automatically triggered. Fetch Trending Topics: The workflow collects trending topics from external sources, such as news RSS feeds and Reddit popular posts. These trends are merged and summarized to provide up-to-date context for content generation. Read Active Campaigns: The workflow reads all rows from the “Active Campaigns” Google Sheet, but only processes campaigns with a status of "active" to avoid generating content for paused or inactive campaigns. Enrich Campaigns with Trends: Each active campaign is enriched with the latest trending topics, so the generated content can reference current events or popular themes. AI Content Generation: For each enriched campaign, Groq AI generates: An engaging post caption tailored to the platform and target audience Creative direction with visual suggestions Relevant hashtags (5-10) Best posting time recommendation for the platform Quality Scoring: The workflow calculates a quality score for each generated content idea, considering factors like caption length, hashtag count, and creative direction. Append to Google Sheets: The generated content ideas, along with their quality scores and other details, are appended to the “Daily Content Plan” Google Sheet for record-keeping and team collaboration. Schedule in Google Calendar: For each campaign, an event is created in Google Calendar with the content details and recommended posting time, ensuring the team is reminded to review or publish the content. Daily Email Summary (Optional): At the end of the process, a summary email can be sent to the team, including statistics such as the number of campaigns processed, average quality score, and a platform breakdown. Set up steps: Prepare Your Google Sheets: Create a sheet named “Active Campaigns” with columns: Project Name, Theme, Target Audience, Platform, and Status (to mark campaigns as active/inactive). Create another sheet named “Daily Content Plan” with columns for Project Name, Date, Platform, Caption, Creative Direction, Hashtags, and any other details you want to track. Connect Google Services to n8n: In n8n, set up and authenticate your Google Sheets and Google Calendar credentials. You can find authentication information in the n8n documentation for Google credentials. Add a Cron Node: Drag in a Cron node and set it to trigger every day at 8:00 AM. Read Campaigns from Google Sheets: Add a Google Sheets node. Set the operation to “Read Rows” and select your “Active Campaigns” sheet. (Optional) Use a Filter or IF node to process only rows where Status is “active”. (Optional) Fetch Trending Topics: If you want to enrich your content with trending topics, add nodes to fetch data from RSS feeds, Reddit, or other sources. Process Each Campaign: Use a SplitInBatches node to process each campaign row individually. Generate Content Ideas with Groq AI: Add a Groq AI node (or OpenAI node if Groq is not available). Configure the prompt to generate a content idea using the campaign’s theme, target audience, and platform. You can reference fields from the Google Sheets node using expressions like $("Google Sheets").item.json['Theme']. Append Results to “Daily Content Plan”: Add another Google Sheets node. Set the operation to “Append” and select your “Daily Content Plan” sheet. Map the generated content fields to the appropriate columns. Schedule Events in Google Calendar: Add a Google Calendar node. Set the operation to “Create Event”. Use the project name and content idea for the event title and description, and set the event time as needed. (Optional) Send a Daily Summary Email: Add an Email node to send a summary of the day’s content plan to your team. Test the Workflow: Run the workflow manually to ensure all steps work as expected. Check that new content ideas appear in the “Daily Content Plan” sheet and that events are created in Google Calendar. Activate the Workflow: Once you’ve confirmed everything works, activate the workflow so it runs automatically every morning.
by Alejandro Alfonso
Terms of Service Change Watcher with AI Summaries Automatically monitors Terms of Service, Privacy Policy, and other legal pages for changes. When content changes are detected, GPT-4o analyzes the old vs new text and emails you a plain-English summary with an impact rating. How it works Every day at 8 AM, the workflow reads your list of URLs from a Google Sheet Each page is fetched and stripped to plain text The text is compared against the previously stored version If a change is detected, the old and new content are sent to GPT-4o for analysis You receive an email with a summary of exactly what changed and how it impacts you All changes are logged to a Change Log sheet for a historical record Setup Create a Google Sheet with two tabs: Pages (columns: url, page_name, last_content, last_checked) and Change Log (columns: date, page_name, url, summary) Add the URLs you want to monitor in the Pages tab — leave last_content and last_checked empty Connect your Google Sheets OAuth2, Gmail OAuth2, and OpenAI API credentials Update the Google Sheet document in all four Google Sheets nodes Set your email address in the Send Change Alert node Run once to save baselines, then activate the workflow
by Yaron Been
Analyze Reddit sentiment around competitor brands using Bright Data URL-based scraping and GPT-5.4. This workflow Reads competitor post URLs from Google Sheets, scrapes Reddit posts via URL using Bright Data's Reddit Posts API, and uses GPT-5.4 to map sentiment distribution. The AI calculates positive, neutral, and negative sentiment percentages, extracts top complaints and praises, identifies vulnerability areas, and scores the competitive opportunity (0-100). High-opportunity brands trigger alerts to the strategy team. How it works: Weekly schedule trigger runs on Monday at 8 AM. Reads the 'competitor_brands' sheet (columns: brand_name, url, industry). Sends each URL to Bright Data for Reddit post discovery. Validates the Bright Data API response. GPT-5.4 analyzes sentiment distribution and identifies competitive opportunities. Parses AI output and merges with original brand data. Filters by AI confidence (>= 0.7). Brands with competitive_opportunity_score >= 70 trigger email alerts and go to 'high_opportunity_brands'. Lower-scoring brands go to 'competitor_sentiment'. Low-confidence results go to 'low_confidence_sentiment'. Setup: Create a Google Sheet with a 'competitor_brands' tab containing columns: brand_name, url, industry. Create output tabs: high_opportunity_brands, competitor_sentiment, low_confidence_sentiment. Configure Bright Data API credentials as HTTP Header Auth (Bearer token). Connect OpenAI, Google Sheets, and Gmail OAuth2 credentials. Requirements: Bright Data API account (~$0.003-0.005 per URL scrape). OpenAI API account (GPT-5.4 costs ~$0.003-0.008 per call). Google Sheets OAuth2 credentials. Gmail OAuth2 credentials. Notes: Track competitive_opportunity_score over time to spot widening vulnerabilities. Use the vulnerability_areas field to inform your product positioning and messaging. Combine with your own product monitoring (Template 21) for a complete competitive picture.
by Oneclick AI Squad
This automated n8n workflow transforms uploaded radiology images into professional, patient-friendly PDF reports. It uses AI-powered image analysis to interpret medical scans, simplify technical terms, and produce clear explanations. The reports are formatted, converted to PDF, stored in a database, and sent directly to patients via email, ensuring both accuracy and accessibility. 🏥 Workflow Overview: Simple Process Flow: Upload Image → 2. AI Analysis → 3. Generate Report → 4. Send to Patient 🔧 How It Works: Webhook Trigger - Receives image uploads via POST request Extract Image Data - Processes patient info and image data AI Image Analysis - Uses GPT-4 Vision to analyze the radiology image Process Analysis - Structures the AI response into readable sections Generate PDF Report - Creates a beautiful HTML report Convert to PDF - Converts HTML to downloadable PDF Save to Database - Logs all reports in Google Sheets Email Patient - Sends the report via email Return Response - Confirms successful processing 📊 Key Features: AI-Powered Analysis** using GPT-4 Vision Patient-Friendly Language** (no medical jargon) Professional PDF Reports** with clear sections Email Delivery** with report attachment Database Logging** for record keeping Simple Webhook Interface** for easy integration 🚀 Usage Example: Send POST request to webhook with: { "patient_name": "John Smith", "patient_id": "P12345", "scan_type": "X-Ray", "body_part": "Chest", "image_url": "https://example.com/xray.jpg", "doctor_name": "Dr. Johnson", "patient_email": "john@email.com" } ⚙️ Required Setup: OpenAI API - For GPT-4 Vision image analysis PDF Conversion Service - HTML to PDF converter Gmail Account - For sending reports Google Sheets - For logging reports Replace YOUR_REPORTS_SHEET_ID with your actual sheet ID Want a tailored workflow for your business? Our experts can craft it quickly Contact our team
by Hans Wilhelm Radam
📌 Title (SEO-Friendly) Automate Facebook Messenger orders to Google Sheets and Google Calendar Introduction This workflow automates Facebook Messenger order management by connecting your Facebook Page with Google Sheets and Google Calendar. It’s designed to help small businesses save time, reduce errors, and streamline order-taking. Every time a customer messages your page, they receive a structured order form, their responses are parsed, and the details are saved directly to Google Sheets. The same workflow also creates a Google Calendar event, ensuring you never miss a delivery or pickup schedule. Who’s It For Small businesses** selling products through Facebook Messenger. Entrepreneurs** who want to eliminate manual order-taking. Teams** that need a centralized order tracker (Google Sheets) and automatic reminders (Google Calendar). How It Works Listen to incoming messages on Facebook Messenger. Send an automated greeting and order form to the customer. Parse their responses (items, quantity, payment method, etc.). Save order details into Google Sheets for easy tracking. Create a matching Google Calendar event for the order date/time. Send a confirmation message and an optional upsell suggestion. Requirements Facebook Page** with Messenger enabled. Meta for Developers account** to create a Facebook App and generate a Page Access Token. Google Sheets** account with a spreadsheet containing the following columns: Date, Customer Name, Order Details, Payment Method, Order Status, Notes Google Calendar** account for order scheduling. n8n instance** (cloud or self-hosted). 💡 Security Best Practice: Store your Page Access Token and Google credentials in n8n Credentials (not hardcoded in nodes). Setup Instructions 1. Facebook Messenger Connection Go to Meta for Developers. Create a Messenger App and generate a Page Access Token. Copy the Webhook URL from your n8n Webhook Trigger node. Add the webhook URL and verify it in your Facebook Page settings. 2. Google Sheets Setup Create a new spreadsheet named Messenger Orders. Add columns: Date, Customer Name, Order Details, Payment Method, Order Status, Notes. Share the sheet with the Google account connected in n8n. 3. Google Calendar Setup Connect your Google Calendar credentials in n8n. Select the calendar where orders should be added. 4. Import & Configure Workflow Download this workflow template. Replace placeholders ({{YOUR_PAGE_ACCESS_TOKEN}}, {{YOUR_GOOGLE_SHEET_ID}}, etc.). Test by sending a message to your Facebook Page. Customization Personalize messages** in the Messenger node (greeting, upsell suggestions). Add extra fields such as delivery address or contact number to both the form and the Google Sheet. Extend the workflow by adding Telegram, Email, or SMS notifications for customers or staff. Use Filter nodes to route VIP orders or high-value purchases to a separate workflow. ⚡ Final Flow: Facebook Messenger → Order Form → Google Sheets → Google Calendar → Customer Confirmation 💬 Call to Action: Clone this workflow, connect your accounts, and start automating your Messenger orders in minutes!
by Mohammad Abubakar
This n8n template demonstrates how to capture website leads via a webhook, validate the data, optionally enrich it, store it in your CRM (HubSpot) or a simple Google Sheet, and instantly notify your team via email and Slack. This is ideal for agencies, freelancers, SaaS founders, and small sales teams who want every lead recorded and followed up automatically within seconds. Good to know The workflow supports two storage options: HubSpot or Google Sheets (choose one branch). Enrichment (Clearbit/Hunter) is optional and can be disabled with a single toggle/IF branch. Consider adding anti-spam (honeypot/captcha) if your form gets abused. How it works Webhook receives the lead Your website form sends a POST request to the Webhook URL with lead fields (name, email, message, etc.). Validation & normalization The workflow trims and normalizes fields (like lowercasing email) and checks required fields. If invalid, it returns a Optional enrichment (Clearbit/Hunter) If enrichment is enabled, the workflow calls an enrichment API and merges results into the lead object (industry, company size, domain, etc.). If enrichment fails, the workflow continues (doesn’t block lead capture). Save lead to CRM (Choose one) HubSpot branch**: find contact by email → create or update the contact record Google Sheets branch**: lookup row by email → update if found → otherwise append a new row Instant notifications Posts a Slack message to a channel, optionally including a CRM/Sheet link Success response to the website Returns a #### How to use? Import the workflow into n8n. Configure the Webhook node and copy the production URL into your website form submit action. Choose your storage path: Enable HubSpot nodes OR Enable Google Sheets nodes Add credentials: Slack credential (Optional) HubSpot / Google Sheets (Optional) Clearbit/Hunter keys in the HTTP Request node Send a test lead from your website and confirm: Lead saved correctly Email received Slack notification posted Website receives a 200 response Requirements An n8n instance (cloud or self-hosted) One of: HubSpot account (for CRM storage), or Google account + Google Sheets (for spreadsheet storage) Slack workspace + Slack credentials Optional: Clearbit/Hunter account for enrichment