Make speaker removal depend on a clear Telegram confirmation
When a speaker must be removed, use a deliberate confirmation signal and a confirmed speaker ID so the action has clear context.
Trigger
Callback Query Received
Triggered when a user taps an inline keyboard button attached to one of your bot's messages.
Action
Delete Speaker
Tool to delete a speaker by their id. use when you need to remove a speaker after confirming their id.
Why this helps
A removal request can be ambiguous or easy to misread when buried in a fast-moving chat.
- Require a deliberate confirmation tap before deletion.
- Tie the action to a specific speaker ID and event context.
- Reduce the chance of acting on an ambiguous message.
Setup
Build it in a few focused steps.
- 1Connect Telegram and Eventee to Notis once in the portal.
- 2Create an automation in the portal or ask Notis to delete a speaker only after the designated confirmation and verification of the speaker ID.
- 3Select Telegram Callback Query Received as the trigger.
- 4Choose a channel for run reports and test with a safe, authorized example where the speaker ID is confirmed.
Questions about this workflow
Can Notis guess which speaker to delete?
No. The instruction should require the exact confirmed speaker ID and skip the action when identity is uncertain.
Should a casual message trigger deletion?
No. Use the designated confirmation tap and an authorized request as conditions in the prompt.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Telegram to Eventee. A trigger fires from one place; an action lands in another.
Telegram triggers
Eventee actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add speaker
Tool to add a new speaker to a specific eventee event. use after creating an event and obtaining its id.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Speaker
Tool to delete a speaker by their id. use when you need to remove a speaker after confirming their id.
New Message Received
Triggered when your bot receives a new message in a private chat, group, or supergroup. To receive every message in a group, Privacy Mode must be disabled for the bot in BotFather.
List Events
Tool to retrieve a list of all events. use when you need an overview of all events.
New Channel Post
Triggered when a new post is published to a channel where your bot is an administrator.
Callback Query Received
Triggered when a user taps an inline keyboard button attached to one of your bot's messages.
Message Edited
Triggered when a message in a chat your bot can see is edited by its sender.
New Chat Member
Triggered when a new member joins a group or supergroup the bot belongs to, including when the bot itself is added.
Connect any two apps with Notis in the middle.
Telegram and Eventee, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Eventee.