Back to Catalog

Generate personalized sales outreach from LinkedIn job signals with Apify & Google Gemini

Intuz Intuz
241 views
2/3/2026
Official Page

Overview.PNG

This n8n template from Intuz provides a complete and automated solution for identifying high-intent leads from LinkedIn job postings and automatically generating personalized outreach emails.

Disclaimer

Community nodes are used in this workflow.

Who’s this workflow for?

  • B2B Sales Teams & SDRs
  • Recruitment Agencies & Tech Recruiters
  • Startup Founders
  • Growth Marketing Teams

How it works

1. Scrape Hiring Signals: The workflow starts by using an Apify scraper to find companies actively hiring for specific roles on LinkedIn (e.g., “ML Engineer”).

2. Filter & Qualify Companies: It automatically filters the results based on your criteria (e.g., company size, industry) to create a high-quality list of target accounts.

3. Find Decision-Makers: For each qualified company, it uses Apollo.io to find key decision-makers (VPs, Directors, etc.) and enrich their profiles with verified email addresses using user’s Apollo API.

4. Build a Lead List: All the enriched lead data—contact name, title, email, company info—is systematically added to a Google Sheet.

5. Generate AI-Powered Emails: The workflow then feeds each lead’s data to a Google Gemini AI model, which drafts a unique, personalized cold email that references the specific job the company is hiring for.

6. Complete the Outreach List: Finally, the AI-generated subject line and email body are saved back into the Google Sheet, leaving you with a fully prepared, hyper-targeted outreach campaign.

Setup Instructions

1. Apify Configuration:

  • Connect your Apify account in the Run the LinkedIn Job Scraper node.
  • You’ll need an apify scrapper, we have used this scrapper
  • In the Custom Body field, paste the URL of your target LinkedIn Jobs search query.

2. Data Enrichment:

  • Connect your account API of data providers like Clay, Hunter, Apollo, etc. using HTTP Header Auth in the Get Targeted Personnel and Email Finder nodes.

3. Google Gemini AI:

  • Connect your Google Gemini (or PaLM) API account in the Google Gemini Chat Model node.

4. Google Sheets Setup:

  • Connect your Google Sheets account.
  • Create a spreadsheet and update the Document ID and Sheet Name in the three Google Sheets nodes to match your own.

5. Activate Workflow:

  • Click “Execute workflow” to run the entire lead generation and email-writing process on demand.

Connect with us:

  • Website: https://www.intuz.com/services
  • Email: getstarted@intuz.com
  • LinkedIn: https://www.linkedin.com/company/intuz
  • Get Started: https://n8n.partnerlinks.io/intuz

For Custom Workflow Automation

Click here- Get Started

Generate Personalized Sales Outreach from LinkedIn Job Signals with Apify & Google Gemini

This n8n workflow automates the process of generating highly personalized sales outreach messages by leveraging LinkedIn job signals. It uses Apify to scrape job data, Google Gemini to craft tailored messages, and Google Sheets to manage the input and output.

What it does

This workflow streamlines your sales outreach by:

  1. Triggering Manually: Initiates the workflow upon manual execution.
  2. Fetching Job Data: Retrieves a specified number of job postings from a Google Sheet.
  3. Filtering Data: Ensures only valid job entries (where a 'jobUrl' exists) are processed.
  4. Extracting Job ID: Uses a Code node to extract the unique job ID from the LinkedIn job URL.
  5. Scraping LinkedIn Job Details (Apify): Utilizes an HTTP Request node to call the Apify API, specifically the "LinkedIn Job Scraper" actor, to get detailed information about the job posting using the extracted job ID.
  6. Parsing Scraped Data: Processes the JSON output from Apify to make it usable for the next steps.
  7. Generating Personalized Outreach (Google Gemini): Employs a Basic LLM Chain with the Google Gemini Chat Model to generate a personalized sales outreach message based on the scraped job description and other relevant details.
  8. Structuring LLM Output: Uses a Structured Output Parser to extract the generated outreach message and a summary of the job description into a defined JSON format.
  9. Merging Data: Combines the original job data with the newly generated outreach message and job summary.
  10. Removing Duplicates: Ensures that only unique outreach messages are processed further.
  11. Limiting Output: Restricts the number of items processed to avoid overwhelming downstream systems (e.g., for testing or batch processing).
  12. Updating Google Sheet: Writes the generated personalized outreach message and job summary back to the original Google Sheet, associating them with the respective job entries.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running instance of n8n.
  • Google Sheets Account: To store and retrieve job posting data.
  • Apify Account: With access to the "LinkedIn Job Scraper" actor and an API token.
  • Google Gemini API Key: For the Google Gemini Chat Model.
  • n8n Credentials: Configured for Google Sheets, Apify (HTTP Request), and Google Gemini.

Setup/Usage

  1. Import the Workflow: Download the JSON provided and import it into your n8n instance.
  2. Configure Credentials:
    • Google Sheets: Set up a Google Sheets credential. Specify the spreadsheet ID and sheet name where your job data is stored and where the outreach messages will be written. Ensure the sheet has columns for jobUrl, personalized_outreach, and job_description_summary.
    • Apify (HTTP Request): Create an HTTP Request credential for Apify. You will need your Apify API token.
    • Google Gemini: Set up a Google Gemini Chat Model credential with your API key.
  3. Review Node Configurations:
    • Google Sheets (Read): Ensure the "Spreadsheet ID" and "Sheet Name" are correctly set to read the initial job data.
    • HTTP Request (Apify): Verify the Apify API endpoint and the token parameter in the URL query. Ensure the jobId is correctly passed from the previous node.
    • Google Gemini Chat Model: Review the prompt to ensure it aligns with your desired outreach message style and content.
    • Structured Output Parser: Confirm the schema matches the expected output from the Gemini model.
    • Google Sheets (Update): Ensure the "Spreadsheet ID" and "Sheet Name" are correctly set to write the results, and the "Update Key" is set to jobUrl (or another unique identifier) to match the correct rows.
  4. Activate the Workflow: Once configured, activate the workflow.
  5. Execute Manually: Click "Execute Workflow" to run it. The workflow will fetch jobs, generate outreach, and update your Google Sheet.

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

🎓 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