AI-powered Telegram task assistant with Notion integration
This workflow creates a powerful AI assistant in Telegram that helps you manage your tasks in Notion. The assistant leverages OpenAI's language models to understand natural language commands, process voice messages, and maintain context through conversations.
Key features:
- Processes both text and voice messages in Telegram
- Transcribes voice messages automatically
- Maintains conversation context with memory
- Manages Notion tasks through a custom tool: • List all tasks • Add new tasks with priority (today/later) • Complete or uncomplete tasks • Change task timing
The workflow consists of two main parts:
- AI Agent section: Handles Telegram connectivity, message processing, voice transcription, and conversation management
- Notion Tool section: Implements the custom tool that connects to your Notion database, allowing the AI to interact with your tasks
Setup requires:
- A Telegram bot token
- OpenAI API credentials
- Notion integration token and database ID
Perfect for personal productivity, team task management, or as a foundation for building more complex AI assistants with additional tools.
AI-Powered Telegram Task Assistant with Notion Integration
This n8n workflow creates an intelligent Telegram bot that acts as a task assistant, leveraging AI to understand user requests and integrate with Notion for task management. It allows users to create and manage tasks in Notion directly from Telegram messages.
What it does
- Listens for Telegram Messages: The workflow is triggered by incoming messages to a configured Telegram bot.
- Extracts Message Content: It captures the text of the Telegram message.
- Processes with AI Agent: The message is fed to an AI Agent (powered by OpenAI) which is configured with a "Call n8n Workflow Tool" and a "Simple Memory" to maintain conversation context.
- Determines User Intent: The AI Agent analyzes the message to understand if the user wants to create a new task.
- Executes Notion Task Creation (if intent is task creation): If the AI determines the user wants to create a task, it utilizes a specialized n8n workflow tool to interact with Notion.
- Creates Notion Database Item: The Notion node creates a new item in a specified Notion database, populating it with task details extracted by the AI.
- Responds via Telegram: The workflow sends a confirmation or relevant response back to the user in Telegram, based on the AI's output or the success of the Notion operation.
Prerequisites/Requirements
- n8n Instance: A running n8n instance.
- Telegram Bot: A Telegram bot token obtained from BotFather.
- OpenAI API Key: An API key for OpenAI to power the AI Agent.
- Notion Integration: A Notion integration with access to your desired Notion database for tasks. You'll need the database ID and ensure the integration has the necessary permissions.
- Child Workflow for Notion Interaction: This workflow expects a separate, callable n8n workflow (referenced by the "Call n8n Workflow Tool") that handles the actual Notion database item creation. This child workflow should be triggered by the "Execute Workflow Trigger" node and contain the Notion node logic.
Setup/Usage
- Import the Workflow: Import the provided JSON into your n8n instance.
- Configure Telegram Trigger:
- Add your Telegram bot credential to the "Telegram Trigger" node.
- Ensure the webhook is set up correctly for your bot.
- Configure OpenAI Chat Model:
- Add your OpenAI API Key credential to the "OpenAI Chat Model" node.
- Configure AI Agent:
- Review the "AI Agent" node configuration. It uses a "Plan and Execute" agent type.
- Crucially, configure the "Call n8n Workflow Tool":
- You will need to create a separate n8n workflow (a "child workflow") that takes task details as input and creates an item in your Notion database. This child workflow should start with an "Execute Workflow Trigger" node.
- In the "Call n8n Workflow Tool" node, specify the
Workflow IDof your child workflow. - Define the
Input Parametersthat your child workflow expects (e.g.,taskName,dueDate,description).
- Configure Notion Node (in the child workflow):
- In your child workflow, add your Notion credential to the "Notion" node.
- Specify the
Database IDwhere tasks should be created. - Map the input parameters from the "Execute Workflow Trigger" to the Notion database properties (e.g.,
{{ $json.taskName }}to your Notion task title property).
- Activate the Workflows: Ensure both the main Telegram workflow and the child Notion workflow are active.
- Test: Send messages to your Telegram bot like "Create a task: Buy groceries by tomorrow" or "Remind me to call John next week." The AI should interpret these requests and create corresponding entries in Notion.
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
AI-powered code review with linting, red-marked corrections in Google Sheets & Slack
Advanced Code Review Automation (AI + Lint + Slack) Who’s it for For software engineers, QA teams, and tech leads who want to automate intelligent code reviews with both AI-driven suggestions and rule-based linting — all managed in Google Sheets with instant Slack summaries. How it works This workflow performs a two-layer review system: Lint Check: Runs a lightweight static analysis to find common issues (e.g., use of var, console.log, unbalanced braces). AI Review: Sends valid code to Gemini AI, which provides human-like review feedback with severity classification (Critical, Major, Minor) and visual highlights (red/orange tags). Formatter: Combines lint and AI results, calculating an overall score (0–10). Aggregator: Summarizes results for quick comparison. Google Sheets Writer: Appends results to your review log. Slack Notification: Posts a concise summary (e.g., number of issues and average score) to your team’s channel. How to set up Connect Google Sheets and Slack credentials in n8n. Replace placeholders (<YOURSPREADSHEETID>, <YOURSHEETGIDORNAME>, <YOURSLACKCHANNEL_ID>). Adjust the AI review prompt or lint rules as needed. Activate the workflow — reviews will start automatically whenever new code is added to the sheet. Requirements Google Sheets and Slack integrations enabled A configured AI node (Gemini, OpenAI, or compatible) Proper permissions to write to your target Google Sheet How to customize Add more linting rules (naming conventions, spacing, forbidden APIs) Extend the AI prompt for project-specific guidelines Customize the Slack message formatting Export analytics to a dashboard (e.g., Notion or Data Studio) Why it’s valuable This workflow brings realistic, team-oriented AI-assisted code review to n8n — combining the speed of automated linting with the nuance of human-style feedback. It saves time, improves code quality, and keeps your team’s review history transparent and centralized.
🎓 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.