Clean up mismatched GitHub and Linear issue states each week
Even good event automations can meet legacy records or unusual edge cases. Notis performs a calm weekly reconciliation, updates only clear mismatches, and reports what changed for review.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Run Query or Mutation
Wildcard action that executes any graphql query or mutation against the linear api. use this as a fallback when no specific action exists for your use case, or when you need to perform complex operations not covered by other linear actions. supports full graphql capabilities including custom queries, mutations, and advanced filtering.
Why this helps
Small status inconsistencies accumulate until the board requires an exhausting manual cleanup, making every planning view harder to trust in the meantime.
- Catches older or exceptional mismatches that event-driven workflows did not resolve.
- Updates only issues with a clear directional link and state discrepancy.
- Provides one scheduled report instead of requiring an open-ended manual audit.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Linear to Notis once.
- 2Tell Notis: 'Every Friday, compare linked open GitHub and Linear issues, correct clear Linear state mismatches, and report any ambiguous records without changing them.'
- 3Choose a weekly recurring trigger and select the channel for the reconciliation report.
- 4Run it once on a small set of test issues and review every proposed or completed update.
Questions about this workflow
Will Notis change issues when the match is uncertain?
Your instruction can require a clear identifier match and ask Notis to report ambiguous records without modifying them.
Why use a schedule instead of an issue event?
The schedule provides a safety net for legacy records, missed events, and edge cases while the event workflows handle normal changes immediately.
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
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.
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 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.
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.
Get create issue default params
Fetches a linear team's default issue estimate and state, useful for pre-filling new issue forms.
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 a label
Creates a new label in linear for a specified team, used to categorize and organize issues.
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.
Delete issue
Archives an existing linear issue by its id, which is linear's standard way of deleting issues; the operation is idempotent.
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.
Get all teams
Retrieves all teams from the linear workspace without requiring any parameters.
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.
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.
GitHub 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.