Build Artifact Details at Release Note Writing Time
Release notes aren't creative writing. Fetch artifacts automatically so you have dates, versions, and build numbers right there.
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
Writing release notes means context-switching to pull artifact details: build numbers, timestamps, build contents. This kills momentum on documentation.
- Draft release notes without leaving Linear
- Keep version accuracy with automatic pulls
- Reduce documentation time by 50%
Setup
Build it in a few focused steps.
- 1Verify Appveyor is connected to Notis
- 2Tell Notis: 'When I create an issue with release label, fetch all Appveyor build artifacts and list them'
- 3Select 'Issue Created' as the trigger
- 4Choose a documentation or releases channel
- 5Test by creating a release issue and check that artifacts appear with version details
Questions about this workflow
Should I list all artifacts or just the latest build?
Tell Notis what you prefer. Most teams want the last 5-10 builds for changelog reference.
Can Notis help format the release notes?
Notis fetches the data and organizes it. You write the text, but data gathering is automatic.
What if I need artifacts from a specific branch?
Mention the branch when setting up and Notis will fetch only from that branch.
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.