HTTP Request and SendGrid integration

📌 Overview This n8n-powered workflow automates the entire lifecycle of lead generation and email workflows/campaign. It combines six specialized workflows into one seamless system that scrapes fresh leads, sends personalized emails, tracks engagements, detects replies, classifies responses, handles follow-ups, and keeps a live CRM updated — all in one loop. Designed for B2B cold outreach and follow-up nurturing, this system integrates with Apify, Google Sheets, SendGrid, Gmail, and OpenAI for AI summarization and real-time alerts. 🧠 What It Does This workflow automates the entire lifecycle of B2B cold campaign. It: Scrapes targeted leads directly from Google Maps (via Apify). Extracts verified emails from business websites with anti-blocking safeguards. Stores everything in a centralized Google Sheets CRM. Sends personalized emails via SendGrid, with unique embedded IDs for tracking. Tracks delivery, opens, clicks, and bounces in real time through webhook events. Detects replies from Gmail, matches them to the right campaign stage, and updates the CRM. Uses AI classification to label replies (Interested, Not Interested, Miscellaneous). Routes qualified replies directly to your sales team or Slack/Telegram channel. Automates follow-up emails (5-day & 10-day intervals) for non-responders. Provides light analytics & reporting in Google Sheets for quick insights (with deeper logs available in SendGrid). 💡 Why This Workflow All-in-One Solution**: Instead of juggling multiple tools, this workflow handles lead gen, outreach, tracking, and CRM updates in one place. Smart Reply Handling**: Never lose a lead — every reply is tracked, classified, and routed intelligently. Scalable & Modular**: Each workflow (lead gen, email sending, webhook, replies, routing, follow-ups) can run independently or as part of the full system. Time-Saving: Reduces manual lead collection, email follow-up, and CRM updating by **90%+. Client-Ready**: Built with reliability in mind — randomized delays, duplicate prevention, priority logic for status updates, and AI-powered classification. 👤 Who It’s For This workflow is ideal for: Agencies** running cold campaigns for clients. B2B Businesses** looking to automate lead generation and follow-ups. Freelancers / Consultants** who need a plug-and-play outreach system without expensive SaaS subscriptions. Sales Teams** that want structured, real-time leads routed directly to their inbox or Slack. Startups** who want a scalable, low-cost alternative to tools like Apollo, Firecrawl, Bright Data or Reply.io. ⚙️ How It Works 🧩 1. Lead Generation Workflow 🎯 Purpose Scrape fresh B2B leads from Google Maps, crawl their websites to extract verified email addresses, and upload structured, clean lead data into a Google Sheets CRM. 🛠 How It Works User Input via Form Trigger The workflow begins with a form asking for: Business keyword (e.g. "Dentist") Location (e.g. "Florida") Lead limit (e.g. 50) Scrape Google Maps via Apify Calls the Apify Google Maps Scraper Actor Extracts structured business data like: Business Name, Website, Phone, Category, Rating, Address. Website Filtering & Normalization Filters out businesses with no website Cleans up URLs Website Email Extraction Sends direct HTTP GET requests to the homepage of each business Parses the raw HTML for public-facing email addresses using regex Implements anti-blocking techniques: Random delays between requests Custom headers / User-Agent spoofing Graceful skip on failures Final Filtering & Data Structuring Keeps only businesses with a valid email address Constructs lead objects with: Business Name, Category, Email, Website, Phone, Rating, Location. Upload to Google Sheets CRM Pushes leads to a connected Google Sheet that acts as the system’s central CRM This CRM becomes the source for the email sending workflow 🧩 2. Send an Email Workflow 🎯 Purpose Automatically sends personalized emails to verified leads using rotating templates, embedded ID tracking, and campaign-stage tagging. 🛠 How It Works Pull Active Leads from CRM Retrieves fresh leads from the Google Sheet where Select a Random Template Pulls from a template library stored in a separate Google Sheet Injects lead-specific variables into placeholders like: [Business Name], [Category], [Location], etc. Embed Unique Tracking ID Appends an embedded ID token to the email. This enables accurate reply source tracking across all email stages Send Email via SendGrid Sends the message using SendGrid's transactional API Emails are tagged internally according to email type. 🧩 3. Webhook Event Workflow 🎯 Purpose Processes SendGrid webhook events (e.g., delivered, opened, clicked, bounced) and updates the CRM with prioritized delivery status and engagement tracking — using clean classification and smart update logic. 🛠 How It Works Receive Events via Webhook Trigger Listens for real-time webhook events from SendGrid, including: delivered, bounce, deferred, processed, open, click, unsubscribe, spamreport, etc. Classify Each Event Type A custom code node adds a route label: status: delivery-level events engagement: recipient interaction events others: uncategorized or unsupported Switch-Based Routing Status Events**: Applies priority logic If multiple status events are received for the same lead, only the highest-priority event is stored Updates corresponding CRM fields: Engagement Events**: Detects interactions like: Opened, Clicked, Unsubscribed, Spam Reported Updates CRM fields: Opened, Clicked, Unsubscribed, Spam Reported, Engaged At Preserve first-time interaction records and avoiding regressions Others Branch**: Logs or gracefully skips events not explicitly supported CRM Synchronization Merges event data with the correct lead by matching Email Ensures all updates are timestamped and consistent across systems 🧩 4. Reply Update Database Workflow 🎯 Purpose Polls Gmail inbox, extracts replies, determines their source, and logs them in both the CRM and a message tracker sheet. 🛠 How It Works Poll Gmail for New Replies Uses Gmail API to fetch recent messages Filters out auto-replies, no-reply addresses, or irrelevant responses Prevent Duplicate Processing Checks each message against a "Processed Message IDs" Google Sheet Skips if the message has been handled before Extract Reply Metadata Match to Lead & Update CRM Determines the original email stage based on ID Updates necessary fields 🧩 5. Email Routing Workflow 🎯 Purpose Uses AI to classify replies by intent (Interested, Not Interested, or Miscellaneous) and automatically routes, labels, and logs them accordingly. 🛠 How It Works Receive Cleaned Reply Triggered after a set time interval Classify Using AI (LangChain / OpenAI) The reply is analyzed and categorized as: Interested: wants to talk, asks for more info Not Interested: says no or unsubscribes Miscellaneous: unclear or unrelated response Gmail Label Assignment Adds Gmail label based on classification Handle “Interested” Replies If Interested: Adds label in Gmail Forwards message to a sales or response channel Updates Google Sheet CRM 🧩 6. Follow-Up Email Workflow 🎯 Purpose Automatically sends up to two follow-up emails to leads who showed interest (opened or clicked) but haven’t replied yet. 🛠 How It Works Scheduled Execution Runs daily or at set intervals Filter Leads for Follow-Up Checks that desired conditions are met: Required number of days have passed: 5 days → Follow-Up 1 10 days → Follow-Up 2 Choose and Personalize Template Injects lead-specific data Embeds corresponding for reply tracking Send via SendGrid Message is tagged by stage Sent using the same logic as the original email Update CRM Increments: Follow-Up Sent flag Follow-Up Count Follow-Up Time field ✅ Setup Requirements (Before You Start) Prepare these items to avoid interruptions during setup: 🌍 Domain DNS Access** You’ll need to add TXT/CNAME records in your registrar (GoDaddy, Namecheap, Cloudflare, etc.) to authenticate your domain with SendGrid. 📧 Domain Email Address or Single Sender Authentication (e.g., [email protected])** Needed for SendGrid domain authentication (don’t use Gmail/Yahoo). This step ensures emails are not flagged as spam. Tip: If you don’t own a domain, you can use a single sender email to test, but for production you MUST authenticate a domain. 🔑 API Keys / Credentials** Apify API Key → for Google Maps scraping. SendGrid API Key → for sending emails + webhook events. Google Sheets OAuth Credentials → for CRM integration. Gmail API Credentials → for reply detection. OpenAI API Key → for AI-based reply classification. 📊 Google Sheet (CRM)** Add desired columns: Business Name, Email, Website, Phone, Category, Status, Reply, Follow-Up Count. 🌐 n8n Environment (Cloud or Self-Hosted)** Must allow Apify node installation. 🛠 How to Set It Up Open n8n (Cloud or Self-Hosted). Install Apify node before importing. Search Apify → click Install. Import the provided .json workflow file into your n8n editor. Set up the required credentials: 🔑 Apify API Key, 🔑 SendGrid API Key, 🔑 Google Sheets OAuth, 🔑 Gmail API, 🔑 OpenAI API Key. Prepare your Google Sheet (CRM). Verify column names match your workflow fields. Adjust “Get Desired Fields” node in n8n “Lead generation workflow” if you add/remove columns. Enable SendGrid Webhook Events. Go to SendGrid → Settings → Mail Settings → Event Webhook. Paste the webhook URL from your n8n “Webhook Event Workflow”. Select: Delivered, Opened, Clicked, Bounced, Unsubscribed, Spam Report. Run a test. Trigger the Lead Generation workflow → check Google Sheets for leads. Send a test email → verify delivery + engagement updates in CRM. Reply from a test inbox → confirm Gmail polling + AI classification. 📂 Additional Provided Resources. To help you get started faster, you’ll also receive: SendGrid Setup and Troubleshooting document. Two ready-to-use Google Sheets example templates** which can be modified to suit your business needs: Email Workflow DB CRM Includes: Leads Tab → structured space for scraped businesses and contact details. Email Templates Tab → pre-written templates for the main email, 1st follow-up, and 2nd follow-up (with placeholders for personalization). Analytics Tab → light reporting on sends, opens, clicks, and replies to give quick campaign insights. Processed Gmails IDs A simpler sheet designed for Gmail reply handling. Useful for tracking processed messages and avoiding duplicates while you familiarize yourself with how reply updates work. 🎨 Customization Tips Templates**: Update the Google Sheets Templates tab with your own outreach copy. Use placeholders like [Business Name], [Location], [Category] so each email feels personalized. CRM Fields: Add or remove CRM columns depending on your business needs (e.g., Industry, Revenue, Sales Owner, Notes). Just make sure the field names match in n8n’s **“Grab Desired Fields” nodes in the Lead generation workflow. Follow-Up Logic: Adjust the timing for follow-ups. Default is **5 days (Follow-Up 1) and 10 days (Follow-Up 2), but you can easily change this to 3/7/14 days or any schedule your sales process requires. Reply Routing**: Customize how AI classification works. For example, rename labels (“Hot Lead”, “Not Interested”, “Out of Scope”) and route replies differently (e.g., forward “Interested” to your sales inbox, Slack channel, or Telegram bot). Analytics & Reporting**: Expand the Google Sheets reporting tab. You can add pivot tables for deeper campaign insights. For more advanced analytics, SendGrid also keeps full logs.* Scalability**: Add proxy handling for higher-volume scraping. Switch to a database (Postgres, Supabase, MongoDB) instead of Google Sheets if managing thousands of leads. Use multiple SendGrid accounts or IP warm-up strategies for large-scale sending. Scraping Alternatives**: If you prefer not to use direct HTTP requests for email extraction, you can integrate with external scrapers like: Firecrawl – lightweight scraper for web/email extraction. Bright Data – residential proxies + scraping tools. Apify Website Scrapers – customizable actors for deep site scraping. These can plug into the workflow instead of (or alongside) the built-in email scraper. ✨ Predefined Templates vs. AI-Generated Emails By default, this workflow uses predefined templates stored in Google Sheets. This design choice was intentional, and here’s why: ✅ Reliability: Alway work, no prompt issues. ✅ Cost Savings: no API token usage. ✅ Total Control, Consistent & Customizable: You control tone and can tweak anytime. ⚡ That said, you can absolutely swap out the template system for AI-based generation if you prefer dynamic messaging. The workflow is flexible — just keep in mind the trade-offs in cost, reliability, and control. ⚡ Best approach: start with templates for stability, then add AI if you want more variety.

