AI-powered information monitoring with OpenAI, Google Sheets, Jina AI and Slack

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

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

Check Legal Regulations : This workflow involves scraping, so ensure you comply with the legal regulations in your country before getting started. Better safe than sorry! Purpose This workflow e...

Best for

Market Research automation workflows
AI Summarization automation workflows
advanced n8n builders looking for reusable templates

Tools used

@n8n/n8n-nodes-langchain.lmchatopenai, @n8n/n8n-nodes-langchain.chainllm, n8n-nodes-base.scheduletrigger, n8n-nodes-base.rssfeedread, @n8n/n8n-nodes-langchain.textclassifier, n8n-nodes-base.stickynote, n8n-nodes-base.googlesheets, n8n-nodes-base.slack

Source and attribution

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

Original n8n.io source

1.1 Workflow description

Title: AI-powered information monitoring with OpenAI, Google Sheets, Jina AI and Slack
Workflow name: AI-powered information monitoring with OpenAI, Google Sheets, Jina AI and Slack

Check Legal Regulations: This workflow involves scraping, so ensure you comply with the legal regulations in your country before getting started. Better safe than sorry!

📌 Purpose

This workflow enables automated and AI-driven topic monitoring, delivering concise article summaries directly to a Slack channel in a structured and easy-to-read format.
It allows users to stay informed on specific topics of interest effortlessly, without manually checking multiple sources, ensuring a time-efficient and focused monitoring experience.

To get started, copy the Google Sheets template required for this workflow from here.

🎯 Target Audience

This workflow is designed for:

Industry professionals looking to track key developments in their field.
Research teams who need up-to-date insights on specific topics.
Companies aiming to keep their teams informed with relevant content.

⚙️ How It Works

Trigger: A Scheduler initiates the workflow at regular intervals (default: every hour).
Data Retrieval:
- RSS feeds are fetched using the RSS Read node.
- Previously monitored articles are checked in Google Sheets to avoid duplicates.
Content Processing:
- The article relevance is assessed using OpenAI (GPT-4o-mini).
- Relevant articles are scraped using Jina AI to extract content.
- Summaries are generated and formatted for Slack.
Output:
- Summaries are posted to the specified Slack channel.
- Article metadata is stored in Google Sheets for tracking.

🛠️ Key APIs and Nodes Used

Scheduler Node: Triggers the workflow periodically.
RSS Read: Fetches the latest articles from defined RSS feeds.
Google Sheets: Stores monitored articles and manages feed URLs.
OpenAI API (GPT-4o-mini): Classifies article relevance and generates summaries.
Jina AI API: Extracts the full content of relevant articles.
Slack API: Posts formatted messages to Slack channels.

This workflow provides an efficient and intelligent way to stay informed about your topics of interest, directly within Slack.

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 - OpenAI Chat Model

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

Block 2 - Basic LLM Chain

Type / Role: @n8n/n8n-nodes-langchain.chainLlm - chainLlm
Config choices: Version 1.5

Block 3 - Schedule Trigger

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

Block 4 - RSS Read

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

Block 5 - Relevance Classification for Topic Monitoring

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

Block 6 - Sticky Note

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

Block 7 - Sticky Note3

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

Block 8 - Google Sheets - Get RSS Feed url followed

Type / Role: n8n-nodes-base.googleSheets - googleSheets
Config choices: Version 4.5

Block 9 - Sticky Note4

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

Block 10 - Sticky Note6

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

Block 11 - Sticky Note5

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

Block 12 - Slack1

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

Block 13 - Sticky Note8

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

Block 14 - Sticky Note9

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

Block 15 - Sticky Note10

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

Block 16 - Sticky Note2

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

Block 17 - Sticky Note11

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

Block 18 - Sticky Note12

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

Block 19 - Sticky Note1

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

Block 20 - Sticky Note7

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

Block 21 - Google Sheets - Get article monitored database

Type / Role: n8n-nodes-base.googleSheets - googleSheets
Config choices: Version 4.5

Block 22 - Code

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

Block 23 - No Operation, do nothing

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

Block 24 - If

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

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

3. Summary Table

Workflow	AI-powered information monitoring with OpenAI, Google Sheets, Jina AI and Slack
Complexity	advanced
Nodes	31
Categories	Market Research, AI Summarization
Author	Dataki
Published	25 Jan 2025

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

Use the JSON export at /data/workflows/2799/2799.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 Market Research workflows AI Summarization workflows

Frequently asked questions

What does AI-powered information monitoring with OpenAI, Google Sheets, Jina AI and Slack do?

Check Legal Regulations : This workflow involves scraping, so ensure you comply with the legal regulations in your country before getting started. Better safe than sorry! Purpose This workflow e...

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 Market Research, AI Summarization use case.

Dataki

14 workflows

Nodes

@n8n/n8n-nodes-langchain.lmchatopenai @n8n/n8n-nodes-langchain.chainllm n8n-nodes-base.scheduletrigger n8n-nodes-base.rssfeedread @n8n/n8n-nodes-langchain.textclassifier n8n-nodes-base.stickynote n8n-nodes-base.googlesheets n8n-nodes-base.slack

Complexity

advanced

Published 25 Jan 2025

Likes 0

View on n8n.io Download Workflow

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

Share Your Workflow

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

Submit Your Template How to Submit

Related Workflows

Answer BigQuery questions in Microsoft Teams with Claude 3.5 dual agents

