Skip to content
Notis

Reflect GitHub escalation labels in Linear priority

A label change often represents a real priority decision. Notis turns that signal into the matching Linear update so the team does not rely on someone noticing and repeating the decision elsewhere.

Trigger

GitHub Issue Labels Changed

Triggers when the labels on a specific GitHub issue change. Fires whenever a label is added to, removed from, or has its metadata (color, description) modified on the monitored issue. The payload includes: - ``current_labels`` -- the full set of labels currently on the issue - ``added_labels`` -- labels that were newly added - ``removed_label_names`` -- names of labels that were removed - ``changed_label_names`` -- labels whose metadata changed without being added or removed

Action

Update issue

Updates an existing linear issue using its `issue id`; requires at least one other attribute for modification, and all provided entity ids (for state, assignee, labels, etc.) must be valid.

Why this helps

An issue becomes urgent in GitHub but remains ordinary in Linear, creating two conflicting pictures of what deserves attention next.

  • Keeps escalation decisions consistent between intake and planning.
  • Responds to the specific added label rather than every metadata change.
  • Reduces manual triage maintenance after priorities have already been discussed.

Setup

Build it in a few focused steps.

  • 1Connect GitHub and Linear once in Notis.
  • 2Describe the outcome: 'If the escalation label is added to this GitHub issue, raise the linked Linear issue to urgent priority and note the GitHub link.'
  • 3Pick GitHub Issue Labels Changed as the trigger and select a run-report channel.
  • 4Add the escalation label to a test issue and verify the Linear priority changes.

Questions about this workflow

Can different GitHub labels set different priorities?

Yes. State the label-to-outcome rules in plain language, and Notis can apply the appropriate valid Linear priority to the linked issue.

What happens when unrelated labels change?

They can be ignored when your instruction names only the escalation labels that should cause a Linear update.

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.

TriggerPolling

Create linear attachment

Creates a new attachment and associates it with a specific, existing linear issue.

ActionInstant

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.

TriggerPolling

Create a comment

Creates a new comment on a specified linear issue.

ActionInstant

New Branch Created

Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.

TriggerPolling

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.

ActionInstant

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.

TriggerPolling

Get create issue default params

Fetches a linear team's default issue estimate and state, useful for pre-filling new issue forms.

ActionInstant

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.

TriggerPolling

Create a label

Creates a new label in linear for a specified team, used to categorize and organize issues.

ActionInstant

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.

TriggerPolling

Delete issue

Archives an existing linear issue by its id, which is linear's standard way of deleting issues; the operation is idempotent.

ActionInstant

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.

TriggerPolling

Get all teams

Retrieves all teams from the linear workspace without requiring any parameters.

ActionInstant

Commit Event

Triggered when a new commit is pushed to a repository.

TriggerInstant

Download issue attachments

Downloads a specific attachment from a linear issue; the `file name` must include the correct file extension.

ActionInstant

Connect any two apps with Notis in the middle.

Not just GitHub and Linear. Any combination from 1,000+ 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.