Daily Backlog Sync: Linear to GitHub
Every morning at 7 AM, Notis pulls all new Linear issues from yesterday and creates matching GitHub issues. Engineers start their day with a current view of all incoming work.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Add assignees to an issue
Adds or removes assignees for a github issue; changes are silently ignored if the authenticated user lacks push access to the repository.
Why this helps
New Linear issues created overnight or yesterday aren't in GitHub yet. Engineers start their day unaware of new work that's already in Linear, leading to duplicate prioritization discussions or missed context.
- Ensure new work appears in GitHub immediately without manual sync steps
- Give engineers a current view of incoming work each morning
- Reduce asynchronous coordination by syncing in batches at predictable times
- Create a structured handoff between planning (Linear) and execution (GitHub)
Setup
Build it in a few focused steps.
- 1Connect Linear and GitHub to Notis
- 2Create an automation: 'Every morning at 7 AM, sync all new Linear issues created since yesterday to GitHub'
- 3Customize scope: 'only sync issues marked Ready or higher priority' or 'sync issues from specific projects'
- 4Set notification to alert your engineering channel when daily sync completes
- 5Configure labels: 'add new-from-linear label to issues created by this sync'
- 6Test by creating a test Linear issue and verifying it syncs the next morning
Questions about this workflow
What if an issue is created in Linear after the morning sync?
It will be synced the next morning. For real-time sync, run the instant sync automation (when-issue-created) alongside this daily batch.
Can I customize the sync time?
Yes. Set it to whenever your team typically starts: 'sync at 8 AM Monday-Friday' or 'sync at 10 AM UTC'.
What if issues are created on weekends?
They'll be synced Monday morning. You can configure the automation to skip weekends: 'only sync on weekdays'.
Does this create duplicates if an issue was already synced?
No, Notis tracks synced issues and skips duplicates. It only creates new GitHub issues for Linear issues that haven't been synced yet.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to GitHub. A trigger fires from one place; an action lands in another.
Linear triggers
GitHub actions
Comment Received Trigger
Triggered when a comment is received.
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Issue Created Trigger
Triggered when a new issue is created.
List repositories starred by the authenticated user
Deprecated: lists repositories starred by the authenticated user, including star creation timestamps; use 'list repositories starred by the authenticated user' instead.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
List stargazers
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
Private Team Comment Created
Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).
Star a repository for the authenticated user
Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Add email for auth user
Adds one or more email addresses (which will be initially unverified) to the authenticated user's github account; use this to associate new emails, noting an email verified for another account will error, while an existing email for the current user is accepted.
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Add app access restrictions
Replaces github app access restrictions for an existing protected branch; requires a json array of app slugs in the request body, where apps must be installed and have 'contents' write permissions.
Project Created
Fires when a new Linear project is created. Covers projects in both public and private teams — polls with the connected user's token, so visibility matches what the connected user can see in Linear.
Add a repository collaborator
Adds a github user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and an invitation may be created or permissions updated directly.
Project Properties Updated
Fires when properties on a Linear project change (status, lead, target date, priority, etc.). Covers projects in both public and private teams — polls with the connected user's token.
Add a repository to an app installation
Adds a repository to a github app installation, granting the app access; requires authenticated user to have admin rights for the repository and access to the installation.
Connect any two apps with Notis in the middle.
Not just Linear and GitHub. 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 GitHub.