Production Environment Details When You Need Them Most
Production incidents break context. Get your environment list in the same thread instead of switching tools while the team waits.
Trigger
Comment Received Trigger
Triggered when a comment is received.
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
Production emergencies happen in comment threads. You need environment info but retrieving it means abandoning the real-time discussion.
- Diagnose issues without leaving the conversation
- Keep the team synchronized in one thread
- Reduce resolution time by seconds that matter
Setup
Build it in a few focused steps.
- 1Connect Appveyor to Notis
- 2Ask Notis: 'When someone mentions production in a comment, fetch all Appveyor environments and post them to the thread'
- 3Select 'Comment Received' as the trigger
- 4Notis posts directly to the existing thread
- 5Test by commenting 'production issue' on any Linear issue and verify environment list appears in thread
Questions about this workflow
Won't this fire too often if we mention production casually?
Make it specific. Ask Notis to trigger only when 'production' is combined with 'down', 'error', or 'failed'.
Can this work in Slack too?
Yes. Notis can work across channels. Set it up for your #incidents Slack channel.
What if the environment list is long?
Notis posts the full list. For large teams, ask to summarize or show only prod and staging.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Appveyor. A trigger fires from one place; an action lands in another.
Linear 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.
Comment Received Trigger
Triggered when a comment is received.
Get Projects
Tool to get a list of all projects for the authenticated account. use after authentication to enumerate available projects.
Issue Created Trigger
Triggered when a new issue is created.
Get Role
Tool to retrieve details of a specific role. use when you need to inspect permissions and metadata of a role by id.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Get Roles
Tool to retrieve all roles in the account. use when you need to enumerate available roles before assigning permissions.
Private Team Comment Created
Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).
Get Users
Tool to retrieve all users in the account. use when you need to list all team users in your appveyor account.
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Connect any two apps with Notis in the middle.
Linear 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.