Find unresolved Buildkite failures and give them an ownerable next step
A scheduled review can turn lingering Buildkite failures into Linear follow-up, helping prevent issues from being forgotten after the alert fades.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
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.
Why this helps
A failure may be noticed once and then forgotten while the team moves on to other work.
- Surface failures that still need attention.
- Create trackable work from available build history.
- Avoid repeatedly recreating follow-up for issues already represented in Linear.
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 review recent available Buildkite failures, check for existing Linear follow-up, and create issues only for unresolved failures without tracked work.
- 4Choose a recurring schedule, then choose where run reports should go.
- 5Test with one real failure and verify Notis distinguishes existing follow-up from a new item.
Questions about this workflow
How does Notis determine whether a failure is unresolved?
It can use status and history available through Buildkite and Linear. If the integrations do not expose enough history or issue linkage to establish that, provide the missing rule or have the automation report uncertainty.
Will it create duplicate issues on every run?
The instruction should ask Notis to check for existing related Linear issues before creating follow-up. Reliable deduplication depends on enough identifying Buildkite and Linear details being available.
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.