Automated SSL/TLS Certificate Expiry Report for AWS > Automatically generates a weekly report of all AWS ACM certificates, including status, expiry dates, and renewal eligibility. The workflow formats the data into both Markdown (for PDF export to Slack) and HTML (for email summary), helping teams stay on top of certificate compliance and expiration risks. Who’s it for This workflow is designed for DevOps engineers, cloud administrators, and compliance teams who manage AWS infrastructure and need automated weekly visibility into the status of their SSL/TLS certificates in AWS Certificate Manager (ACM). It's ideal for teams that want to reduce the risk of expired certs, track renewal eligibility, and maintain reporting for audit or operational purposes. How it works / What it does This n8n workflow performs the following actions on a weekly schedule: Trigger: Automatically runs once a week using the Weekly schedule trigger. Fetch Certificates: Uses Get many certificates action from AWS Certificate Manager to retrieve all certificate records. Parse Data: Processes and reformats certificate data (dates, booleans, SANs, etc.) into a clean JSON object. Generate Reports: 📄 Markdown Report: Uses the Certificate Summary Markdown Agent (OpenAI) to generate a Markdown report for PDF export. 🌐 HTML Report: Uses the Certificate Summary HTML Agent to generate a styled HTML report for email. Deliver Reports: Converts Markdown to PDF and sends it to Slack as a file. Sends HTML content as a formatted email. How to set up Configure AWS Credentials in n8n to allow access to AWS ACM. Create a new workflow and use the following nodes in sequence: Schedule Trigger: Weekly (e.g., every Monday at 08:00 UTC) AWS ACM → Get many certificates Function Node → Parse ACM Data: Converts and summarizes certificate metadata OpenAI Chat Node (Markdown Agent) with a system/user prompt to generate Markdown Configure Metadata → Define file name and MIME type (.md) Create document file → Converts Markdown to document stream Convert to PDF Slack Node → Upload the PDF to a channel (Optional) Add a second OpenAI Chat Node for generating HTML and sending it via email Connect Output: Markdown report → Slack file upload HTML report → Email node with embedded HTML Requirements 🟩 n8n instance (self-hosted or cloud) 🟦 AWS account with access to ACM 🟨 OpenAI API key (for ChatGPT Agent) 🟥 Slack webhook or OAuth credentials (for file upload) 📧 Email integration (e.g., SMTP or SendGrid) 📝 Permissions to write documents (Google Drive / file node) How to customize the workflow Change report frequency**: Adjust the Weekly schedule trigger to daily or monthly as needed. Filter certificates**: Modify the function node to only include EXPIRED, IN_USE, or INELIGIBLE certs. Add tags or domains to include/exclude. Add visuals**: Enhance the HTML version with colored rows, icons, or company branding. Change delivery channels**: Replace Slack with Microsoft Teams, Discord, or Telegram. Send Markdown as email attachment instead of PDF. Integrate ticketing**: Create a JIRA/GitHub issue for each certificate that is EXPIRED or INELIGIBLE.

