HumationHuman + Automation
Back to Catalog

Scrape public email addresses from any website using Firecrawl

Lucas WalterLucas Walter
3462 views
2/3/2026
ExportWebhookData TransformationLoopCSV
Official Page

Who's it for

This template is perfect for sales professionals, marketers, and business developers who need to quickly gather contact information from company websites. Whether you're building prospect lists, researching potential partners, or collecting leads for outreach campaigns, this automation saves hours of manual email hunting.

What it does

This workflow automatically discovers and extracts email addresses from any website by:

  • Taking a website URL as input through a simple form
  • Using Firecrawl's mapping API to find relevant pages (about, contact, team pages)
  • Batch scraping those pages to extract email addresses
  • Intelligently handling common email obfuscations like "(at)" and "(dot)"
  • Returning a clean, deduplicated list of valid email addresses

The automation handles rate limiting, retries failed requests, and filters out invalid or hidden email addresses to ensure you get quality results.

How to set up

  1. Get Firecrawl API access: Sign up at firecrawl.dev and obtain your API key
  2. Configure credentials: In n8n, create a new HTTP Header Auth credential named "Firecrawl" with:
    • Header Name: Authorization
    • Header Value: Bearer YOUR_API_KEY
  3. Import the workflow: Copy the workflow JSON into your n8n instance
  4. Test the form: Activate the workflow and test with a sample website URL

How to customize the workflow

Search parameters: Modify the search parameter in the map_website node to target different page types (currently searches for "about contact company authors team")

Extraction limits: Adjust the limit parameter to scrape more or fewer pages per website

Retry logic: The workflow includes retry logic with a 12-attempt limit - modify the check_retry_count node to change this

Output format: The set_result node formats the final output - customize this to match your preferred data structure

Email validation: The JSON schema in start_batch_scrape defines how emails are extracted - modify the prompt or schema for different extraction rules

The workflow is designed to be reliable and handle common edge cases like rate limiting and failed requests, making it production-ready for regular use.

Scrape Public Email Addresses from Any Website using Firecrawl

This n8n workflow provides a robust solution for extracting publicly available email addresses from a specified website. It leverages the Firecrawl API for web scraping and includes logic to handle potential errors and ensure a clean output of email addresses.

What it does

This workflow automates the following steps:

  1. Receives Website URL: It starts by accepting a website URL via an n8n form submission.
  2. Scrapes Website Content: It makes an HTTP request to the Firecrawl API to scrape the content of the provided website URL.
  3. Checks for Firecrawl API Errors: It verifies if the Firecrawl API call was successful.
  4. Extracts Email Addresses: If the scraping is successful, it uses a regular expression to extract all valid email addresses from the scraped content.
  5. Handles Errors: If the Firecrawl API call fails, it stops the workflow and reports an error.
  6. Formats Output: It formats the extracted email addresses into a clean list.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance to import and execute the workflow.
  • Firecrawl API Key: An API key for the Firecrawl service to scrape website content. This will need to be configured as a credential in n8n.

Setup/Usage

  1. Import the Workflow:

    • Download the provided JSON file for this workflow.
    • In your n8n instance, click on "Workflows" in the left sidebar.
    • Click "New" and then "Import from JSON".
    • Paste the workflow JSON or upload the file.

  2. Configure Credentials:

    • Locate the "HTTP Request" node (ID: 19).
    • You will need to configure a credential for the Firecrawl API. This typically involves setting up an "API Key Auth" credential type, where you provide your Firecrawl API key.
    • Ensure the HTTP Request node is configured to use this credential for authentication with the Firecrawl API.

  3. Activate the Workflow:

    • Once imported and configured, activate the workflow by toggling the "Active" switch in the top right corner of the workflow editor.

  4. Trigger the Workflow:

    • The workflow is triggered by an n8n Form Trigger. You can access the form by clicking on the "On form submission" node (ID: 1225) and then clicking the "Open Form" button in the node's settings panel.
    • Enter the website URL you wish to scrape for email addresses into the form and submit it.

  5. View Results:

    • After submission, the workflow will execute. You can view the extracted email addresses in the output of the "Edit Fields" node (ID: 38) if the scraping was successful.
    • If there was an error with the Firecrawl API, the "Stop and Error" node (ID: 528) will be triggered, and you will see the error message in the workflow execution logs.

Related Templates

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 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

Wessel BulteBy Wessel Bulte
247

AI-powered code review with linting, red-marked corrections in Google Sheets & Slack

Advanced Code Review Automation (AI + Lint + Slack) Who’s it for For software engineers, QA teams, and tech leads who want to automate intelligent code reviews with both AI-driven suggestions and rule-based linting — all managed in Google Sheets with instant Slack summaries. How it works This workflow performs a two-layer review system: Lint Check: Runs a lightweight static analysis to find common issues (e.g., use of var, console.log, unbalanced braces). AI Review: Sends valid code to Gemini AI, which provides human-like review feedback with severity classification (Critical, Major, Minor) and visual highlights (red/orange tags). Formatter: Combines lint and AI results, calculating an overall score (0–10). Aggregator: Summarizes results for quick comparison. Google Sheets Writer: Appends results to your review log. Slack Notification: Posts a concise summary (e.g., number of issues and average score) to your team’s channel. How to set up Connect Google Sheets and Slack credentials in n8n. Replace placeholders (<YOURSPREADSHEETID>, <YOURSHEETGIDORNAME>, <YOURSLACKCHANNEL_ID>). Adjust the AI review prompt or lint rules as needed. Activate the workflow — reviews will start automatically whenever new code is added to the sheet. Requirements Google Sheets and Slack integrations enabled A configured AI node (Gemini, OpenAI, or compatible) Proper permissions to write to your target Google Sheet How to customize Add more linting rules (naming conventions, spacing, forbidden APIs) Extend the AI prompt for project-specific guidelines Customize the Slack message formatting Export analytics to a dashboard (e.g., Notion or Data Studio) Why it’s valuable This workflow brings realistic, team-oriented AI-assisted code review to n8n — combining the speed of automated linting with the nuance of human-style feedback. It saves time, improves code quality, and keeps your team’s review history transparent and centralized.

higashiyama By higashiyama
90