HumationHuman + Automation
Back to Catalog

Automated job scraping with SerpAPI, Gemini AI filter & email notifications

LouisLouis
65 views
2/3/2026
HTTPREST APIWebhookExampleHello World
Official Page

🛜 Daily Notification on Specific Latest Job Offers 🛜

🌟 Overview: Never miss a job offer again! This n8n workflow automates daily job scraping from LinkedIn, Indeed, Welcome to the Jungle, and more, using Google Dorks and SerpAPI. It filters offers with a Gemini AI agent, stores them in Google Sheets, and sends a sleek HTML newsletter to your inbox or subscribers—all manageable from your phone!

💼 Use Cases:

  • Students hunting for M&A, valuation, or transaction services internships (6+ months).
  • Career switchers seeking automated, curated job alerts.
  • Content creators building a job newsletter to monetize their audience.

⚙️ How It Works:

  1. Scrape: Uses SerpAPI with a tailored Google Dork to fetch fresh job listings daily from top platforms.
  2. Filter: A Gemini AI agent validates offers to ensure they match corporate finance criteria.
  3. Store: Saves new offers in Google Sheets, marking duplicates to avoid spam.
  4. Notify: Generates an email/newsletter notification and sends it via Outlook

🛠️ Setup Instructions:

  • Import the JSON workflow into n8n.
  • Add credentials: SerpAPI (API key), Google Sheets (OAuth2), Microsoft Outlook (OAuth2)
  • Customize the Google Dork in the "Edit Fields" node for specific job criteria.
  • Schedule to run daily at 7 AM. Test and tweak the AI prompt for precision.

🔑 Required Credentials & Nodes:

  • Credentials: SerpAPI, Google Sheets OAuth2, Microsoft Outlook OAuth2
  • Nodes: Schedule Trigger, HTTP Request, Google Sheets, AI Agent (Gemini), Microsoft Outlook

🔗 Creator: Louis Delahaye | n8n.io/creators/louisdl

🎥 YouTube @cash-routine

My AI Agency : https://agence-alain.fr

Automated Job Scraping with SerpApi, Gemini AI Filtering, and Email Notifications

This n8n workflow automates the process of finding new job postings, filtering them using Google Gemini AI, and sending email notifications for relevant opportunities.

What it does

This workflow streamlines your job search by:

  1. Triggering on Schedule: Initiates the job search process at predefined intervals (e.g., daily, weekly).
  2. Fetching Job Search Queries: Reads job search parameters (keywords, location, etc.) from a Google Sheet.
  3. Executing Sub-workflows for Each Query: For each job query from the Google Sheet, it calls a sub-workflow to perform the actual job scraping.
  4. Scraping Job Postings: The sub-workflow uses an HTTP Request node to query SerpApi for job listings based on the provided search parameters.
  5. Comparing with Previously Found Jobs: New job postings are compared against a list of previously identified jobs (likely stored in another Google Sheet) to avoid duplicate notifications.
  6. Filtering with Google Gemini AI: For newly found jobs, it uses the Google Gemini Chat Model via an AI Agent to evaluate if the job description matches specific criteria or is of interest.
  7. Aggregating Relevant Jobs: Collects all jobs that pass the AI filtering.
  8. Sending Email Notifications: Sends an email via Microsoft Outlook containing the details of the newly found and AI-filtered job postings.
  9. Updating Google Sheet: Adds the newly found jobs to the Google Sheet of previously found jobs to maintain a record and prevent future duplicate processing.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running instance of n8n.
  • Google Sheets Account: To store job search queries and a record of previously found jobs. You'll need to configure Google Sheets credentials in n8n.
  • SerpApi Account and API Key: To scrape job listings. You'll need to provide your SerpApi API key for the HTTP Request node.
  • Google Gemini AI Access: For the Google Gemini Chat Model. This typically involves a Google Cloud Project and API key.
  • Microsoft Outlook Account: To send email notifications. You'll need to configure Microsoft Outlook credentials in n8n.

