Get a Daily Telegram Report of Blocked Notion Tasks
Blockers compound over time. Start each day by surfacing them in Telegram so your team can prioritize unblocking.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Send Message
Send a text message to a telegram chat using the bot api.
Why this helps
Tasks get marked Blocked in Notion but stay that way for days because no one sees them. Neurodivergent team members especially struggle to notice and act on invisible blockers.
- Surface blockers early each day so they don't fester
- Create accountability for unblocking through team visibility
- Reduce the cognitive load of hunting for blocked tasks
- Enable faster decision-making on what to unblock first
Setup
Build it in a few focused steps.
- 1Connect Notion and Telegram to Notis.
- 2Create an automation: 'Every weekday at 9 AM, send a Telegram message listing all tasks currently marked Blocked in Notion, with the person who reported the blocker and a brief note.'
- 3Select the trigger: 'Notis: Recurring Schedule' and set it to weekdays at 9 AM.
- 4Configure Telegram as your action and pick your team channel.
- 5Test by manually triggering the automation and verifying the blocked tasks list.
Questions about this workflow
How does Notis identify blocked tasks?
Your prompt should specify how you flag blockers. For example: 'Tasks with Status = Blocked' or 'Tasks in my Impediments database' and Notis will query accordingly.
Can the report prioritize blockers by severity?
Yes. Add to your prompt: 'Sort by urgency; show Critical blockers first, then High, then Medium' and Notis will order them.
What if I only want to see blockers assigned to me?
Refine your prompt: 'Only show blockers assigned to me' and Notis will filter to your tasks.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Telegram. A trigger fires from one place; an action lands in another.
Notion triggers
Telegram actions
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Answer Callback Query
Use this method to send answers to callback queries sent from inline keyboards. the answer will be displayed to the user as a notification at the top of the chat screen or as an alert.
Comment Created
Triggers when a new comment is created in Notion. Optional `page_id` filter scopes to comments on a specific page. When omitted, fires for any new comment in the workspace the integration has access to. Requires the 'Read comments' capability on the Notion integration. If a connection was authorized before that capability was enabled, the user must re-authorize the connection for comment events to flow.
Delete Message
Delete a message, including service messages, with certain limitations.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Edit Message
Edit text messages sent by the bot.
Database Created
Triggers when a new Notion database (the container) is created. A database is the post-2025-09-03 container that holds one or more data sources. This trigger fires for the container's creation event (`database.created`), distinct from `NOTION_DATASOURCE_CREATED` which fires when a new data source is added to an existing database. Most customers calling Notion's `POST /v1/databases` (the legacy API) or creating a database via the Notion UI will see this event. Adding a new data source to an existing database fires `data_source.created` instead — use `NOTION_DATASOURCE_CREATED` for that. Notion's payload puts `entity.type: "block"` (the container is a `child_database` block in the content tree) and `entity.id` is the database id.
Export Chat Invite Link
Generate a new primary invite link for a chat; any previously generated primary link is revoked. the bot must be an administrator in the chat for this to work and must have the appropriate administrator rights.
Data Source Created
Triggers when a new Notion data source is created. Fires workspace-wide. The payload's `data.parent` carries the data source's tree parent (typically the teamspace) for downstream filtering. A single template-based database creation can fire multiple `data_source.created` events at once — one per data source the template instantiates.
Forward Message
Forward messages of any kind. service messages can't be forwarded.
Data Source Schema Updated
Triggers when a Notion data source's schema is updated. Fires on column add / remove / rename. Payload includes `data.updated_properties: [{id, name, action}]` so consumers can discriminate the kind of change downstream. Optional `data_source_id` filter scopes to schema changes on a single data source. When omitted, fires for any schema change in the workspace the integration has access to. Note: adding a column also fires `page.properties_updated` once per existing row in the data source. Customers wanting a single structural-change signal should use this trigger.
Get Chat Info
Get up to date information about the chat (current name of the user for one-on-one conversations, current username of a user, group or channel, etc.).
New Page
Triggers when a new page is added to a Notion database.
Get Chat Administrators
Get a list of administrators in a chat. on success, returns an array of chatmember objects that contains information about all chat administrators except other bots.
Page Added to Page
Fires when a new subpage (a `child_page` type block) is added under a specified parent Notion page.
Get Chat History
Get chat history messages. note: this uses the getupdates method with specific parameters to retrieve historical messages.
Connect any two apps with Notis in the middle.
Not just Notion and Telegram. Any combination from 985+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Telegram.