Confirm the Telegram Destination for Deployment Updates
Check the destination chat context as part of a deployment status workflow.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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
A correct CI update is less useful when posted into a chat whose current context is unclear.
- Retrieve current information about the intended Telegram chat.
- Add a context check to the deployment update process.
- Reduce confusion about where an update is being posted.
Setup
Build it in a few focused steps.
- 1Connect Appveyor and Telegram once in the Notis portal.
- 2Create an automation in Automations, New Automation, or describe the outcome to Notis from any channel.
- 3In one instruction, ask Notis to check the relevant Appveyor deployment, retrieve current Telegram chat information, and report both the status and chat context in Telegram.
- 4Choose notis_webhook as the trigger and arrange for the deployment process to call the endpoint.
- 5Choose a report channel and test with one real deployment and intended chat.
Questions about this workflow
Does chat info verify that a chat is the right destination?
It retrieves current chat details. Your instruction should compare those details with destination context you provide if a confirmation is needed.
Will it publish to a different chat automatically?
This workflow checks and reports chat information. Do not treat it as routing unless the intended destination is clearly supplied.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Appveyor to Telegram. A trigger fires from one place; an action lands in another.
Appveyor 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.
Appveyor 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.