Setup/Usage

  1. Import the Workflow: Import the provided JSON into your n8n instance.
  2. Configure Credentials:
    • Set up your Google Sheets credentials.
    • Set up your Microsoft Outlook credentials.
    • Configure the HTTP Request node with your SerpApi API Key.
    • Configure the Google Gemini Chat Model node with your Google Gemini AI credentials.
  3. Prepare Google Sheets:
    • Create a Google Sheet for your job search queries. This sheet should contain columns for your search terms (e.g., "keywords", "location").
    • Create another Google Sheet to store the jobs that have already been processed and notified. This sheet will be used by the "Compare Datasets" node.
  4. Customize Nodes:
    • Schedule Trigger (839): Adjust the schedule to your preferred frequency for running the job search (e.g., every day, once a week).
    • Google Sheets (18): Configure this node to read from your job search queries Google Sheet.
    • Execute Workflow (111): Ensure the sub-workflow ID is correctly set if you separate the job scraping logic into a distinct workflow.
    • HTTP Request (19): Verify the SerpApi endpoint and parameters are correctly configured for your job search needs.
    • AI Agent (1119) and Google Gemini Chat Model (1262): Customize the prompt for the AI Agent to accurately filter job descriptions based on your specific criteria.
    • Microsoft Outlook (433): Customize the email subject and body to include relevant job details.
    • Google Sheets (18 - for writing): Configure this node to write the new job postings to your "previously found jobs" Google Sheet.
  5. Activate the Workflow: Once configured, activate the workflow to start automating your job search.

Related Templates

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

🎓 How to transform unstructured email data into structured format with AI agent

This workflow automates the process of extracting structured, usable information from unstructured email messages across multiple platforms. It connects directly to Gmail, Outlook, and IMAP accounts, retrieves incoming emails, and sends their content to an AI-powered parsing agent built on OpenAI GPT models. The AI agent analyzes each email, identifies relevant details, and returns a clean JSON structure containing key fields: From – sender’s email address To – recipient’s email address Subject – email subject line Summary – short AI-generated summary of the email body The extracted information is then automatically inserted into an n8n Data Table, creating a structured database of email metadata and summaries ready for indexing, reporting, or integration with other tools. --- Key Benefits ✅ Full Automation: Eliminates manual reading and data entry from incoming emails. ✅ Multi-Source Integration: Handles data from different email providers seamlessly. ✅ AI-Driven Accuracy: Uses advanced language models to interpret complex or unformatted content. ✅ Structured Storage: Creates a standardized, query-ready dataset from previously unstructured text. ✅ Time Efficiency: Processes emails in real time, improving productivity and response speed. *✅ Scalability: Easily extendable to handle additional sources or extract more data fields. --- How it works This workflow automates the transformation of unstructured email data into a structured, queryable format. It operates through a series of connected steps: Email Triggering: The workflow is initiated by one of three different email triggers (Gmail, Microsoft Outlook, or a generic IMAP account), which constantly monitor for new incoming emails. AI-Powered Parsing & Structuring: When a new email is detected, its raw, unstructured content is passed to a central "Parsing Agent." This agent uses a specified OpenAI language model to intelligently analyze the email text. Data Extraction & Standardization: Following a predefined system prompt, the AI agent extracts key information from the email, such as the sender, recipient, subject, and a generated summary. It then forces the output into a strict JSON structure using a "Structured Output Parser" node, ensuring data consistency. Data Storage: Finally, the clean, structured data (the from, to, subject, and summarize fields) is inserted as a new row into a specified n8n Data Table, creating a searchable and reportable database of email information. --- Set up steps To implement this workflow, follow these configuration steps: Prepare the Data Table: Create a new Data Table within n8n. Define the columns with the following names and string type: From, To, Subject, and Summary. Configure Email Credentials: Set up the credential connections for the email services you wish to use (Gmail OAuth2, Microsoft Outlook OAuth2, and/or IMAP). Ensure the accounts have the necessary permissions to read emails. Configure AI Model Credentials: Set up the OpenAI API credential with a valid API key. The workflow is configured to use the model, but this can be changed in the respective nodes if needed. Connect the Nodes: The workflow canvas is already correctly wired. Visually confirm that the email triggers are connected to the "Parsing Agent," which is connected to the "Insert row" (Data Table) node. Also, ensure the "OpenAI Chat Model" and "Structured Output Parser" are connected to the "Parsing Agent" as its AI model and output parser, respectively. Activate the Workflow: Save the workflow and toggle the "Active" switch to ON. The triggers will begin polling for new emails according to their schedule (e.g., every minute), and the automation will start processing incoming messages. --- Need help customizing? Contact me for consulting and support or add me on Linkedin.

DavideBy Davide
1616

Tax deadline management & compliance alerts with GPT-4, Google Sheets & Slack

