HumationHuman + Automation
Back to Catalog

Personalized cold email generator with Supabase, Smartlead & Google Gemini AI

Rahi UppalRahi Uppal
651 views
2/3/2026
TrelloWordPressAutomationContent ManagementPublishing
Official Page

n8n Workflow: AI-Personalized Email Outreach (Smartlead)

🔄 Purpose

This workflow automates cold email campaigns by:

  • Fetching leads
  • Generating hyper-personalized email content using AI
  • Sending emails via Smartlead API
  • Logging campaign activity into Google Sheets

🧩 Workflow Structure

  1. Schedule Trigger

    • Starts the workflow automatically at scheduled intervals.
    • Ensures continuous campaign execution.

  2. Get Leads

    • Fetches lead data (name, email, company, role, industry).
    • Serves as the input for personalization.

  3. Loop Over Leads

    • Processes each lead one by one.
    • Maintains individualized email generation.

  4. Aggregate Lead Data

    • Collects and formats lead attributes.
    • Prepares structured input for the AI model.

  5. Basic LLM Chain #1

    • Generates personalized snippets/openers using AI.
    • Tailored based on company, role, and industry.

  6. Update Row (Google Sheets)

    • Saves AI outputs (snippets) for tracking and QA.

  7. Basic LLM Chain #2

    • Expands snippet into a full personalized email draft.
    • Includes subject line + email body.

  8. Information Extractor

    • Extracts structured fields from AI output:
      • Subject
      • Greeting
      • Call-to-Action (CTA)
      • Closing

  9. Update Row (Google Sheets)

    • Stores finalized draft in Google Sheets.
    • Provides visibility and audit trail.

  10. Code

    • Formats email into Smartlead-compatible payload.
    • Maps fields like subject, body, and recipient details.

  11. Smartlead API Request

    • Sends the personalized email through Smartlead.
    • Returns message ID and delivery status.

  12. Basic LLM Chain #3 (Optional)

    • Generates follow-up versions for multi-step campaigns.
    • Ensures varied engagement over time.

  13. Information Extractor (Follow-ups)

    • Structures follow-up emails into ready-to-send format.

  14. Update Row (Google Sheets)

    • Updates campaign logs with:
      • Smartlead send status
      • Message IDs
      • AI personalization notes

⚙️ Data Flow Summary

  • Trigger → Runs workflow
  • Get Leads → Fetch lead records
  • LLM Personalization → Create openers + full emails
  • Google Sheets → Save drafts & logs
  • Smartlead API → Send personalized email
  • Follow-ups → Generate and log structured follow-up messages

📊 Use Case

  • Automates hyper-personalized cold email outreach at scale.
  • Uses AI to improve response rates with contextual personalization.
  • Provides full visibility by saving drafts and send logs in Google Sheets.
  • Integrates seamlessly with Smartlead for sending and tracking.

Personalized Cold Email Generator with Supabase, Smartlead & Google Gemini AI

This n8n workflow automates the generation of personalized cold emails using AI, leveraging data from Supabase and preparing it for a bulk email sender like Smartlead. It streamlines the outreach process by creating tailored content for each prospect.

What it does

This workflow is designed to:

  1. Trigger on Schedule: Initiates the workflow at predefined intervals (e.g., daily, weekly).
  2. Fetch Prospect Data: Retrieves a list of prospects from a Supabase database.
  3. Process Prospects in Batches: Iterates through each prospect individually to ensure personalized processing.
  4. Generate Personalized Email Content:
    • Uses a "Basic LLM Chain" (likely powered by Google Gemini AI) to generate an initial draft of a personalized cold email based on prospect data.
    • Employs an "Information Extractor" (also likely AI-powered) to refine and structure the generated email content, ensuring it meets specific criteria or extracts key data points.
  5. Aggregate Results: Collects all the generated personalized emails after individual processing.
  6. Conditional Logic: Includes an "If" node, which suggests a conditional step for further processing or filtering based on the generated email content or prospect data. (Note: The specific condition is not defined in the provided JSON, but it indicates a branching point.)
  7. Send to Smartlead (Implied): While not explicitly defined in the provided JSON, the workflow's directory name ("7713-personalized-cold-email-generator-with-supabase-smartlead--google-gemini-ai") strongly suggests that the generated emails are intended to be sent to a platform like Smartlead for bulk outreach. The "HTTP Request" node could be used for this purpose.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running instance of n8n.
  • Supabase Account: With a database containing your prospect information. You'll need credentials to connect.
  • Google Gemini AI (or similar LLM): Access to a Language Model for generating email content. This workflow specifically uses the "Google Gemini Chat Model" node.
  • API Credentials for AI Services: API keys or access tokens for your chosen LLM.
  • Smartlead Account (Implied): If integrating with Smartlead, you'll need an account and its API credentials.
  • Basic JavaScript Knowledge: For configuring the "Code" node if custom logic is required.

Setup/Usage

  1. Import the Workflow: Download the workflow JSON and import it into your n8n instance.
  2. Configure Credentials:
    • Supabase: Set up your Supabase credentials in n8n, providing your Supabase URL and API key.
    • Google Gemini Chat Model: Configure the credentials for your Google Gemini AI.
    • HTTP Request (if sending to Smartlead): If the HTTP Request node is used to send data to Smartlead, configure it with the Smartlead API endpoint and your API key or authentication method.
  3. Customize Nodes:
    • Schedule Trigger: Adjust the schedule to your desired frequency for running the workflow.
    • Supabase Node: Configure the Supabase node to query the correct table and columns for your prospect data.
    • Basic LLM Chain & Information Extractor: Customize the prompts and configurations for the AI nodes to generate the desired email content and extract relevant information.
    • If Node: Define the conditions for the "If" node based on your specific requirements for filtering or routing.
    • HTTP Request Node: If sending to Smartlead, configure the HTTP Request node with the correct payload structure and headers required by the Smartlead API to create or send campaigns.
  4. Activate the Workflow: Once configured, activate the workflow to start generating personalized cold emails on schedule.

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