Send a message to Telegram on a new item saved to Reader
What is it
This workflow aims to build a simple bot that will send a message to a telegram channel every time there is a new saved item to the Reader.
This workflow can be easily modify to support other way of sending the notification, thanks to existing n8n nodes.
Warning: This is only for folks who already have access to the Reader, it won't work if you don't
Also, this workflow use a file to store the last update time in order to not sync everything everytime.
Setup
The config node :
- It contains the telegram channel id
- It also contains the file used as storage
To get the header auth, you have to :
- Go to the reader
- Open the devtools, Option + ⌘ + J (on macOS), or Shift + CTRL + J (on Windows/Linux)
- Go to network and find a
profile_details/request, click on it - Go to Request Headers
- Copy the value for "Cookie"
- In n8n, set the name of the Header auth account to
Cookieand the value with the one you copied before
n8n Workflow: Send a Message to Telegram
This n8n workflow demonstrates a basic setup for sending messages to Telegram. While the provided JSON is a foundational structure, it outlines the core components for triggering an action and sending data to Telegram.
What it does
This workflow provides a starting point for creating a Telegram notification system.
- Starts Manually or on Schedule: The workflow can be triggered manually or configured to run at specified intervals using the Cron node.
- Processes Data (Placeholder): It includes several core n8n nodes like Function, Function Item, HTTP Request, Read Binary File, Edit Fields (Set), Write Binary File, and Convert to/from binary data. These nodes are currently unconnected and serve as placeholders, indicating potential steps for data manipulation, external API calls, file operations, and data transformation that could precede sending a message.
- Sends Message to Telegram: The final connected node is a Telegram node, which is intended to send a message.
Prerequisites/Requirements
- n8n Instance: A running instance of n8n.
- Telegram Account: A Telegram account and a Bot Token. You will need to create a new bot via BotFather on Telegram to get your token and chat ID.
- Telegram Credential: An n8n Telegram credential configured with your Bot Token.
Setup/Usage
- Import the workflow: Import the provided JSON into your n8n instance.
- Configure Telegram Credential:
- Click on the "Telegram" node.
- Under "Credentials", click "Create New".
- Enter your Telegram Bot Token (obtained from BotFather).
- Save the credential.
- Configure Telegram Chat ID:
- In the "Telegram" node, set the "Chat ID" to the recipient's chat ID (can be a user ID or a group ID).
- Set the "Text" field to the message you wish to send.
- Activate the Workflow: Enable the workflow to make it active.
- Trigger the Workflow:
- You can manually execute the workflow by clicking "Execute Workflow" in the n8n editor.
- If you enable the "Cron" node and configure its schedule, the workflow will trigger automatically based on that schedule.
Note on Placeholder Nodes: The workflow includes several unconnected nodes (Function, Function Item, HTTP Request, Read Binary File, Edit Fields (Set), Write Binary File, Convert to/from binary data). These are currently inactive and serve as examples of how you might integrate data processing, API calls, or file operations into your workflow before sending a message via Telegram. You would connect and configure these nodes as needed for your specific use case.
Related Templates
Daily cash flow reports with Google Sheets, Slack & Email for finance teams
Simplify financial oversight with this automated n8n workflow. Triggered daily, it fetches cash flow and expense data from a Google Sheet, analyzes inflows and outflows, validates records, and generates a comprehensive daily report. The workflow sends multi-channel notifications via email and Slack, ensuring finance professionals stay updated with real-time financial insights. 💸📧 Key Features Daily automation keeps cash flow tracking current. Analyzes inflows and outflows for actionable insights. Multi-channel alerts enhance team visibility. Logs maintain a detailed record in Google Sheets. Workflow Process The Every Day node triggers a daily check at a set time. Get Cash Flow Data retrieves financial data from a Google Sheet. Analyze Inflows & Outflows processes the data to identify trends and totals. Validate Records ensures all entries are complete and accurate. If records are valid, it branches to: Sends Email Daily Report to finance team members. Send Slack Alert to notify the team instantly. Logs to Sheet appends the summary data to a Google Sheet for tracking. Setup Instructions Import the workflow into n8n and configure Google Sheets OAuth2 for data access. Set the daily trigger time (e.g., 9:00 AM IST) in the "Every Day" node. Test the workflow by adding sample cash flow data and verifying reports. Adjust analysis parameters as needed for specific financial metrics. Prerequisites Google Sheets OAuth2 credentials Gmail API Key for email reports Slack Bot Token (with chat:write permissions) Structured financial data in a Google Sheet Google Sheet Structure: Create a sheet with columns: Date Cash Inflow Cash Outflow Category Notes Updated At Modification Options Customize the "Analyze Inflows & Outflows" node to include custom financial ratios. Adjust the "Validate Records" filter to flag anomalies or missing data. Modify email and Slack templates with branded formatting. Integrate with accounting tools (e.g., Xero) for live data feeds. Set different trigger times to align with your financial review schedule. Discover more workflows – Get in touch with us
By Oneclick AI SquadAutomatically detect & classify GitHub API errors with GPT-4o to Airtable, Notion & Slack
Automatically detect, classify, and document GitHub API errors using AI. This workflow connects GitHub, OpenAI (GPT-4o), Airtable, Notion, and Slack to build a real-time, searchable API error knowledge base — helping engineering and support teams respond faster, stay aligned, and maintain clean documentation. ⚙️📘💬 🚀 What This Template Does 1️⃣ Triggers on new or updated GitHub issues (API-related). 🪝 2️⃣ Extracts key fields (title, body, repo, and link). 📄 3️⃣ Classifies issues using OpenAI GPT-4o, identifying error type, category, root cause, and severity. 🤖 4️⃣ Validates & parses AI output into structured JSON format. ✅ 5️⃣ Creates or updates organized FAQ-style entries in Airtable for quick lookup. 🗂️ 6️⃣ Logs detailed entries into Notion, maintaining an ongoing issue knowledge base. 📘 7️⃣ Notifies the right Slack team channel (DevOps, Backend, API, Support) with concise summaries. 💬 8️⃣ Tracks & prevents duplicates, keeping your error catalog clean and auditable. 🔄 💡 Key Benefits ✅ Converts unstructured GitHub issues into AI-analyzed documentation ✅ Centralizes API error intelligence across teams ✅ Reduces time-to-resolution for recurring issues ✅ Maintains synchronized records in Airtable & Notion ✅ Keeps DevOps and Support instantly informed through Slack alerts ✅ Fully automated, scalable, and low-cost using GPT-4o ⚙️ Features Real-time GitHub trigger for API or backend issues GPT-4o-based AI classification (error type, cause, severity, confidence) Smart duplicate prevention logic Bi-directional sync to Airtable + Notion Slack alerts with contextual AI insights Modular design — easy to extend with Jira, Teams, or email integrations 🧰 Requirements GitHub OAuth2 credentials OpenAI API key (GPT-4o recommended) Airtable Base & Table IDs (with fields like Error Code, Category, Severity, Root Cause) Notion integration with database access Slack Bot token with chat:write scope 👥 Target Audience Engineering & DevOps teams managing APIs Customer support & SRE teams maintaining FAQs Product managers tracking recurring API issues SaaS orgs automating documentation & error visibility 🪜 Step-by-Step Setup Instructions 1️⃣ Connect your GitHub account and enable the “issues” webhook event. 2️⃣ Add OpenAI credentials (GPT-4o model for classification). 3️⃣ Create an Airtable base with fields: Error Code, Category, Root Cause, Severity, Confidence. 4️⃣ Configure your Notion database with matching schema and access. 5️⃣ Set up Slack credentials and choose your alert channels. 6️⃣ Test with a sample GitHub issue to validate AI classification. 7️⃣ Enable the workflow — enjoy continuous AI-powered issue documentation!
By Rahul JoshiAutomate bank statement and invoice reconciliation with GPT and Google Sheets
🟢 Manual Trigger Workflow starts manually to initiate the reconciliation process on demand. 📄 Fetch Invoices & Bank Statements Retrieves invoice data and bank statement data from Google Sheets for comparison. 🔀 Merge Data Combines both datasets into a single structured dataset for processing. 🧩 Format Payload for AI Function node prepares and structures the merged data into a clean JSON payload for AI analysis. 🤖 AI Reconciliation AI Agent analyzes the invoice and bank statement data to identify matches, discrepancies, and reconciled entries. 🧮 Parse AI Output Parses the AI response into a structured format suitable for adding back to Google Sheets. 📊 Update Sheets Adds the reconciled data and reconciliation results into the target Google Sheet for recordkeeping. 🧾 Prerequisites ✅ OpenAI API Credentials Required for the AI Reconciliation node to process and match transactions. Add your OpenAI API key in n8n → Credentials → OpenAI. ✅ Google Sheets Credentials Needed to read invoice and bank statement data and to write reconciled results. Add credentials in n8n → Credentials → Google Sheets. ✅ Google Sheets Setup The connected spreadsheet must contain the following tabs: Invoices – for invoice data Bank_Statement – for bank transaction data Reconciled_Data – for storing the AI-processed reconciliation output ✅ Tab Structure & Required Headers Invoices Sheet Columns: Invoice_ID Invoice_Date Customer_Name Amount Status Bank_Statement Sheet Columns: Transaction_ID Transaction_Date Description Debit/Credit Amount Reconciled_Data Sheet Columns: Invoice_ID Transaction_ID Matched_Status Remarks Confidence_Score ⚙️ n8n Environment Setup Ensure all nodes are connected correctly and the workflow has permission to access the required sheets. Test each fetch and write operation before running the full workflow.
By Chintan Prajapati