Get Build Context on Critical Bug Reports
When a critical bug lands, you need to know what's deployed right now. Fetch artifacts automatically instead of juggling two tools.
Trigger
Issue Created Trigger
Triggered when a new issue is created.
Action
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.
Why this helps
Context-switching between Linear and CI/CD breaks focus during urgent bug response, losing momentum while hunting for build info.
- See what's deployed without switching apps
- Triage bugs faster with full build history
- Reduce cognitive load during urgent response
Setup
Build it in a few focused steps.
- 1Connect your Appveyor account to Notis via the portal - this one-time setup is reused by all automations
- 2Ask Notis in any channel: 'When a new issue with critical label is created, fetch the latest build artifacts from Appveyor'
- 3Notis will confirm the trigger - select 'Issue Created'
- 4Choose a Slack channel where Notis posts the artifact list
- 5Test by creating a critical issue and verify artifacts appear within seconds
Questions about this workflow
How does Notis know which artifacts matter?
Notis fetches recent artifacts for your projects. If you need specific branches or projects, mention that and Notis will filter.
Can multiple automations fire on the same trigger?
Yes. Each automation runs independently on that trigger without interfering.
What if we mark things critical that aren't deployments?
Use a more specific label combination like 'critical' + 'production' or ask Notis to trigger only when comments mention deploy or rollback.
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.