Automate Gmail labeling with Gemini AI & build InfraNodus knowledge graph with Telegram alerts
Automated Gmail Labeling and Brainstorming
This template can be used to automatically label your incoming Gmail messages with AI and to build a knowledge graph from the emails tagged with a specific label to brainstorm new ideas based on them.
You can also get notified about the emails with the most important labels via Telegram as well as receive new ideas as you are building a knowledge graph of incoming messages.
The idea generation is based on the InfraNodus knowledge graph content gap detection algorithm, which builds a network from your content and then finds a blind spot and uses AI to generate an interesting research question or idea that can be used to bridge this gap.

Why it works so well?
Think of all the business emails you receive that bypass the spam filters. Probably, they are personalized to you already. Now imagine if you build a knowledge graph from them for over a month. You will then have a ideation device based on your interests and marketing profile. Now, if you identify the gaps inside and generate interesting research questions based on them, you will come up with new interesting ideas that will be relevant (because they touch on the topics that matter to you), but novel, because they bridge them in new ways.
What is it useful for?
- Automate Gmail incoming message labeling with the new Classifier n8n node β much more advanced than the default Gmail labeling rules.
- Get notified via Telegram (or a messenger of your choice) about the most important messages and be sure not to miss anything important.
- Keep the messages with a certain label saved into knowledge graph for brainstorming and ideation.
- Every time a new message of this category comes in, it's added into the graph, changing its structure, a new idea is generated. So instead of looking at each specific offer, you now use them to generate insights for you.
How it works
-
Step 1: This template can is triggered automatically when a new Gmail message arrives. Note: you need to connect your Gmail account here in this node
-
Step 2: We use the new n8n AI Classifier Node to classify your email based on its content. You might need to update to n8n 1.94 version to make it work. Note: we like to use Gemini AI for that classifier as it's the same company as Gmail, so should be safe with data
-
Step 3: After classifying the message, we label the message with the appropriate label. Note: you need to create the labels before in your Gmail account
-
Step 4: For a certain category (e.g. "Business" you format the message and save it into your InfraNodus graph. Note: specify your InfraNodus API here and choose the name of the graph. It will use the InfraNodus HTTP
graphAndEntriesendpoint and save your data to an InfraNodus graph. By default, we save the text knowledge graph using thecontextSettingsparameters (it will only build a text graph of the content), but you can take an alternative setting from thisΒ InfraNodus HTTP node's settings and create a social knowledge graph, that will also show email senders in the graph itself. -
Step 5 (optional): Generate an interesting insight question with the
graphAndAdviceendpoint of InfraNodus. -
Step 6 (optional): Then send this insight via Telegram to a chat.
-
Step 7 (optional): Link some important labels to the second Telegram notification node, so you receive important messages for specified labels.
-
Step 8 (optional): Send a Telegram notification
We use Telegram, because it takes only 30 seconds to set up a bot with an API (send /newbot to @botfather, unlike Discord or Slack, which is long and cumbersome to set up. You can also attach a Gmail send node and generate an email instead.
How to use
You need an InfraNodus GraphRAG API account and key to use this workflow.
- Create an InfraNodus account or log in.
- Get the API key at https://infranodus.com/api-access and create a Bearer authorization key for the InfraNodus HTTP nodes.
- Add this Authorization code in Steps 4 and 5 of the workflow.
- Come up with the name of the graph and change it in the HTTP InfraNodus nodes in the steps 4 and 5 and also in the Telegram node in Step 6 that sends a link to the graph.
- For additional text processing / idea generation settings you can use in the HTTP InfraNodus nodes, see the InfraNodus access points page. For example, in Step 4 you can change the text processing settings to build a social knowledge graph (settings are available in the Node's Notes section) and in Step 5 you can change the
requestModefromquestiontoideato receive business ideas instead. - Authorize your Gmail account for Steps 2, 3, 7 and 8 Gmail nodes. The easiest way to set it up is to open a free Google Console API account and to create an OAuth access point for n8n. You can then reuse it with other Google services like Google Sheets, Drive, etc. So it's a useful thing to have in general.
- Set up the Gemini AI API key using the instructions in the Step 2 Gemini AI classification node.
- Set up the Telegram node bot for the Step 8. It takes only 30 seconds: just go to @botfather and type in
/newbotand you'll have an API key ready. To get the conversation ID, follow the n8n / Telegram instructions in the node itself. - Once everything is ready, try to run the default automated workflow to test if everything works well.
Requirements
- An InfraNodus account and API key
- An Google Cloud API OAuth client and key for Gmail access
- A Gemini AI API key
- A Telegram bot API key
- n8n version 1.94 and higher (for Text Classification AI node to work)
Customizing this workflow
Check our other n8n workflows at https://n8n.io/creators/infranodus/ for useful content gap analysis, expert panel, and marketing, and research workflows that utilize GraphRAG for better AI generation.
Finally, check out https://infranodus.com to learn more about our network analysis technology used to build knowledge graphs from text.
For support, please, contact https://support.noduslabs.com
Automate Gmail Labeling with Gemini AI & Infranodus Knowledge Graph Alerts
This n8n workflow automates the process of classifying and labeling incoming Gmail emails using Google's Gemini AI, and then sends alerts to Telegram, optionally integrating with Infranodus for knowledge graph creation.
Description
This workflow simplifies email management by intelligently categorizing emails. It listens for new emails in Gmail, uses AI to classify their content, applies appropriate labels in Gmail, and sends real-time notifications via Telegram, with an option to build a knowledge graph in Infranodus.
What it does
- Triggers on New Gmail Emails: Listens for new emails arriving in a specified Gmail account.
- Extracts Email Content: Retrieves the subject and plain text body of the incoming email.
- Classifies Email with AI: Uses a Google Gemini Chat Model (via Langchain's Text Classifier) to categorize the email content.
- Applies Gmail Labels: Based on the AI classification, it applies a corresponding label to the email in Gmail.
- Sends Telegram Alert: Notifies a Telegram chat with details of the classified email and the applied label.
- Optional Infranodus Integration: Prepares the classified email data for potential integration with Infranodus (though the specific HTTP Request for Infranodus is currently a placeholder, it's set up for future expansion).
- Waits for a short period: Includes a
Waitnode, likely to prevent rate limiting or allow for asynchronous processing.
Prerequisites/Requirements
- n8n Instance: A running n8n instance.
- Gmail Account: A Google account with Gmail enabled. You'll need to set up Google OAuth2 credentials in n8n for Gmail.
- Google Gemini API Key: Access to Google Gemini through a Google Cloud project with the Gemini API enabled. You'll need to configure credentials for the Google Gemini Chat Model.
- Telegram Bot Token: A Telegram bot and its API token. You'll need to configure Telegram credentials in n8n.
- Infranodus Account (Optional): If you plan to use the Infranodus integration, an Infranodus account and API access will be required. (Note: The Infranodus HTTP request is currently a placeholder and would need to be fully configured).
Setup/Usage
- Import the workflow: Download the provided JSON and import it into your n8n instance.
- Configure Gmail Trigger:
- Click on the "Gmail Trigger" node.
- Select or create a new "Google OAuth2 API" credential.
- Configure the "Watch For" option (e.g., "New Email").
- Activate the workflow.
- Configure Google Gemini Chat Model:
- Click on the "Google Gemini Chat Model" node.
- Select or create a new "Google Gemini" credential, providing your API key.
- Configure Text Classifier:
- Click on the "Text Classifier" node.
- Ensure it's connected to the Google Gemini Chat Model.
- Define your classification labels and examples within this node to train the AI.
- Configure Gmail (Labeling):
- Click on the "Gmail" node.
- Select the same "Google OAuth2 API" credential used for the trigger.
- Set the operation to "Update" and resource to "Message".
- Map the
IDfrom the Gmail Trigger and thelabelIdsfrom the Text Classifier output to apply the labels.
- Configure Telegram:
- Click on the "Telegram" node.
- Select or create a new "Telegram API" credential, providing your bot token.
- Enter the
Chat IDwhere you want to receive alerts. - Customize the message text to include relevant email and classification details.
- Infranodus (Optional):
- The "HTTP Request" node is named "Infranodus". If you wish to integrate with Infranodus, you will need to:
- Configure the URL for the Infranodus API endpoint.
- Set the HTTP Method (e.g., POST).
- Add any required headers (e.g., API Key for authorization).
- Map the email content and classification data into the request body as required by the Infranodus API.
- The "HTTP Request" node is named "Infranodus". If you wish to integrate with Infranodus, you will need to:
- Activate the Workflow: Once all credentials and configurations are set, activate the workflow. It will now automatically process new emails.
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
π 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.
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