Turn HR news into policy update tasks and a weekly Gmail digest with RSS, Google Drive, Gemini, and GPT-5.2

Open on n8n.io

$20/month : Unlimited workflows

2500 executions/month

Try free

THE #1 IN WEB SCRAPING

Scrape any website without limits

Try free

HOSTINGER

Early Deal
DISCOUNT 20%

Self-hosted n8n

Unlimited workflows - from $4.99/mo

Try free

#1 hub for scraping, AI & automation

6000+ actors - $5 credits/mo

Try free

1. Workflow Overview

HR Weekly Radar AI powered workflow that scans HR news via RSS, checks which of your policies or contract templates might need updates, and sends a weekly internal newsletter as HTML. What this tem...

Best for

HR automation workflows
AI RAG automation workflows
advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.scheduletrigger, n8n-nodes-base.set, n8n-nodes-base.rssfeedread, n8n-nodes-base.filter, n8n-nodes-base.code, n8n-nodes-base.httprequest, n8n-nodes-base.html, n8n-nodes-base.merge

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Paul Karrmann.

Original n8n.io source

1.1 Workflow description

Title: Turn HR news into policy update tasks and a weekly Gmail digest with RSS, Google Drive, Gemini, and GPT-5.2
Workflow name: Turn HR news into policy update tasks and a weekly Gmail digest with RSS, Google Drive, Gemini, and GPT-5.2

HR Weekly Radar

AI powered workflow that scans HR news via RSS, checks which of your policies or contract templates might need updates, and sends a weekly internal newsletter as HTML.

What this template is for

If you maintain an HR policy and template library, this helps you spot relevant changes faster and turn them into a small, actionable review list.

Good to know

This workflow fetches article pages and sends extracted text to LLMs
Respect the publisher’s terms and avoid redistributing full article text outside your organization
Cost and runtime depend on how many articles you process and how long the extracted text is

How it works

Weekly trigger starts the workflow
RSS feed read pulls new HR articles
Filter keeps only the last 7 days
Limit node caps processing to maxArticles
HTTP request fetches each article page
HTML extract + cleanup converts the article body to plain text
Google Drive node lists your policy and template file names
Merge combines each article with the document list
Reading agent evaluates relevance and suggests:
which documents to review or update
what change to consider
missing document ideas
Build report aggregates results across all articles
Summary agent writes a short, scannable HTML email
Gmail sends the newsletter to your chosen recipient

How to use

Add your RSS feed URL in the Workflow Configuration node (newsUrl)
Set your recipient email (userEmail)
Set your Google Drive folder id that contains policies and templates (templatesFolderId)
Connect credentials for:
Google Drive
LLM provider nodes
Gmail
Run once manually and verify the email formatting, then activate the workflow

Requirements

RSS feed URL with HR or compliance updates
Google Drive folder containing policy and template files
LLM credentials for:
per article analysis
newsletter drafting
Gmail account to send the email

Customising this workflow

Increase or decrease maxArticles to control cost and speed
Adjust the last 7 days filter if you want a different reporting window
Change the HTML extraction selector if your news source has a different page layout
Swap the final Gmail node for Slack, Teams, Notion, or Google Docs
Add a redaction step before the Reading Agent if you want to remove signatures or long quoted sections

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Weekly trigger

Type / Role: n8n-nodes-base.scheduleTrigger - scheduleTrigger
Config choices: Version 1.3

Block 2 - Config

Type / Role: n8n-nodes-base.set - set
Config choices: Version 3.4

Block 3 - Read RSS feed

Type / Role: n8n-nodes-base.rssFeedRead - rssFeedRead
Config choices: Version 1.2

Block 4 - Keep last 7 days

Type / Role: n8n-nodes-base.filter - filter
Config choices: Version 2.3

Block 5 - Cap articles

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 6 - Fetch article page

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.3

Block 7 - Extract article body

Type / Role: n8n-nodes-base.html - html
Config choices: Version 1.2

Block 8 - Clean article text

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 9 - Combine article data

Type / Role: n8n-nodes-base.merge - merge
Config choices: Version 3.2

Block 10 - Normalize article fields

Type / Role: n8n-nodes-base.set - set
Config choices: Version 3.4

Block 11 - Add id and excerpt

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 12 - List policy and template files

Type / Role: n8n-nodes-base.googleDrive - googleDrive
Config choices: Version 3

Block 13 - Aggregate file inventory

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 14 - Attach file inventory

Type / Role: n8n-nodes-base.merge - merge
Config choices: Version 3.2

Block 15 - Structured output schema

