Skip to main content

Notion status-based alert messages (Slack, Telegram, WhatsApp, Discord, Email)

Workflow preview

Workflow preview
100%
Notion status-based alert messages (Slack, Telegram, WhatsApp, Discord, Email) preview
Open on n8n.io

Important notice

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

1. Workflow Overview

Notion Status Based Alert Template Who is this for? Teams that live in Notion and want an instant ping to the right person when a task changes state. Perfect for content creators, project managers,...

Best for

  • Project Management automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.emailsend, n8n-nodes-base.set, n8n-nodes-base.switch, n8n-nodes-base.slack, n8n-nodes-base.telegram, n8n-nodes-base.whatsapp, n8n-nodes-base.discord, n8n-nodes-base.notiontrigger

Source and attribution

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

Original n8n.io source

1.1 Workflow description

Title
Notion status-based alert messages (Slack, Telegram, WhatsApp, Discord, Email)
Workflow name
Notion status-based alert messages (Slack, Telegram, WhatsApp, Discord, Email)

Notion Status-Based Alert Template

Who is this for?

Teams that live in Notion and want an instant ping to the right person when a task changes state.
Perfect for content creators, project managers, or any small team that tracks work in a Notion database and prefers Slack / Telegram / Discord / e-mail notifications over manually checking a board.

What problem does this solve?

Polling Notion or checking a kanban board is slow and error-prone.
This workflow watches a Notion database and routes an alert to specific people based on the item’s Status. One central map decides who gets pinged for “On Deck”, “In Progress”, “Ready for Review”, or “Ready to Publish”.

How it works

  1. Trigger – choose either method
    • Polling (Notion Trigger) – fires every minute.
    • Push (Webhook) – register the production URL in a Notion automation and disable polling.
  2. Set Notion Page Info – copies Title, Status, URL, etc. into top-level fields.
  3. Switch (Status router) – routes the item down a branch that matches its Status.
  4. Set-Mention nodes – one per Status. Each node sets a single field mention (e.g. <@U123456>).
    Add or edit these nodes to map new statuses or recipients.
  5. Build Message – assembles a rich text block:
    Task title Status: <@UserIDs> <Notion URL|Open in Notion>
  6. Send nodes – Slack (active) + optional Telegram / WhatsApp / Discord / Email (disabled by default). All reuse the same {{$json.message}}.

Setup steps

  1. Import this template into n8n.
  2. Connect credentials
  • Notion API token
  • Slack OAuth (and any other channels you enable)
  1. Edit the Status → Mention map
  • Open each Set-Mention node and replace the placeholder with the real Slack ID / chat ID / phone / email.
  • Copy a node for every extra Status you use, wire it to a new Switch output, and update the value.
  1. Set environment variables (recommended)
  • NOTION_DB_ID, SLACK_CHANNEL, EMAIL_FROM, etc.
  1. Pick your trigger style
  • Keep polling enabled or disable it and enable the Webhook, then register the webhook URL in Notion.
  1. Test – change a task’s Status in Notion → watch Slack for the ping.

Example output

> Title: “Draft blog post – AI productivity”
> Status: Ready for Review
> Slack message:
> &gt; *Draft blog post – AI productivity* &gt; Status: Ready for Review &gt; &lt;@U789012&gt; &gt; &lt;https://www.notion.so/…|Open in Notion&gt; &gt;

Extending the flow

  • Wire additional channels after Build Message—they all consume the same {{$json.message}}.
  • Add richer logic (e.g. due-date reminders) in the Set Notion Page Info node.
  • Verify Notion webhook signatures in a Function node if you rely on push triggers.

This template is the leanest possible setup: one table of statuses → direct pings to the right people. Swap the IDs, flip on your favourite channels, and ship.

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 - Send Email

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

Block 2 - Set Notion Page Info

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

Block 3 - Build Message

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

Block 4 - Switch

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

Block 5 - Set On Deck

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

Block 6 - Set In Progress

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

Block 7 - Set Ready For Review

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

Block 8 - Set Ready To Publish

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

Block 9 - Send Slack Msg

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

Block 10 - Send Telegram Msg

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

Block 11 - Send WhatsApp Msg

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

Block 12 - Send Discord Msg

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

Block 13 - Notion Trigger (Polling)

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

Block 14 - Notion Trigger (Webhook)

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

Block 15 - Sticky Note

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

Block 16 - Sticky Note1

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

Block 17 - Sticky Note2

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

3. Summary Table

Workflow Notion status-based alert messages (Slack, Telegram, WhatsApp, Discord, Email)
Complexity advanced
Nodes 17
Categories Project Management
Author Matty Reed
Published 25 May 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/4386/4386.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 Notion status-based alert messages (Slack, Telegram, WhatsApp, Discord, Email) do?

Notion Status Based Alert Template Who is this for? Teams that live in Notion and want an instant ping to the right person when a task changes state. Perfect for content creators, project managers,...

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 Project Management use case.