Keep Linear issues current with Buildkite deployment updates
Put deployment progress beside the Linear work it affects, so people can see what shipped without chasing status in another tool.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create a comment
Creates a new comment on a specified linear issue.
Why this helps
Deployment status is easy to miss when updates live away from the issue tracking the work.
- Keep deployment updates with the associated issue.
- Reduce status pings and context switching.
- Make release progress easier to find later.
Setup
Build it in a few focused steps.
- 1Connect Buildkite and Linear once in the Notis portal.
- 2Create an automation in Automations, New Automation, or tell Notis in plain language from any channel.
- 3Describe that Notis should use each deployment notification to comment on the related Linear issue with available status and pipeline details.
- 4Choose a webhook trigger, then choose where run reports should go.
- 5Test with one real deployment notification and confirm the comment appears on the intended issue.
Questions about this workflow
How does Notis know which issue to comment on?
The webhook payload or accessible Buildkite data must identify the related Linear issue. If it does not, provide an issue identifier in the request or have Notis report that the association is missing.
Does this trigger directly from a Buildkite event?
Buildkite trigger events are not listed for this package. A Notis webhook starts the automation, and your Buildkite setup needs to send it an HTTP request.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Buildkite to Linear. A trigger fires from one place; an action lands in another.
Buildkite triggers
Linear actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create linear attachment
Creates a new attachment and associates it with a specific, existing linear issue.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create a comment
Creates a new comment on a specified linear issue.
Create linear issue
Creates a new issue in a specified linear project and team, requiring a title and description, and allowing for optional properties like assignee, state, priority, cycle, and due date.
Get create issue default params
Fetches a linear team's default issue estimate and state, useful for pre-filling new issue forms.
Create a label
Creates a new label in linear for a specified team, used to categorize and organize issues.
Delete issue
Archives an existing linear issue by its id, which is linear's standard way of deleting issues; the operation is idempotent.
Get all teams
Retrieves all teams from the linear workspace without requiring any parameters.
Download issue attachments
Downloads a specific attachment from a linear issue; the `file name` must include the correct file extension.
Connect any two apps with Notis in the middle.
Buildkite and Linear, 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 Linear.