Skip to main content

Multi-channel task reminder system with Telegram, Email and Slack

Workflow preview

Workflow preview
100%
Multi-channel task reminder system with Telegram, Email and Slack preview
Open on n8n.io

Important notice

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

1. Workflow Overview

This n8n workflow automates task creation and scheduled reminders for users via a Telegram bot, ensuring timely notifications across multiple channels like email and Slack. It streamlines task mana...

Best for

  • Personal Productivity automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.webhook, n8n-nodes-base.stickynote, n8n-nodes-base.if, n8n-nodes-base.postgres, n8n-nodes-base.respondtowebhook, n8n-nodes-base.scheduletrigger, n8n-nodes-base.splitinbatches, n8n-nodes-base.switch

Source and attribution

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

Original n8n.io source

1.1 Workflow description

Title
Multi-channel task reminder system with Telegram, Email and Slack
Workflow name
Multi-channel task reminder system with Telegram, Email and Slack

This n8n workflow automates task creation and scheduled reminders for users via a Telegram bot, ensuring timely notifications across multiple channels like email and Slack. It streamlines task management by validating inputs, storing tasks securely, and delivering reminders while updating statuses for seamless follow-up.

Key Features

  • Enables users to create tasks directly in chat via webhook integration.
  • Triggers periodic checks for due tasks and processes them individually for accurate reminders.
  • Routes reminders to preferred channels (Telegram, email, or Slack) based on user settings.
  • Validates inputs, handles errors gracefully, and logs task data for persistence and auditing.

Workflow Process

  • The Webhook Entry Point node receives task creation requests from users via chat (e.g., Telegram bot), including details like user ID, task description, and channel preferences.
  • The Input Validation node checks for required fields (e.g., user ID, task description); if validation fails, it routes to the Error Response node.
  • The Save to Database node stores validated task data securely in a database (e.g., PostgreSQL, MongoDB, or MySQL) for persistence.
  • The Success Response node (part of Response Handlers) returns a confirmation message to the user in JSON format.
  • The Schedule Trigger node runs every 3 minutes to check for pending reminders (with a 5-minute buffer for every hour to avoid duplicates).
  • The Fetch Due Tasks node queries the database for tasks due within the check window (e.g., reminders set for within 3 minutes).
  • The Tasks Check node verifies if fetched tasks exist and are eligible for processing.
  • The Split Items node processes each due task individually to handle them in parallel without conflicts.
  • The Channel Router node directs reminders to the appropriate channel based on task settings (e.g., email, Slack, or Telegram).
  • The Email Sender node sends HTML-formatted reminder emails with task details and setup instructions.
  • The Slack Sender node delivers Slack messages using webhooks, including task formatting and user mentions.
  • The Telegram Sender node sends Telegram messages via bot API, including task ID, bot setup, and conversation starters.
  • The Update Task Status node marks the task as reminded in the database (e.g., updating status to "sent" with timestamp).
  • The Workflow Complete! node finalizes the process, logging completion and preparing for the next cycle.

Setup Instructions

  • Import the workflow into n8n and configure the Webhook Entry Point with your Telegram bot's webhook URL and authentication.
  • Set up database credentials in the Save to Database and Fetch Due Tasks nodes (e.g., connect to PostgreSQL or MongoDB).
  • Configure channel-specific credentials: Telegram bot token for Telegram Sender, email SMTP for Email Sender, and Slack webhook for Slack Sender.
  • Adjust the Schedule Trigger interval (e.g., every 3 minutes) and add any custom due-time logic in Fetch Due Tasks.
  • Test the workflow by sending a sample task creation request via the webhook and simulating due tasks to verify reminders and status updates.
  • Monitor executions in n8n dashboard and tweak validation rules or response formats as needed for your use case.

Prerequisites

  • Telegram bot setup with webhook integration for task creation and messaging.
  • Database service (e.g., PostgreSQL, MongoDB, or MySQL) for task storage and querying.
  • Email service (e.g., SMTP provider) and Slack workspace for multi-channel reminders.
  • n8n instance with webhook and scheduling enabled.
  • Basic API knowledge for bot configuration and channel routing.

Modification Options

  • Customize the Input Validation node to add fields like priority levels or recurring task flags.
  • Extend the Channel Router to include additional channels (e.g., Microsoft Teams or SMS via Twilio).
  • Modify the Schedule Trigger to use dynamic intervals based on task urgency or user preferences.
  • Enhance the Update Task Status node to trigger follow-up actions, like archiving completed tasks.
  • Adjust the Telegram Sender node for richer interactions, such as inline keyboards for task rescheduling.

Explore More AI Workflows: Get in touch with us for custom n8n automation!

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 - Webhook - Receive Task

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

Block 2 - Sticky Note

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

Block 3 - Validate Input

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

Block 4 - Sticky Note1

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

Block 5 - Save Task to Database

Type / Role
n8n-nodes-base.postgres - postgres
Config choices
Version 2.4

Block 6 - Sticky Note2

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

Block 7 - Success Response

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

Block 8 - Error Response

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

Block 9 - Sticky Note3

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

Block 10 - Schedule Trigger - Every 5 Minutes

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

Block 11 - Sticky Note4

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

Block 12 - Fetch Due Tasks

Type / Role
n8n-nodes-base.postgres - postgres
Config choices
Version 2.4

Block 13 - Sticky Note5

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

Block 14 - Check Tasks Exist

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

Block 15 - Sticky Note6

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

Block 16 - Split Into Items

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

Block 17 - Sticky Note7

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

Block 18 - Route by Channel

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

Block 19 - Sticky Note8

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

Block 20 - Send Email Reminder

Type / Role
n8n-nodes-base.emailSend - emailSend
Config choices
Version 2.1

Block 21 - Sticky Note9

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

Block 22 - Send Slack Reminder

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

Block 23 - Sticky Note10

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

Block 24 - Send Telegram Reminder

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

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

3. Summary Table

Workflow Multi-channel task reminder system with Telegram, Email and Slack
Complexity advanced
Nodes 27
Categories Personal Productivity
Author Oneclick AI Squad
Published 30 Oct 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/10345/10345.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

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

  4. 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. 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.

Frequently asked questions

What does Multi-channel task reminder system with Telegram, Email and Slack do?

This n8n workflow automates task creation and scheduled reminders for users via a Telegram bot, ensuring timely notifications across multiple channels like email and Slack. It streamlines task mana...

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 Personal Productivity use case.