Close Linear Issues When Notion Tasks Complete

Mark done in Notion? The Linear issue closes automatically. No more ghost issues clogging your Linear workflow.

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.

Linear logo

Action

Delete issue

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

Why this helps

You finish a task and mark it done in Notion, but the Linear issue stays open. Your team thinks work is still in progress. Manually closing issues in Linear is friction you forget to do.

  • Automatic status sync: mark done once in Notion, Linear closes automatically
  • Clean workflow: no ghost open issues after work is done
  • Accurate burndown: Linear's open issues reflect actual work status
  • Less friction: no manual issue closing needed

Setup

Build it in a few focused steps.

  • 1Connect Notion and Linear to Notis.
  • 2Create the automation: 'When I mark a Notion task as done (or archive it), close the matching Linear issue.'
  • 3Notis will ask how you mark tasks complete in Notion (e.g., status field, specific label, or page archive).
  • 4Confirm the Linear status to use when closing (e.g., Done, Completed, Closed).
  • 5Test by marking a Notion task complete and verifying the Linear issue closes.

Questions about this workflow

What if the Linear issue is already in 'Done'? Will closing it move it elsewhere?

If the Linear issue is already done, this automation will set it to the confirmed closed status (often already done). No change if it's already there.

Can I configure which Notion status values trigger closure?

Yes. For example, 'Close the Linear issue if the Notion status is Done, Archived, or Deferred.' You set the mapping.

What if I reopen a task in Notion after closing it in Linear?

You can create a separate automation for that: 'If a Notion task is reopened, reopen the matching Linear issue.'

Does this work for subtasks too?

Yes. Any Notion page with a completion status can trigger the automation, including nested subtasks.

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 logo

Notion triggers

Linear logo

Linear actions

All Page Events

Triggers when any Notion page is created or updated across the workspace.

TriggerPolling

Create linear attachment

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

ActionInstant

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.

TriggerInstant

Create a comment

Creates a new comment on a specified linear issue.

ActionInstant

New Comment

Triggers when a new comment is added to a specified Notion block or page.

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

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.

TriggerInstant

Get create issue default params

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

ActionInstant

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.

TriggerInstant

Create a label

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

ActionInstant

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.

TriggerInstant

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 Page

Triggers when a new page is added to a Notion database.

TriggerPolling

Get all teams

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

ActionInstant

Page Added to Page

Fires when a new subpage (a `child_page` type block) is added under a specified parent Notion page.

TriggerPolling

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 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.