HumationHuman + Automation
Back to Catalog

Newsletter signup flow with Email Verification API, Gmail & Google Sheets tracking

Jitesh DugarJitesh Dugar
245 views
2/3/2026
Google SheetsSlackNotificationsAutomationGoogle Forms
Official Page

Newsletter Sign-up with Email Verification & Welcome Email Automation

📋 Description

A complete, production-ready newsletter automation workflow that validates email addresses, sends personalized welcome emails, and maintains comprehensive logs in Google Sheets. Perfect for marketing teams, content creators, and businesses looking to build high-quality email lists with minimal manual effort.

✨ Key Features

Email Verification

  • Real-time validation using Verifi Email API
  • Checks email format (RFC compliance)
  • Verifies domain existence and MX records
  • Detects disposable/temporary email addresses
  • Identifies potential spoofed emails

Automated Welcome Emails

  • Personalized HTML emails with subscriber's first name
  • Beautiful, mobile-responsive design with gradient headers
  • Branded confirmation and unsubscribe links
  • Sent via Gmail (or SMTP) automatically to valid subscribers

Smart Data Handling

  • Comprehensive logging to Google Sheets with three separate tabs
  • Handles incomplete submissions gracefully
  • Preserves original user data throughout verification process
  • Tracks source attribution for multi-channel campaigns

Error Management

  • Automatic retry logic on API failures
  • Separate logging for different error types
  • Detailed technical reasons for invalid emails
  • No data loss with direct webhook referencing

🎯 Use Cases

  • Newsletter sign-ups on websites and landing pages
  • Lead generation forms with quality control
  • Marketing campaigns requiring verified email lists
  • Community building with automated onboarding
  • SaaS product launches with email collection
  • Content creator audience building
  • E-commerce customer list management

📊 What Gets Logged

Master Log (All Subscribers)

  • Timestamp, name, email, verification result
  • Verification score and email sent status
  • Source tracking, disposable status, domain info

Invalid Emails Log

  • Detailed rejection reasons
  • Technical diagnostic information
  • MX record status, RFC compliance
  • Provider information for troubleshooting

Invalid Submissions Log

  • Incomplete form data
  • Missing required fields
  • Timestamp for follow-up

🔧 Technical Stack

Trigger: Webhook (POST endpoint)
Email Verification: Verifi Email API
Email Sending: Gmail OAuth2 (or SMTP)
Data Storage: Google Sheets (3 tabs)
Processing: JavaScript code nodes for data formatting

