Skip to content
Notis

Make Appveyor Incident Checks Easier to Start

Give your team clear bot shortcuts for the Appveyor checks they need during an incident.

Trigger

Webhook received

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

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

During an incident, remembering the right way to ask for build status or logs adds friction.

  • Make common Appveyor check requests discoverable.
  • Give teammates a consistent way to start a bot interaction.
  • Reduce prompt recall during incident response.

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 intended command update from any channel.
  • 3In one instruction, ask Notis to set Telegram bot commands that help teammates request Appveyor build status and available logs.
  • 4Choose notis_webhook as the trigger and have the relevant incident process call the endpoint when commands should be updated.
  • 5Choose a report channel and test the command list with one real bot configuration.

Questions about this workflow

Do these commands run Appveyor checks by themselves?

This action changes the Telegram bot command list. Separate automation behavior is needed to respond to command interactions and check Appveyor.

Can the workflow add commands to every bot?

It applies to the connected Telegram bot. Confirm that this is the bot your team uses.

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.

TriggerScheduled

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.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Delete Message

Delete a message, including service messages, with certain limitations.

ActionInstant

Edit Message

Edit text messages sent by the bot.

ActionInstant

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.

ActionInstant

Forward Message

Forward messages of any kind. service messages can't be forwarded.

ActionInstant

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.).

ActionInstant

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.

ActionInstant

Get Chat History

Get chat history messages. note: this uses the getupdates method with specific parameters to retrieve historical messages.

ActionInstant

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.