Keep Issue Priority in Sync Across Notion and Linear
Update priority once in Notion. Your Linear issue follows automatically. No more out-of-sync statuses that cause confusion.
Trigger
Page Properties Updated
Triggers when properties of a Notion page are updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.
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
Managing priorities across two systems leads to inconsistency. You change priority in Notion but forget to update Linear, leading to misaligned team expectations and wasted effort chasing down which tool has the truth.
- Single source of truth for priorities: change it once, sync everywhere
- Reduce status confusion: team always sees accurate priority in Linear
- Less re-context: stop checking which tool has the latest status
- Automatic sync: no manual updates or reminders needed
Setup
Build it in a few focused steps.
- 1Ensure your Notion workspace and Linear account are connected to Notis.
- 2Create the automation by telling Notis: 'Update the Linear issue priority whenever I change the priority field in my Notion task.'
- 3Notis will map your Notion priority levels (e.g., Low, Medium, High) to Linear priorities (Urgent, High, Medium, Low, No Priority).
- 4Select your notification channel for sync reports.
- 5Test by changing a task's priority in Notion and checking that the Linear issue updates within a minute.
Questions about this workflow
Can I use custom priority names in Notion?
Yes. When you set up the automation, tell Notis your priority labels (e.g., 'P0', 'P1', 'P2') and it will map them to Linear's priority scale.
What if I change priority directly in Linear? Will it sync back to Notion?
This workflow is one-way: Notion to Linear. To sync changes from Linear back to Notion, you'd create a separate automation.
Does this sync work for sub-tasks or only top-level tasks?
It works for any Notion page with a priority property, including nested pages and sub-tasks.
How often does the sync check for priority changes?
Notion notifies Notis immediately when you update a property. Linear is updated within seconds.
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.