Type / Role: @n8n/n8n-nodes-langchain.outputParserStructured - outputParserStructured
Config choices: Version 1.3

Block 16 - Gemini chat model

Type / Role: @n8n/n8n-nodes-langchain.lmChatGoogleGemini - lmChatGoogleGemini
Config choices: Version 1

Block 17 - Doc impact analyzer

Type / Role: @n8n/n8n-nodes-langchain.agent - agent
Config choices: Version 3.1

Block 18 - Build radar report

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 19 - OpenAI chat model

Type / Role: @n8n/n8n-nodes-langchain.lmChatOpenAi - lmChatOpenAi
Config choices: Version 1.3

Block 20 - Email writer

Type / Role: @n8n/n8n-nodes-langchain.agent - agent
Config choices: Version 3.1

Block 21 - Send radar email

Type / Role: n8n-nodes-base.gmail - gmail
Config choices: Version 2.2

Block 22 - Sticky Note5

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 23 - Sticky Note6

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 24 - Sticky Note

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Showing the first 24 of 26 workflow blocks. Download the JSON for the full node graph.

3. Summary Table

Workflow	Turn HR news into policy update tasks and a weekly Gmail digest with RSS, Google Drive, Gemini, and GPT-5.2
Complexity	advanced
Nodes	26
Categories	HR, AI RAG
Author	Paul Karrmann
Published	30 Jan 2026

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

Use the JSON export at /data/workflows/13124/13124.json as the source template for this automation.
2. Import the template into n8n

Open n8n, import the downloaded JSON, and review each node before activating the workflow.
3. Configure credentials and variables

Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
4. Test with sample data

Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
5. Activate and monitor

Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Download workflow JSON Original n8n.io source HR workflows AI RAG workflows

Frequently asked questions

What does Turn HR news into policy update tasks and a weekly Gmail digest with RSS, Google Drive, Gemini, and GPT-5.2 do?

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your HR, AI RAG use case.

Paul Karrmann

3 workflows

Nodes

n8n-nodes-base.scheduletrigger n8n-nodes-base.set n8n-nodes-base.rssfeedread n8n-nodes-base.filter n8n-nodes-base.code n8n-nodes-base.httprequest n8n-nodes-base.html n8n-nodes-base.merge

Complexity

advanced

Published 30 Jan 2026

Likes 0

View on n8n.io Download Workflow

Install path: /data/workflows/13124/13124.json

Share Your Workflow

Have a useful automation to share? Publish it and help the community.

Submit Your Template How to Submit

Related Workflows

Manage employee offboarding with Google Workspace, Slack, HubSpot and Notion

## Quick Overview This workflow receives an HR offboarding webhook, validates and enriches the employee record, suspends the user in Google Workspace, deactivates the user in Slack, looks up the matching HubSpot contact, logs the event to Notion and Google Sheets, and notifies HR/IT via Gmail and Slack. ## How it works 1. Receives a POST webhook from the HR system with employee offboarding details. 2. Parses the payload to normalize key fields (name, email, department, manager, last day) and flags invalid requests. 3. Posts an alert to a Slack IT channel when the record is invalid and stops further processing. 4. Enriches valid records with an offboarding ID, risk level, revocation deadline, and an actions summary. 5. Suspends the employee in Google Workspace via the Admin Directory API, deactivates the user in Slack via the Slack API, searches for the contact in HubSpot, and creates an offboarding entry in a Notion database. 6. Combines the revocation results and appends a compliance log row to a Google Sheets “Offboarding Log” tracker. 7. Emails an offboarding completion summary to the manager and HR using Gmail and posts a completion digest to the Slack IT channel. ## Setup 1. Copy the n8n webhook URL from the HR offboarding webhook trigger and configure your HR system to POST the offboarding payload to it. 2. Provide credentials/tokens for the Google Admin Directory API and Slack API (both used via HTTP requests) and replace the placeholder Bearer tokens in the request headers. 3. Add a HubSpot App Token credential with access to search contacts. 4. Create a Notion database for offboarding logs, add a Notion API integration, and set the Notion database ID and API key in the Notion request. 5. Add Google Sheets OAuth credentials, set your Google Sheet ID, and ensure the “Offboarding Log” sheet contains the columns mapped in the append step. 6. Add a Gmail connection for sending summary emails and set the target Slack channel ID for the invalid-record alert and IT ops digest messages.

View

Send AI interview briefs from resumes with GPT-4o-mini, Google Sheets and Gmail