## Quick overview Turn Microsoft Teams into a natural language BI tool. This dual-agent Claude workflow intelligently classifies user questions, generates safe BigQuery SQL, executes the query, and returns a plain-English summary alongside a data preview directly to your Teams channel. ## How it works 1. The workflow listens for new messages in a designated Microsoft Teams channel or chat. 2. It checks a 24-hour static data cache for your BigQuery schema. If the cache is missing or expired, it automatically fetches the latest INFORMATION_SCHEMA metadata. 3. A main Claude 3.5 Sonnet agent classifies the user's intent (analytical, conversational, or unsafe) and identifies the relevant database tables. 4. If the intent is analytical, a specialized Claude SQL sub-agent generates a read-only SELECT query tailored exactly to your schema. 5. The workflow executes the query against BigQuery (safely constrained to a maximum of 100 rows). 6. A final Claude agent translates the raw query results into a concise, plain-English summary. 7. The answer is posted back to Teams as an Adaptive Card, complete with a formatted data preview and the generated SQL code. 8. Non-analytical questions or pipeline errors are intelligently routed to receive standard conversational replies in Teams. ## Setup 1. CRITICAL SECURITY: Restrict your Google Cloud Service Account IAM roles to BigQuery Data Viewer and BigQuery Job User ONLY. Do not use a highly privileged account. 2. Configure your Microsoft Teams trigger and posting credentials, specifying the target team and channel for the bot to operate in. 3. Configure your Google BigQuery credentials to allow reading metadata and executing queries. 4. Configure your Anthropic credentials for the three Claude LangChain nodes. 5. Update the "Configure Variables" node with your specific GCP Project ID and BigQuery Dataset ID. ## Requirements - A Google Cloud project with BigQuery enabled and existing structured datasets. - An Anthropic API key with access to the Claude 3.5 Sonnet model. - Microsoft Teams administrator access to authorize the n8n integration. ## Customization - Distributed Environments: If you are running n8n with multiple worker nodes (Queue Mode), you must swap the $getWorkflowStaticData() schema cache logic to read/write from a dedicated Key-Value store (like Redis or Supabase) to ensure state synchronization. - UI Layout: Modify the Create Teams Adaptive Card node to add corporate branding, custom colors, or alter the FactSet data preview structure. ## Additional info This architecture features built-in pipeline protections, including strict 40,000-character payload limits to prevent LLM context window blowouts, and fallback handling for "zero-row" query results to ensure users are never left without a response.

View

Evaluate LinkedIn profiles with Apify and Groq Llama chat model

## Quick overview This workflow collects a LinkedIn profile URL via an n8n form, scrapes the public profile data using the Apify LinkedIn Profile Scraper actor, analyzes the results with a Groq-hosted Llama model, and displays an HTML-formatted evaluation back to the user. ## How it works 1. Receives a LinkedIn Profile URL when a user submits the n8n form. 2. Prepares the LinkedIn URL along with the Apify API token and Groq API key used for downstream requests. 3. Sends the profile URL to the Apify `harvestapi/linkedin-profile-scraper` actor and retrieves the scraped dataset items. 4. Passes the scraped profile JSON to a Groq chat model via an LLM chain to generate an HTML evaluation with a score and recommendations. 5. Displays the generated HTML evaluation to the user as the form completion message. ## Setup 1. Add a valid Apify API token and ensure the Apify actor endpoint (`harvestapi/linkedin-profile-scraper`) is accessible for your account. 2. Add Groq API credentials in n8n and confirm the selected model (meta-llama/llama-4-scout-17b-16e-instruct) is available to your Groq account. 3. Replace the placeholder API key values in the workflow (or move them to n8n credentials/environment variables) and verify the form field label matches `LinkedIn Profile URL`.

View

Validate startup ideas with Google Gemini, Groq, and Gmail

## Quick overview This workflow collects a startup idea via an n8n form, uses Google Gemini to generate a SWOT-style analysis, assigns a viability score, uses Groq to turn the results into a structured validation report, and emails the final report through Gmail. ## How it works 1. Receives a startup idea, industry, and target audience from an n8n Form trigger. 2. Sends the submission to Google Gemini to generate a professional analysis covering the problem, business model, and SWOT factors. 3. Generates a startup viability score (currently a random value from 80–100) and packages it with the Gemini analysis. 4. Sends the score and analysis to Groq (Llama 3.3 70B) to compile a full validation report with an executive summary, market potential, recommendations, and final verdict. 5. Emails the generated validation report to the configured recipient using Gmail. ## Setup 1. Add credentials for Google Gemini (PaLM) API, Groq API, and a Gmail OAuth2 connection. 2. Replace the placeholder recipient address in the Gmail step ("[email protected]") with your target email address before activating the workflow. 3. Publish the n8n form, then share the form URL with the users who should submit their startup ideas for validation.

View

Need Custom Automation?

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

AI-powered information monitoring with OpenAI, Google Sheets, Jina AI and Slack

Workflow preview

Important notice

1. Workflow Overview

Best for

Tools used

Source and attribution

1.1 Workflow description

📌 Purpose

🎯 Target Audience

⚙️ How It Works

🛠️ Key APIs and Nodes Used

1.2 Logical Blocks

2. Block-by-Block Analysis

Block 1 - OpenAI Chat Model

Block 2 - Basic LLM Chain

Block 3 - Schedule Trigger

Block 4 - RSS Read

Block 5 - Relevance Classification for Topic Monitoring

Block 6 - Sticky Note

Block 7 - Sticky Note3

Block 8 - Google Sheets - Get RSS Feed url followed

Block 9 - Sticky Note4

Block 10 - Sticky Note6

Block 11 - Sticky Note5

Block 12 - Slack1

Block 13 - Sticky Note8

Block 14 - Sticky Note9

Block 15 - Sticky Note10

Block 16 - Sticky Note2

Block 17 - Sticky Note11

Block 18 - Sticky Note12

Block 19 - Sticky Note1

Block 20 - Sticky Note7

Block 21 - Google Sheets - Get article monitored database

Block 22 - Code

Block 23 - No Operation, do nothing

Block 24 - If

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