AI-Driven Tax Compliance & Deadline Management System Description Automate tax deadline monitoring with AI-powered insights. This workflow checks your tax calendar daily at 8 AM, uses GPT-4 to analyze upcoming deadlines across multiple jurisdictions, detects overdue and critical items, and sends intelligent alerts via email and Slack only when immediate action is required. Perfect for finance teams and accounting firms who need proactive compliance management without manual tracking. 🏛️🤖📊 Good to Know AI-Powered: GPT-4 provides risk assessment and strategic recommendations Multi-Jurisdiction: Handles Federal, State, and Local tax requirements automatically Smart Alerts: Only notifies executives when deadlines are overdue or critical (≤3 days) Priority Classification: Categorizes deadlines as Overdue, Critical, High, or Medium priority Dual Notifications: Critical alerts to leadership + daily summaries to team channel Complete Audit Trail: Logs all checks and deadlines to Google Sheets for compliance records How It Works Daily Trigger - Runs at 8:00 AM every morning Fetch Data - Pulls tax calendar and company configuration from Google Sheets Analyze Deadlines - Calculates days remaining, filters by jurisdiction/entity type, categorizes by priority AI Analysis - GPT-4 provides strategic insights and risk assessment on upcoming deadlines Smart Routing - Only sends alerts if overdue or critical deadlines exist Critical Alerts - HTML email to executives + Slack alert for urgent items Team Updates - Slack summary to finance channel with all upcoming deadlines Logging - Records compliance check results to Google Sheets for audit trail Requirements Google Sheets Structure Sheet 1: TaxCalendar DeadlineID | DeadlineName | DeadlineDate | Jurisdiction | Category | AssignedTo | IsActive FED-Q1 | Form 1120 Q1 | 2025-04-15 | Federal | Income | John Doe | TRUE Sheet 2: CompanyConfig (single row) Jurisdictions | EntityType | FiscalYearEnd Federal, California | Corporation | 12-31 Sheet 3: ComplianceLog (auto-populated) Date | AlertLevel | TotalUpcoming | CriticalCount | OverdueCount 2025-01-15 | HIGH | 12 | 3 | 1 Credentials Needed Google Sheets - Service Account OAuth2 OpenAI - API Key (GPT-4 access required) SMTP - Email account for sending alerts Slack - Bot Token with chat:write permission Setup Steps Import workflow JSON into n8n Add all 4 credentials Replace these placeholders: YOURTAXCALENDAR_ID - Tax calendar sheet ID YOURCONFIGID - Company config sheet ID YOURLOGID - Compliance log sheet ID C12345678 - Slack channel ID tax@company.com - Sender email cfo@company.com - Recipient email Share all sheets with Google service account email Invite Slack bot to channels Test workflow manually Activate the trigger Customizing This Workflow Change Alert Thresholds: Edit "Analyze Deadlines" node: Critical: Change <= 3 to <= 5 for 5-day warning High: Change <= 7 to <= 14 for 2-week notice Medium: Change <= 30 to <= 60 for 2-month lookout Adjust Schedule: Edit "Daily Tax Check" trigger: Change hour/minute for different run time Add multiple trigger times for tax season (8 AM, 2 PM, 6 PM) Add More Recipients: Edit "Send Email" node: To: cfo@company.com, director@company.com CC: accounting@company.com BCC: archive@company.com Customize Email Design: Edit "Format Email" node to change colors, add logo, or modify layout Add SMS Alerts: Insert Twilio node after "Is Critical" for emergency notifications Integrate Task Management: Add HTTP Request node to create tasks in Asana/Jira for critical deadlines Troubleshooting | Issue | Solution | |-------|----------| | No deadlines found | Check date format (YYYY-MM-DD) and IsActive = TRUE | | AI analysis failed | Verify OpenAI API key and account credits | | Email not sending | Test SMTP credentials and check if critical condition met | | Slack not posting | Invite bot to channel and verify channel ID format | | Permission denied | Share Google Sheets with service account email | 📞 Professional Services Need help with implementation or customization? Our team offers: 🎯 Custom workflow development 🏢 Enterprise deployment support 🎓 Team training sessions 🔧 Ongoing maintenance 📊 Custom reporting & dashboards 🔗 Additional API integrations Discover more workflows – Get in touch with us

Oneclick AI SquadBy Oneclick AI Squad
93