HumationHuman + Automation
Back to Catalog

Create AI personalized video & voice outreach with HeyGen, ElevenLabs & Perplexity

Automate With MarcAutomate With Marc
594 views
2/3/2026
AIStorageOpenAIAutomationSupabase
Official Page

Automated Sales Rep Clone Outreach Video and Voice Note for B2B Outbound

This workflow automatically transforms new leads from Google Sheets into hyper-personalized outreach videos, voice notes, and emails using AI research, scriptwriting, video cloning, and voice generation. Perfect for SDRs, founders, and agencies who want to scale outreach without sacrificing personalization.

🎥 Watch step by step build: https://www.youtube.com/watch?v=q9AAh9zRou4

What this template does

Whenever a new row is added to your Google Sheets CRM, this workflow:

Reads the new lead (Name, Email, Phone, Company, Industry, LinkedIn URL)

Runs deep research on the person & company using Perplexity

Generates a personalized 30-second outreach script

Creates a cloned-face, AI-generated HeyGen video with the script

Creates an ElevenLabs voice note using the same personalized insights

Uploads the audio file to Google Drive

Sends an email to yourself containing:

Outreach subject line

Email body

Personalized video link

Personalized voice note link

(Optional) Sends a WhatsApp/SMS/MMS message via Twilio with the files or links

This template builds a complete AI-powered outbound engine—research, video, voice note, and email—fully automated.

Why this is useful

Turns manual outbound into a hands-free, 360° AI workflow

Personalized video outreach dramatically increases reply rates

Consistent research quality for every lead

SDRs save hours per day on manual prep

Perfect for:

Influencer agencies

SaaS outbound teams

Founders doing cold outreach

Recruitment agencies

Real estate & service businesses

Requirements

Before running this workflow, connect:

Google Sheets OAuth (trigger + CRM sheet)

Perplexity API Key

OpenAI API Key (GPT-5.1, GPT-4.1-mini)

OpenRouter API Key

HeyGen API Key (for video avatar)

ElevenLabs API Key (for voice note)

Google Drive OAuth (for file upload)

Twilio credentials (optional SMS/WhatsApp)

⚠️ All credentials must be added manually after importing. This ensures security and complies with n8n Template Guidelines.

How it works (Node Breakdown)

  1. Google Sheets Trigger

Watches your CRM sheet and fires whenever a new lead row is added.

  1. Code Node — Extract Latest Row

Ensures only the newly added row continues through the workflow.

  1. Research Agent

Powered by OpenAI + Perplexity

Scrapes professional history, company insights, marketing gaps

Identifies outreach opportunities & triggers

Produces a structured research summary

  1. Scripting Agent

Writes a natural, human-sounding 30-second outreach script tailored to that exact lead.

  1. HeyGen Video Generator

Creates a personalized avatar video narrating the script (720×1280).

  1. ElevenLabs Voice Generation

Generates a custom voice note version of the pitch.

  1. Google Drive Upload

Saves the voice note file for sharing or sending via WhatsApp.

  1. Twilio Message (optional)

Sends the voice note or video link via SMS/WhatsApp.

  1. Email Output

Creates a fully structured JSON email including:

Subject line

Personalized body

HeyGen video link

Voice note link

Delivered via Gmail node.

Setup (Step-by-Step)

Import the template into n8n

Open Google Sheets Trigger → choose your CRM sheet

Add all required credentials:

Perplexity

OpenAI

OpenRouter

HeyGen

ElevenLabs

Google Drive

Gmail

Twilio (optional)

In HeyGen node, choose:

Your avatar

Your preferred voice ID

In ElevenLabs node, set:

Your preferred voice model

Review the system prompts of:

Research Agent

Script Agent

Email Agent Adjust for your brand tone if needed.

Run once manually to test.

Turn on the workflow—your AI outbound engine is live.

Customization Ideas

Swap HeyGen avatar to match your brand identity

Add a Slack notification when each video is ready

Save research & scripts into a Notion database

Create a HubSpot contact for each lead

Add duplicate detection logic

Auto-post video to social channels for public outreach

Troubleshooting

Video stuck in “processing”? → Increase the Wait node duration (30–60 sec).

Voice note too robotic? → Switch to a premium ElevenLabs voice.

Research not specific enough? → Strengthen the system prompt with more constraints.

Emails not arriving? → Ensure Gmail OAuth has send permission configured.

API authentication errors? → Check credentials in each node (OpenAI, Perplexity, HeyGen, etc.).

