Verify Project Configuration When Builds Are Linked
Linking builds to issues should include verifying projects are properly set up. Fetch your project list to catch configuration gaps.
Trigger
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Action
Get Projects
Tool to get a list of all projects for the authenticated account. use after authentication to enumerate available projects.
Why this helps
Build tracking gets messy when projects aren't consistently configured. You link a build but don't notice missing integrations or wrong settings.
- Catch configuration issues early
- Keep builds linked to properly set up projects
- Maintain CI/CD consistency
Setup
Build it in a few focused steps.
- 1Connect Appveyor to Notis
- 2Ask Notis: 'When an issue is updated with a build link, fetch all Appveyor projects and highlight any configuration gaps'
- 3Select 'Issue Updated' as your trigger
- 4Pick your engineering channel
- 5Test by updating an issue with a build link and verify project list appears
Questions about this workflow
How does Notis know what a configuration gap is?
Tell Notis your standards. For example: flag projects without GitHub integration or projects not updated in 30 days.
What if a project looks correct but isn't?
The automation shows the full list. If something seems off, click through to Appveyor for detailed inspection.
Can this create missing projects?
No, this fetches existing projects. If a project is missing, create it in Appveyor and the next run will show it.
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.