Automatically track CI/CD failures in Linear
Failed workflows disappear into GitHub notifications while your team lives in Linear. Notis automatically creates a Linear issue the moment a workflow fails so the problem surfaces where decisions actually get made.
Trigger
GitHub Workflow Run State Changed
Triggers when a GitHub Actions workflow run's status or conclusion changes. Monitors a single workflow run and fires an event whenever it transitions between states (e.g., queued to in_progress, or in_progress to completed) or when its conclusion is set (e.g., success, failure, cancelled).
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
CI/CD failures are often discovered accidentally when someone checks GitHub, leading to delays in fixing broken builds. Neurodivergent founders need problems visible in their task system to stay on top of them. Silent CI failures create technical debt that compounds quickly.
- Failed builds get immediate visibility in Linear
- Team stays aligned on CI/CD issues without checking GitHub
- Reduce time-to-fix for broken builds
- Prevent technical debt from silently accumulating
Setup
Build it in a few focused steps.
- 1Connect GitHub and Linear to Notis.
- 2Create the automation: 'When a GitHub Actions workflow fails, create a high-priority Linear issue with the failure details.'
- 3Select an urgent notification channel.
- 4Choose the trigger: GitHub Workflow Run State Changed (filtered for failures).
- 5Test by intentionally failing a workflow and verify the Linear issue appears immediately.
Questions about this workflow
Can I only get alerts for specific workflows?
Yes. Your prompt can specify workflow names or patterns to monitor, e.g., 'only for the deploy workflow.'
Should I include the workflow logs in the Linear issue?
Notis can include error messages and a direct link to the workflow run for quick diagnosis.
What if the workflow fails repeatedly?
You can set up Notis to check for existing unresolved issues before creating duplicates, or create new ones if you prefer tracking each failure separately.
Can I auto-assign to the person who made the last commit?
Yes. Notis can extract the last committer and assign the Linear issue to them automatically.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Linear. A trigger fires from one place; an action lands in another.
GitHub triggers
Linear actions
New Workflow Artifact Created
Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artifacts.
Create linear attachment
Creates a new attachment and associates it with a specific, existing linear issue.
Branch Changed
Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.
Create a comment
Creates a new comment on a specified linear issue.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
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.
Check Run Status / Conclusion Changed
Triggers when a specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, in_progress, completed, etc.), conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required), started_at, and completed_at.
Get create issue default params
Fetches a linear team's default issue estimate and state, useful for pre-filling new issue forms.
Check Suite Status / Conclusion Changed
Triggers when a GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for changes to status (queued, in_progress, completed, etc.) and conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required, startup_failure, stale). Optionally filters by GitHub App ID.
Create a label
Creates a new label in linear for a specified team, used to categorize and organize issues.
New Code Scanning Alert Created
Triggers when a new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be filtered by Git reference, scanning tool, state, and severity. The payload includes the alert number, rule details, tool information, state, severity, and the location of the most recent instance.
Delete issue
Archives an existing linear issue by its id, which is linear's standard way of deleting issues; the operation is idempotent.
New Repository Collaborator Added
Triggers when a new collaborator is added to a GitHub repository. Monitors the full list of collaborators on a repository and fires an event for each newly added collaborator. The payload includes the collaborator's GitHub username, account ID, profile URL, avatar URL, permission flags (pull, triage, push, maintain, admin), and assigned role name.
Get all teams
Retrieves all teams from the linear workspace without requiring any parameters.
Commit Event
Triggered when a new commit is pushed to a repository.
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.
Not just GitHub and Linear. Any combination from 985+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Linear.