Keep release planning supplied with an environment reference
A scheduled reference helps your team avoid restarting the same environment lookup whenever release planning comes around.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Get Environments
Tool to get a list of all deployment environments. use when you need to enumerate available environments before creating deployments.
Why this helps
Recurring release planning often repeats the same small information-gathering task before the real work can begin.
- Make environment discovery part of the planning rhythm.
- Reduce repeat lookups across release discussions.
- Keep the reference available in a familiar channel.
Setup
Build it in a few focused steps.
- 1Connect Telegram and Appveyor to Notis once in the portal.
- 2Create an automation through the portal or by asking Notis conversationally.
- 3Use one instruction to retrieve Appveyor environments and summarize them for release planning.
- 4Select a recurring schedule as the trigger and choose a channel for run reports.
- 5Test a manual run and confirm the scheduled message is useful to the team.
Questions about this workflow
Does the workflow deploy to an environment?
No. It only retrieves the environment list.
How often can it run?
Choose a recurring schedule that fits your team's planning cadence.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Telegram to Appveyor. A trigger fires from one place; an action lands in another.
Telegram triggers
Appveyor actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Build Artifacts
Tool to get the list of artifacts for a specific build job. use when you need to retrieve artifacts after a job completes.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Environments
Tool to get a list of all deployment environments. use when you need to enumerate available environments before creating deployments.
New Message Received
Triggered when your bot receives a new message in a private chat, group, or supergroup. To receive every message in a group, Privacy Mode must be disabled for the bot in BotFather.
Get Projects
Tool to get a list of all projects for the authenticated account. use after authentication to enumerate available projects.
New Channel Post
Triggered when a new post is published to a channel where your bot is an administrator.
Get Role
Tool to retrieve details of a specific role. use when you need to inspect permissions and metadata of a role by id.
Callback Query Received
Triggered when a user taps an inline keyboard button attached to one of your bot's messages.
Get Roles
Tool to retrieve all roles in the account. use when you need to enumerate available roles before assigning permissions.
Message Edited
Triggered when a message in a chat your bot can see is edited by its sender.
Get Users
Tool to retrieve all users in the account. use when you need to list all team users in your appveyor account.
New Chat Member
Triggered when a new member joins a group or supergroup the bot belongs to, including when the bot itself is added.
Connect any two apps with Notis in the middle.
Telegram and Appveyor, 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 Appveyor.