Multi-agent RAG system for smarter BRD (Business Requirement Document) writing Who’s it for This workflow is designed for Business Analysts, Project Managers, and Operations Teams who need to automate the creation, tracking, and delivery of Business Requirements Documents (BRDs) from submitted forms and supporting materials. It’s ideal for organizations handling multiple BRD requests and looking to streamline document generation, archiving, and communication. How it works / What it does Trigger: The process begins when a BRD request form is submitted along with any supporting files. Sample supporting document PDF: Download URL Data Recording: Creates a BRD request record and appends it to a tracking Google Sheet. Handles multiple uploaded files, saving them to Google Drive. Creates supporting document records and updates the supporting documents tracking sheet. Content Extraction & Storage: Extracts text from uploaded PDF files. Inserts extracted content into a vector store for contextual retrieval by AI agents. Document Generation: Uses two specialized AI agents: General BRD Writer Agent for the overall document structure. Business Requirement Writer Agent for detailed business requirement sections. Both agents query the stored data and produce content, which is then merged. Metadata & File Creation: Configures metadata for the document. Creates a final document file (Google Docs). Finalization: Converts the document to PDF Sample output Archives the PDF in Google Drive. Sends a BRD response email to the requester with the completed document. Updates the request status in the Google Sheet as completed. How to set up Prepare Google Sheets: Create a BRD tracking sheet. Create a supporting document tracking sheet. Configure Google Drive: Set up folders for supporting documents and archived PDFs. Ensure the workflow has API access to upload and retrieve files. Form Integration: Connect your BRD request form to trigger the workflow. Vector Store: Configure a vector database or embedding store for extracted document text. AI Agents: Configure the General BRD Writer Agent and Business Requirement Writer Agent with your preferred OpenAI model. Link both agents to the Query Data Tool for retrieving embedded content. Email Setup: Configure email sending credentials to deliver final BRDs to requesters. Requirements Google Sheets API credentials. Google Drive API credentials. An OpenAI API key with access to the desired models. A form submission trigger (e.g., Google Forms, Typeform). Vector store or embedding database for contextual AI queries. Permissions for file uploads, downloads, and updates in Google Drive. How to customize the workflow Custom Templates**: Modify the AI agents’ system prompts to match your organization’s BRD format and tone. Metadata Fields**: Add custom fields (e.g., department, priority level) during metadata configuration. File Storage Paths**: Adjust Google Drive folder structure for project-specific storage. Approval Steps**: Insert an approval workflow between draft document creation and final archiving. Notification Channels**: Add Slack, Microsoft Teams, or other notification integrations in addition to email. AI Model Selection**: Swap the OpenAI model for another LLM or fine-tuned variant to improve BRD quality for your domain.

