Keep Telegram bot commands aligned with Backendless
Reduce bot maintenance by having Notis review the Backendless service information you specify and refresh the command list on a schedule.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Set Bot Commands
Use this method to change the list of the bot's commands. see https://core.telegram.org/bots#commands for more details about bot commands.
Why this helps
When service capabilities change, bot commands can become stale and require someone to remember a manual update.
- Keep a Telegram bot's command list aligned with supplied service information.
- Reduce forgotten manual command updates.
- Give users clearer entry points to supported actions.
Setup
Build it in a few focused steps.
- 1Connect Backendless and Telegram once in the Notis portal.
- 2Create an automation in Automations, or tell Notis what you want from any channel.
- 3Describe which Backendless service information to review and how to derive the Telegram bot commands.
- 4Choose a Notis schedule trigger and select where run reports should go.
- 5Test with one real service description and confirm the command list is accurate before relying on the schedule.
Questions about this workflow
Will Notis discover every available Backendless service automatically?
The automation can only use service information available through Backendless access and the context you provide. Specify the source and any details needed to form commands.
What Telegram action updates the commands?
It uses Set Bot Commands. The bot must be configured for the destination and the generated commands should be reviewed in your test.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Backendless to Telegram. A trigger fires from one place; an action lands in another.
Backendless 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.
Backendless 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.