Verify CI/CD Setup When You Create New Projects
New projects in Linear should have matching CI/CD pipelines. Fetch your project list automatically to catch missing pipeline setup before work starts.
Trigger
Project Created
Fires when a new Linear project is created. Covers projects in both public and private teams — polls with the connected user's token, so visibility matches what the connected user can see in Linear.
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
New projects in Linear often launch without matching CI/CD setup. This gap is discovered weeks later when deployment fails.
- Catch missing pipelines before work begins
- Reduce deployment surprises later
- Keep project setup consistent across tools
Setup
Build it in a few focused steps.
- 1Connect Appveyor to Notis
- 2Tell Notis: 'When a new project is created in Linear, fetch all Appveyor projects and show me which ones exist'
- 3Choose 'Project Created' as your trigger
- 4Select your engineering or devops channel
- 5Test by creating a new Linear project and verify the Appveyor project list appears
Questions about this workflow
Should I create the Appveyor project first or this automation?
Create Appveyor project first. This automation catches it immediately. If creating both, run this check and it shows the new project.
What if we use a naming convention?
Mention it. Notis can highlight matches or mismatches based on your pattern.
Can this prevent project creation without CI/CD?
Not directly, but seeing the gap makes it obvious and forces the conversation about pipeline setup.
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.