This workflow uses a number of technologies to track the value of ETFs, stocks and other exchange-traded products: Baserow: To keep track of our investments n8n’s Cron node: To trigger the workflow compiling our daily morning briefing Webscraping: The HTTP Request & HTML Extract nodes to fetch up-to-date prices from the relevant stock exchange and structure this infromation Javascript: We’ll use the Function node to build a custom HTML body with all the relevant information Sendgrid: The Email Service Provider in this workflow to send out our email Thanks to n8n, the steps in this workflow can easily be changed. Not a Sendgrid user? Simply remove the Sendgrid node and add a Gmail node instead. The stock exchange has a REST API? Just throw away the HTML Extract node. Here’s how it works: Data Source In this scenario, our data source is Baserow. In our table, we’ll track all information needed to identify each investment product: We have two text type columns (Name and ISIN) as well as two number type columns (Count and Purchase Price). Workflow Nodes Cron The Cron node will trigger our workflow to run each work day in the morning hours. Baserow The Baserow node will fetch our investments from the database table shown above. HTTP Request Using the HTTP Request node we can fetch live data from the stock exchange of our choice based on the ISIN. This example uses Tradegate, which is used by many German fintechs. The basic approach should also work for other exchanges, as long as they provide the required data to the public. HTML Extract Since our HTTP Request node fetches full websites, we’re using the HTML Extract node to extract the information we’re looking for from each website. If an exchange other than Tradegate is used, the selectors used in this node will most likely need to be updated. + 6. Set The Set nodes helps with setting the exact columns we’ll use in our table. In this case we’re first formatting the results from our exchange, then calculate the changes based on the purchase price. Function Here were using a bit of Javascript magic to build an HTML email. This is where any changes to the email content would have to be made. Sendgrid Finally we send out the email built in the previous step. This is where you can configure sender and recipients. Result The basic email generated by this workflow will look like so: