Make cancellation follow-up a quick team decision
Bring a cancellation into Telegram with a simple poll that helps your team agree on what to do next.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Send Poll
Send a native poll to a telegram chat using the bot api.
Why this helps
Cancellation notices can prompt scattered discussion, leaving ownership and next steps unclear.
- Surface a cancellation in the team chat where follow-up can happen.
- Offer a short set of next-step choices in a native Telegram poll.
- Use cancellation context included in the webhook request to make the decision specific.
Setup
Build it in a few focused steps.
- 1Connect Billsby and Telegram once in the Notis portal.
- 2Create an automation named Billsby cancellation follow-up, from Automations, New Automation, or tell Notis to create it from any channel.
- 3In one instruction, ask Notis to create a Telegram poll when an incoming Billsby webhook reports a cancellation, summarizing the supplied context and offering relevant follow-up choices.
- 4Choose the Notis webhook trigger and the Telegram team chat; choose where run reports go.
- 5Send one real cancellation example to the webhook and review the poll and its options.
Questions about this workflow
Will this detect cancellations without a webhook request?
No. Billsby has no listed integration trigger here. A cancellation must be represented in a request sent to the Notis webhook.
Can the poll include a reason for cancellation?
Only when that reason is present in the request. Notis should avoid inventing a reason or customer context.
Can I change the poll choices?
Yes. Include the choices you want in the plain language instruction, or ask Notis to derive a short set of relevant next steps from the supplied cancellation details.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Billsby to Telegram. A trigger fires from one place; an action lands in another.
Billsby 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.
Billsby 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.