Spot Recurring Appveyor Failure Clues
Look across the build history available to Notis and bring repeat issues into one conversation.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Send Message
Send a text message to a telegram chat using the bot api.
Why this helps
The same failure can return across builds before anyone connects the pattern.
- Bring repeated failure clues into view on a schedule.
- Summarize patterns in the Appveyor history available to the check.
- Help the team focus follow-up on recurring issues.
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 tell Notis the outcome from any channel.
- 3In one instruction, ask Notis to review available Appveyor build history for recurring failure clues and summarize them in Telegram, noting any history limits.
- 4Choose notis_cron as the trigger and set a recurring schedule.
- 5Choose a report channel and test with one real review of available build history.
Questions about this workflow
Does Appveyor provide unlimited history for this review?
This workflow relies on history returned or otherwise available to the Appveyor check. The message should state limits if the available history does not cover the desired period.
Will it diagnose repeat failures?
It can highlight repeated clues in the available data, but those clues may need engineering investigation before they are treated as a diagnosis.
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.