🚀 Setup Requirements

  1. Google Account - For Sheets and Gmail integration
  2. Verifi Email API Key - (https://verifi.email)
  3. Google Sheets - Pre-configured with 3 tabs (template provided)
  4. 5-10 minutes - Quick setup with step-by-step instructions included

📈 Benefits

✅ Improve Email Deliverability - Remove invalid emails before sending campaigns
✅ Reduce Bounce Rates - Only send to verified, active email addresses
✅ Save Money - Don't waste email credits on invalid addresses
✅ Better Analytics - Track conversion rates by source
✅ Professional Onboarding - Personalized welcome experience
✅ Scalable Solution - Handles high-volume sign-ups automatically
✅ Data Quality - Build a clean, high-quality subscriber list

🎨 Customization Options

  • Email Template - Fully customizable HTML design
  • Verification Threshold - Adjust score requirements
  • Brand Colors - Match your company branding
  • Confirmation Flow - Add double opt-in if desired
  • Multiple Sources - Track different signup forms
  • Language - Easily translate email content

📦 What's Included

  • ✅ Complete n8n workflow JSON (ready to import)
  • ✅ Google Sheets template structure
  • ✅ Responsive HTML email template
  • ✅ Setup documentation with screenshots
  • ✅ Troubleshooting guide
  • ✅ Customization examples

🔒 Privacy & Compliance

  • GDPR-compliant with unsubscribe links
  • Secure data handling via OAuth2
  • No data shared with third parties
  • Audit trail in Google Sheets
  • Easy data deletion/export

💡 Quick Stats

  • 12 Nodes - Fully automated workflow
  • 3 Data Paths - Valid, invalid, and incomplete submissions
  • 100% Uptime - When properly configured
  • Instant Processing - Real-time email verification
  • Unlimited Scale - Based on your API limits

🏆 Perfect For

  • Marketing Agencies
  • SaaS Companies
  • Content Creators
  • E-commerce Stores
  • Community Platforms
  • Educational Institutions
  • Membership Sites
  • Newsletter Publishers

🌟 Why Use This Workflow?

Instead of manually verifying emails or dealing with bounce complaints, this workflow automates the entire process from sign-up to welcome email. Save hours of manual work, improve your email deliverability, and create a professional first impression with every new subscriber.

Start building a high-quality email list today!

Newsletter Signup Flow with Email Verification, Google Sheets Tracking, and Gmail Confirmation

This n8n workflow automates the process of signing up new subscribers for a newsletter, including email verification, tracking signups in Google Sheets, and sending a confirmation email via Gmail.

What it does

  1. Receives Signup Data: Listens for new newsletter signup requests via a webhook.
  2. Verifies Email (Placeholder): Includes a Code node, which is typically used for custom logic like calling an email verification API. Note: The current JSON does not include actual email verification logic, but the node is in place for it.
  3. Conditional Processing: Uses an If node to branch the workflow based on the email verification result.
    • If Valid: Proceeds to record the signup and send a confirmation.
    • If Invalid: (No explicit path defined in the JSON, but could be extended to send an error or log invalid attempts).
  4. Tracks Signups in Google Sheets: Appends the new subscriber's details (e.g., email, signup date) to a specified Google Sheet.
  5. Sends Confirmation Email: Sends a personalized welcome email to the new subscriber using Gmail.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance.
  • Google Sheets Account: To track newsletter signups.
    • A Google Sheets credential configured in n8n.
    • A Google Sheet prepared with columns for subscriber data (e.g., Email, Signup Date).
  • Gmail Account: To send confirmation emails.
    • A Gmail credential configured in n8n.
  • Email Verification API (Optional but Recommended): An API key and access to an email verification service (e.g., MailboxValidator, ZeroBounce) if you intend to implement robust email verification. The Code node is a placeholder for this integration.

Setup/Usage

  1. Import the Workflow: Import the provided JSON into your n8n instance.
  2. Configure Credentials:
    • Google Sheets Node: Select or create a Google Sheets OAuth2 credential.
    • Gmail Node: Select or create a Gmail OAuth2 credential.
  3. Configure Google Sheets Node (ID: 18):
    • Specify the Spreadsheet ID of your Google Sheet.
    • Specify the Sheet Name where signups will be recorded.
    • Ensure the operation is set to "Append Row" or similar, and map the incoming data to your sheet columns (e.g., {{ $json.email }} to an "Email" column).
  4. Configure Gmail Node (ID: 356):
    • Set the "To" email address using an expression like {{ $json.email }}.
    • Customize the "Subject" and "Body" of the confirmation email.
  5. Configure Webhook Node (ID: 47):
    • The Webhook URL will be generated automatically once the workflow is activated. This URL will be the endpoint to which your signup form submits data.
    • Ensure your signup form sends data (e.g., email) to this webhook URL, typically as a POST request.
  6. Configure If Node (ID: 20):
    • Modify the If node's conditions to evaluate the output of the Code node (email verification result). For example, if the Code node returns a boolean isValid property, the condition might be {{ $json.isValid }} is "true".
  7. Configure Code Node (ID: 834):
    • Important: This node is a placeholder. You will need to add custom JavaScript code here to integrate with an email verification API.
      • The code should take the incoming email address (e.g., from {{ $json.email }}) as input.
      • It should make an API call to your chosen email verification service.
      • It should return a boolean value (e.g., isValid: true/false) that the If node can then evaluate.
  8. Activate the Workflow: Once configured, activate the workflow.

Now, any data sent to the webhook URL will trigger the workflow, process the signup, and send a confirmation email if the email is deemed valid.

Related Templates

Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets

This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.

Ranjan DailataBy Ranjan Dailata
161

Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax

Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions

Daniel NkenchoBy Daniel Nkencho
601

Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation

PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.

Le NguyenBy Le Nguyen
942