Confirm event updates are pointed at the right Telegram chat
Run a lightweight destination check before launch activity so renamed groups or changed usernames do not create confusion.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
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.).
Why this helps
Telegram groups can be renamed or reorganized, leaving event automations pointed at a destination the team no longer recognizes.
- Catch renamed or unexpected chat destinations
- Give operators a clear pre-launch verification
- Reduce misdirected event communication risk
Setup
Build it in a few focused steps.
- 1Connect Eventbrite and Telegram to Notis once in the portal.
- 2Ask Notis to verify the current Telegram chat information before selected Eventbrite campaign or event dates and report discrepancies.
- 3Choose a recurring pre-launch schedule and select a channel for run reports.
- 4Test with the real destination chat and confirm its current name and username are reported.
Questions about this workflow
Does this send an event announcement?
No. It retrieves current chat information so you can verify the destination before other communications run.
When should the check run?
Schedule it before campaign launches or major event dates, especially if your team frequently reorganizes chats.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Eventbrite to Telegram. A trigger fires from one place; an action lands in another.
Eventbrite triggers
Telegram actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Message
Delete a message, including service messages, with certain limitations.
Edit Message
Edit text messages sent by the bot.
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.
Forward Message
Forward messages of any kind. service messages can't be forwarded.
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.).
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.
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.
Eventbrite and Telegram, 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 Telegram.