Know when a Billsby payment needs follow-up
Put failed payment details in the Telegram chat where your team already coordinates recovery.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Send Message
Send a text message to a telegram chat using the bot api.
Why this helps
Payment failures can sit unnoticed when billing updates live in a separate dashboard.
- See payment failure details in Telegram as soon as the webhook request arrives.
- Keep customer and invoice context with the alert when Billsby includes it in the payload.
- Give your team one place to coordinate follow-up.
Setup
Build it in a few focused steps.
- 1Connect Billsby and Telegram once in the Notis portal.
- 2Create an automation named Billsby payment failure alert, from Automations, New Automation, or tell Notis to create it from any channel.
- 3In one instruction, ask Notis to send a concise Telegram message when an incoming Billsby webhook reports a failed payment, including customer and invoice details present in the request.
- 4Choose the Notis webhook trigger and the Telegram chat where the message should go; choose where run reports go.
- 5Send one real Billsby payment failure example to the webhook and review the Telegram message.
Questions about this workflow
Does Billsby have a built-in Notis trigger for this?
No Billsby trigger event is listed for this package. The automation starts when a Billsby webhook request reaches the Notis webhook trigger.
What details can the Telegram message include?
Notis can summarize details present in the incoming request, such as customer or invoice information. It cannot include fields that Billsby did not send.
What happens if the webhook payload is missing invoice details?
The message can report the failure with the details that are present. Ask Notis to say when key information is missing rather than guess.
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.