n8n Workflow: AI-Powered Personalized Video & Voice Outreach with HeyGen, ElevenLabs, and Perplexity

This n8n workflow demonstrates a powerful automation for creating highly personalized video and voice outreach campaigns. It leverages AI agents to generate tailored content and integrates with various services to deliver a comprehensive outreach solution.

What it does

This workflow orchestrates a series of steps to generate and potentially deliver personalized outreach:

  1. Trigger: The workflow is manually triggered or can be configured to listen for new data in a Google Sheet. This sheet would contain the recipient information and initial prompts.
  2. Code Execution: A "Code" node is used to define and structure the input for the AI agent, likely extracting relevant data from the trigger.
  3. AI Agent (Perplexity/OpenAI): An "AI Agent" node, configured with either an OpenAI Chat Model or an OpenRouter Chat Model (potentially leveraging Perplexity through OpenRouter), processes the input. This agent is responsible for generating personalized content, such as video scripts or voiceover text, based on the provided data.
  4. Structured Output Parsing: A "Structured Output Parser" node ensures that the AI agent's output is correctly formatted (e.g., as JSON) for subsequent steps.
  5. HTTP Request (HeyGen/ElevenLabs): An "HTTP Request" node is used to interact with external APIs. Based on the directory name, this is likely where calls to HeyGen (for video generation) and ElevenLabs (for voice synthesis) would be made, using the AI-generated content.
  6. Google Drive Integration: A "Google Drive" node is included, suggesting that generated videos, voiceovers, or other related assets might be stored in Google Drive.
  7. Communication (Twilio/Gmail): "Twilio" and "Gmail" nodes are present, indicating potential steps for sending personalized SMS messages or emails, perhaps containing links to the generated videos or voice messages.
  8. Wait: A "Wait" node is included, which could be used to introduce delays between actions, for example, to space out outreach efforts or wait for API processing.
  9. Sticky Note: A "Sticky Note" is present, likely for documentation or internal notes within the workflow.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance.
  • Google Sheets Account: For the trigger and potentially for storing data.
  • OpenAI API Key or OpenRouter API Key: For the AI Agent to access language models. If using OpenRouter, you might configure it to use Perplexity or other models.
  • HeyGen Account and API Key: (Inferred from directory name) For generating personalized videos.
  • ElevenLabs Account and API Key: (Inferred from directory name) For generating personalized voiceovers.
  • Twilio Account and Credentials: If you plan to send SMS messages.
  • Gmail Account and Credentials: If you plan to send emails.
  • Google Drive Account and Credentials: If you plan to store files in Google Drive.

Setup/Usage

  1. Import the Workflow: Download the provided JSON and import it into your n8n instance.
  2. Configure Credentials:
    • Set up your Google Sheets, OpenAI/OpenRouter, Twilio, Gmail, and Google Drive credentials within n8n.
    • For HeyGen and ElevenLabs, configure the "HTTP Request" node with your respective API keys and endpoints.
  3. Google Sheets Trigger Configuration:
    • Specify the Google Sheet and worksheet that will trigger the workflow (e.g., on new row added).
    • Ensure your Google Sheet has columns for recipient names, personalization details, and any other data required by the AI agent.
  4. Code Node Customization: Review and customize the "Code" node to correctly extract and format data from your Google Sheet for the AI agent.
  5. AI Agent Configuration:
    • Select your preferred chat model (OpenAI or OpenRouter).
    • Define the prompt for the "AI Agent" to guide it in generating personalized content (e.g., "Generate a personalized video script for {{ $json.recipientName }} about {{ $json.productFeature }}").
  6. Structured Output Parser: Ensure the schema in this node matches the expected output format from your AI agent.
  7. HTTP Request Node Customization:
    • Configure the HTTP Request nodes for HeyGen and ElevenLabs with the appropriate API endpoints, request bodies (using the AI-generated content), and headers (including your API keys).
    • Adjust the parameters for video and voice generation (e.g., voice ID, video template ID).
  8. Google Drive Configuration: If storing files, configure the "Google Drive" node to upload the generated videos/voiceovers to a specific folder.
  9. Communication Nodes:
    • Configure the "Twilio" node to send SMS messages with links to the generated content.
    • Configure the "Gmail" node to send personalized emails.
  10. Activate the Workflow: Once all configurations are complete, activate the workflow. It will now automatically trigger based on your Google Sheets data and initiate the personalized outreach process.

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