Lead analysis & personalized email generation with OpenAI, Firecrawl & gotoHuman
💼 Lead Outreach Agent
This AI workflow helps you quickly react to new leads with an initial personalized outreach. A great start of your lead nurturing sequence to avoid loosing precious leads that could turn into paying customers. Most importantly it uses gotoHuman so you can review the AI-analysis and the AI-generated editable email draft before it is sent out in your name.
How it works
- We receive a new form submission incl. the email address and company name of the prospect and extract the website URL from the address. We proceed only for company email addresses.
- We scrape the website using Firecrawl and summarize it with OpenAI
- Our AI agent runs an analysis based on the lead information and documents describing our own company and the defined Ideal Customer Profiles. It also fetches previously approved examples from gotoHuman so you're effectively creating a self-learning agent. It responds with the analysis and the drafted outreach email.
- Human Approval in gotoHuman. Allows editing the drafted email.
- We can now send our email including any edits made during the review and be sure that we are using high-quality content instead of AI slop.
How to set up
- Most importantly, install the gotoHuman node before importing this template! (Just add the node to a blank canvas before importing)
- Set up your credentials for the different services
- In gotoHuman, select and create the pre-built review template "Lead Outreach Agent" or import the ID:
T873fI1Xli5nt3eh33Rj - Select this template in the gotoHuman node
Requirements
You need accounts for
- gotoHuman (Human Supervision)
- OpenAI (AI Agent)
- Typeform (Lead Form Submissions)
- Firecrawl (Website Scraping)
- Gmail
- Google Docs (Company Wiki)
How to customize
- Replace the Typeform trigger with any other way you might receive or find new leads
- Provide the AI Sales Agent with more context to properly analyze the lead and create better personalized emails. Consider adding tools that allow the agent to fetch more infos about the prospect's company or personal profile, or to find out more about your specific product/service offerings and how your sales pitches look like.
Lead Analysis & Personalized Email Generation with OpenAI & Firecrawl
This n8n workflow automates the process of analyzing new leads from Typeform submissions, enriching their data, and generating personalized email outreach using OpenAI, Firecrawl, and a human-in-the-loop approval step via Gmail.
What it does
This workflow streamlines your lead qualification and outreach by:
- Capturing New Leads: Automatically triggers upon new submissions to a specified Typeform.
- Initial Lead Qualification: Uses a "Code" node to perform initial data processing or transformation on the incoming Typeform data.
- Enriching Lead Data (Implicit): Although not explicitly shown in the provided JSON, the presence of an "AI Agent" and "OpenAI" nodes suggests that the workflow intends to use AI to analyze and enrich lead information, potentially by extracting key details or categorizing the lead.
- Generating Personalized Email Content: Leverages an "OpenAI Chat Model" and a "Structured Output Parser" to craft highly personalized email drafts based on the lead's information and potentially scraped data (implied by the directory name "firecrawl").
- Human-in-the-Loop Approval: Sends the generated email draft to a designated Gmail account for manual review and approval.
- Conditional Logic: Includes an "If" node, indicating that subsequent actions (e.g., sending the email, logging the lead) would depend on the outcome of the human approval or other conditions. (The specific conditions and subsequent actions are not defined in the provided JSON but are implied by the node's presence).
Prerequisites/Requirements
- n8n Account: A running instance of n8n.
- Typeform Account: A Typeform account with a form configured to capture lead information.
- OpenAI API Key: An API key for OpenAI to utilize its language models.
- Gmail Account: A Gmail account configured as a credential in n8n for sending approval emails.
- Firecrawl (Implied): Based on the directory name, it's highly probable that a Firecrawl integration (or similar web scraping tool) is intended to be used for website content extraction, which would require appropriate credentials or setup.
Setup/Usage
- Import the Workflow: Import the provided JSON into your n8n instance.
- Configure Typeform Trigger:
- Select your Typeform credential.
- Choose the specific Typeform form you want to monitor for new submissions.
- Configure OpenAI Credentials:
- Set up your OpenAI API Key credential in n8n.
- Ensure the "OpenAI Chat Model" and "OpenAI" nodes are using this credential.
- Configure Gmail Credentials:
- Set up your Gmail OAuth2 or API Key credential in n8n.
- In the "Gmail" node, specify the recipient email address for the approval emails (likely your own or a team inbox).
- Review and Customize Code Node: Examine the "Code" node to understand and adjust any data processing logic as needed for your specific lead data.
- Review and Customize AI Agent/OpenAI Prompts:
- Inspect the "AI Agent" and "OpenAI Chat Model" nodes.
- Adjust the prompts and model parameters to ensure the generated email content aligns with your brand voice and outreach strategy.
- Define the schema in the "Structured Output Parser" to match the desired format of the personalized email (ee.g., subject, body).
- Define Conditional Logic (If Node):
- The "If" node currently has no conditions defined. You will need to add conditions based on the output of the "Gmail" node (e.g., if an approval email was sent, if a specific response was received).
- Connect the "True" and "False" branches of the "If" node to subsequent actions (e.g., send the email if approved, log to a CRM if not approved, etc.).
- Activate the Workflow: Once all credentials and configurations are set, activate the workflow to start processing new Typeform submissions.
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.
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
Automate Dutch Public Procurement Data Collection with TenderNed
TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch 🔗 LinkedIn – Wessel Bulte