Bring Appveyor Pipeline Context into the Incident Room
Keep the team focused by bringing build status and available clues into the incident conversation.
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
During an incident, switching between the response room and pipeline views makes coordination harder.
- Put returned pipeline context in the incident room.
- Keep response discussion close to relevant build details.
- Reduce repeated context switching during an incident.
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 incident update to Notis from any channel.
- 3In one instruction, ask Notis to check the relevant Appveyor pipeline and post the returned status plus useful available log clues to the Telegram incident room.
- 4Choose notis_webhook as the trigger and have the incident workflow call the endpoint.
- 5Choose a report channel and test with one real pipeline incident.
Questions about this workflow
Will it include full build logs in the room?
This workflow posts a concise message with useful available clues. For a full returned file, use a document sending action and ensure a file is available.
Does it open an incident or resolve one?
No. It shares Appveyor context in Telegram and does not manage incident state.
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.