See Your Deployed Projects at Sprint Planning Time
Planning a sprint without knowing which projects are deployed is guessing. Auto-fetch the full project list so you plan realistic work.
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
Switching between Linear and Appveyor during sprint planning breaks momentum. You commit to work without knowing deployment status.
- Plan sprints knowing what's actually deployed
- Avoid overcommitting to unrealistic scope
- Keep project visibility without tool-switching
Setup
Build it in a few focused steps.
- 1Ensure Appveyor is connected in Notis - one-time setup shared across all automations
- 2Tell Notis: 'When an issue is moved to a sprint, fetch all Appveyor projects and show me which are active'
- 3Select 'Issue Updated' as the trigger - fires when issue is assigned to sprint
- 4Pick your team channel for the project list
- 5Test by moving an issue to a sprint and verify the project list appears
Questions about this workflow
Why do I need the project list at sprint time?
It shows what's already live, what's staging, what needs deployment planning. This prevents overcommitting.
Can this reflect my branch strategy?
Yes. Mention your branching pattern when setting up and Notis will filter projects accordingly.
Does this slow down sprint planning?
No - the list appears in your channel while you're working. Zero manual effort.
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.