## Quick Overview This workflow runs every 15 minutes to read candidate rows from Google Sheets, download each resume PDF from Google Drive, extract text, generate an HTML interview brief using OpenAI GPT-4o-mini, email it via Gmail to the interviewer, and mark the row as Processed to avoid duplicates. ## How it works 1. Runs on a schedule trigger every 15 minutes. 2. Reads all candidate rows from the “Candidates” tab in Google Sheets and processes them one at a time. 3. Skips any rows where the Status column is already set to “Processed.” 4. Extracts the Google Drive file ID from the resume link, downloads the PDF, and converts it to plain text. 5. Cleans and truncates the resume text and combines it with the candidate’s name, role, and email details. 6. Sends the resume text and metadata to OpenAI (GPT-4o-mini) to generate a styled HTML interviewer brief. 7. Emails the HTML brief to the interviewer via Gmail and updates the candidate row in Google Sheets to “Processed,” then waits 5 seconds before moving to the next candidate. ## Setup 1. Add Google Sheets OAuth credentials and replace `YOUR_CANDIDATES_SHEET_ID`, then create a “Candidates” sheet with columns Name, Email, Job Role, Resume Drive Link, Interviewer Email, and Status. 2. Add Google Drive OAuth credentials and ensure each resume PDF is accessible to the workflow (for example, shared so the connected account can view it). 3. Add an OpenAI API credential and keep the model set to GPT-4o-mini. 4. Add Gmail OAuth credentials and confirm the sender name and subject line meet your email requirements. 5. Adjust the schedule interval if you want the workflow to check for new candidates more or less frequently.

View

Provision new hire IT accounts with Google Workspace, Slack, and Gmail

## Quick Overview This workflow receives new-hire records via a webhook, validates and normalizes the data, then provisions a Google Workspace account, creates an onboarding task in Google Tasks, notifies the IT team in Slack, emails the hiring manager via Gmail, and logs the run to Google Sheets. ## How it works 1. Receives a new hire payload from the HR system through an HTTP webhook endpoint. 2. Parses the payload, standardizes key fields (name, department, manager, start date), and skips records missing required identity data. 3. If the record is invalid, posts a Slack message to the IT channel for manual review and stops processing. 4. For valid hires, generates a company email address, username, temporary password, ticket title, and a target ready-by date. 5. Creates the new user in the Google Admin Directory (Google Workspace) and opens an IT onboarding checklist as a Google Tasks task. 6. Posts a provisioning summary to the IT Slack channel, emails the manager a day-one checklist via Gmail, and appends the provisioning details to a Google Sheets log. ## Setup 1. Configure your HR system (or source app) to send a POST request to the workflow webhook path `/hr/new-hire` using the production webhook URL. 2. Add Google credentials with access to the Admin SDK Directory API (for user creation), Google Tasks, Gmail, and Google Sheets, and ensure the account has the required admin permissions. 3. Add Slack credentials, set the target channel ID for IT onboarding notifications, and update the channel selection if needed. 4. Update the email domain in the generated address (currently `@yourcompany.com`) and confirm how departments map to Google Workspace org unit paths. 5. Set your Google Sheets document ID and ensure it contains (or can create) a sheet named "Provisioning Log" with matching columns for the appended fields.

View

Need Custom Automation?

Get help designing a custom n8n workflow that connects your stack and fits your process.

Turn HR news into policy update tasks and a weekly Gmail digest with RSS, Google Drive, Gemini, and GPT-5.2

Workflow preview

1. Workflow Overview

Best for

Tools used

Source and attribution

1.1 Workflow description

HR Weekly Radar

What this template is for

Good to know

How it works

How to use

Requirements

Customising this workflow

1.2 Logical Blocks

2. Block-by-Block Analysis

Block 1 - Weekly trigger

Block 2 - Config

Block 3 - Read RSS feed

Block 4 - Keep last 7 days

Block 5 - Cap articles

Block 6 - Fetch article page

Block 7 - Extract article body

Block 8 - Clean article text

Block 9 - Combine article data

Block 10 - Normalize article fields

Block 11 - Add id and excerpt

Block 12 - List policy and template files

Block 13 - Aggregate file inventory

Block 14 - Attach file inventory

Block 15 - Structured output schema

Block 16 - Gemini chat model

Block 17 - Doc impact analyzer

Block 18 - Build radar report

Block 19 - OpenAI chat model

Block 20 - Email writer

Block 21 - Send radar email

Block 22 - Sticky Note5

Block 23 - Sticky Note6

Block 24 - Sticky Note

3. Summary Table

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

2. Import the template into n8n

3. Configure credentials and variables

4. Test with sample data

5. Activate and monitor

5. General Notes & Resources

Frequently asked questions