Share Deployment Status Alongside a Location
Keep deployment coordination and a supplied map point together in the Telegram conversation.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Send Location
Send point on the map location to a telegram chat using the bot api.
Why this helps
Teams coordinating a location-based rollout can have status and site context in separate threads.
- Share a supplied location with a deployment status update.
- Keep rollout context in one chat.
- Avoid manually posting the map point separately.
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 result to Notis from any channel.
- 3In one instruction, ask Notis to check the relevant Appveyor deployment and send a location supplied in the request to Telegram with the returned status.
- 4Choose notis_webhook as the trigger and have the calling system provide the needed location and invoke the endpoint.
- 5Choose a report channel and test with one real deployment and supplied point.
Questions about this workflow
Does Appveyor provide geographic coordinates?
This workflow requires the location to be supplied by the calling system or user. Appveyor status alone does not imply a location.
Is this useful for every software deployment?
It is most useful when rollout coordination genuinely depends on a physical site or supplied map point.
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.