Automated Weekly Backlog Sync From Notion to Linear
Every Monday morning, your entire new Notion backlog becomes Linear issues. Ritual replaces chaos, consistency replaces forgotten tasks.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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
Weekly planning feels impossible when you're juggling tasks across tools. You accumulate ideas in Notion all week, then either forget to sync them Friday, or spend an hour manually creating Linear issues. Either way, some tasks fall through the cracks.
- Ritual replaces chaos: every week at the same time, your backlog syncs
- Nothing falls through: structured review cycle catches all new tasks
- Team preparation: consistent Friday or Monday sync gives team time to plan
- Batch processing: single operation replaces constant manual entry
Setup
Build it in a few focused steps.
- 1Connect Notion and Linear to Notis.
- 2Ask Notis: 'Every Monday at 9 AM, create Linear issues for all new or updated tasks in my Notion backlog.'
- 3Notis will confirm the schedule and target Linear project.
- 4Optionally add filters (e.g., 'Only sync tasks marked Ready').
- 5On the first Monday, verify the backlog sync runs and creates the expected issues.
Questions about this workflow
Can I change the day or time of the weekly sync?
Yes. Coordinate with your team's planning rhythm (e.g., Friday before planning, Monday before standup).
What if I added a task on Friday that should already be included?
The sync looks back over the past week, so tasks added any day since the last run will be included.
Can I manually trigger the sync outside the scheduled time?
Yes. Ask Notis to run the sync immediately if you want an on-demand review.
How does this handle tasks that were synced last week and haven't changed?
Notis tracks what's been synced and only creates new issues for tasks added or updated since the last sync.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Linear. A trigger fires from one place; an action lands in another.
Notion triggers
Linear actions
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create linear attachment
Creates a new attachment and associates it with a specific, existing linear issue.
Comment Created
Triggers when a new comment is created in Notion. Optional `page_id` filter scopes to comments on a specific page. When omitted, fires for any new comment in the workspace the integration has access to. Requires the 'Read comments' capability on the Notion integration. If a connection was authorized before that capability was enabled, the user must re-authorize the connection for comment events to flow.
Create a comment
Creates a new comment on a specified linear issue.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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.
Database Created
Triggers when a new Notion database (the container) is created. A database is the post-2025-09-03 container that holds one or more data sources. This trigger fires for the container's creation event (`database.created`), distinct from `NOTION_DATASOURCE_CREATED` which fires when a new data source is added to an existing database. Most customers calling Notion's `POST /v1/databases` (the legacy API) or creating a database via the Notion UI will see this event. Adding a new data source to an existing database fires `data_source.created` instead — use `NOTION_DATASOURCE_CREATED` for that. Notion's payload puts `entity.type: "block"` (the container is a `child_database` block in the content tree) and `entity.id` is the database id.
Get create issue default params
Fetches a linear team's default issue estimate and state, useful for pre-filling new issue forms.
Data Source Created
Triggers when a new Notion data source is created. Fires workspace-wide. The payload's `data.parent` carries the data source's tree parent (typically the teamspace) for downstream filtering. A single template-based database creation can fire multiple `data_source.created` events at once — one per data source the template instantiates.
Create a label
Creates a new label in linear for a specified team, used to categorize and organize issues.
Data Source Schema Updated
Triggers when a Notion data source's schema is updated. Fires on column add / remove / rename. Payload includes `data.updated_properties: [{id, name, action}]` so consumers can discriminate the kind of change downstream. Optional `data_source_id` filter scopes to schema changes on a single data source. When omitted, fires for any schema change in the workspace the integration has access to. Note: adding a column also fires `page.properties_updated` once per existing row in the data source. Customers wanting a single structural-change signal should use this trigger.
Delete issue
Archives an existing linear issue by its id, which is linear's standard way of deleting issues; the operation is idempotent.
New Page
Triggers when a new page is added to a Notion database.
Get all teams
Retrieves all teams from the linear workspace without requiring any parameters.
Page Added to Page
Fires when a new subpage (a `child_page` type block) is added under a specified parent Notion page.
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 Notion 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.