Automatically sync GitHub issues to Linear
Stop duplicating issues across GitHub and Linear. Let Notis automatically create Linear issues whenever something new arrives on GitHub so you can manage everything from one place.
Trigger
New Issue Created
Triggers when a new issue is created in a GitHub repository. Pull requests are automatically excluded -- only true issues produce events. Results can be filtered by labels, assignee, creator, and mentioned user. The payload includes the issue number, title, body, state, labels, assignees, comment count, creator details, timestamps, and direct links to the issue on GitHub.
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
Neurodivergent founders often manage code in GitHub but track work in Linear. Manually creating matching issues in both systems creates cognitive overhead and inevitably leads to desynchronized data when some issues slip through the cracks.
- No manual issue creation saves context-switching
- Keep GitHub and Linear perfectly synchronized
- Never miss an issue that needs Linear tracking
- Eliminates duplicate data entry across systems
Setup
Build it in a few focused steps.
- 1Connect your GitHub and Linear accounts to Notis (one-time setup in the portal).
- 2Open Notis automation creation and describe: 'When a new GitHub issue arrives, create a matching issue in Linear with the same title and description.'
- 3Choose the channel where Notis reports each automation run (Telegram, email, etc.).
- 4Select the GitHub trigger: New Issue Created.
- 5Test with an actual new GitHub issue to verify the Linear issue appears correctly.
Questions about this workflow
Can I control which labels get added to the Linear issue?
Notis interprets your plain-language instruction, so you can include details like 'add the bug label if it's marked as a bug on GitHub' and Notis will apply them based on the incoming issue data.
What if the Linear issue already exists?
Notis will create a new issue unless you specifically tell it to check for duplicates in your prompt. You can customize this behavior in the automation setup.
Does this work for pull requests too?
This automation only triggers for issues. Pull requests are excluded automatically by the GitHub trigger. You can set up a separate automation for PRs if you need that.
Can I assign the Linear issue to a specific person?
Yes. Your plain-language prompt can include 'assign to me' or 'assign to [team member]' and Notis will handle it automatically based on the team structure you set up.
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.