Keep Files in Sync Between Notion and Linear
Attach a file to a Notion task? It automatically attaches to the Linear issue too. Documentation stays together without duplication.
Trigger
Page Updated
Triggers when any block within a specified Notion page is updated.
Action
Create linear attachment
Creates a new attachment and associates it with a specific, existing linear issue.
Why this helps
You upload a screenshot or document to a Notion task for context, but the Linear issue doesn't have it. Teammates check Linear and have to ask for the file. Context gets fragmented.
- Unified documentation: files exist in both places without duplication
- Reduce context-switching: team finds all assets in Linear
- No manual re-uploads: Notis handles the attachment sync
- Better issue context: Linear issues have all supporting materials
Setup
Build it in a few focused steps.
- 1Connect Notion and Linear to Notis.
- 2Create the automation: 'When I attach a file to a Notion page, add it as an attachment to the matching Linear issue.'
- 3Notis will ask which Notion pages/database to monitor.
- 4Confirm the file types to sync (all, or specific extensions like images and PDFs).
- 5Test by attaching a file to a Notion page and verifying it appears in the Linear issue within a minute.
Questions about this workflow
What file types can be synced? Are there size limits?
Most common file types (images, PDFs, documents, spreadsheets) can sync. Linear's attachment limits apply (typically up to 10MB per file). Check Notis and Linear documentation for specific limits.
If I delete a file in Notion, is it removed from Linear?
No. Deleting a Notion attachment doesn't delete the Linear attachment. You can optionally configure Notis to remove it, but it's not automatic by default.
What if a Notion page has multiple attachments? Do they all sync?
Yes. All attachments on a Notion page sync to the matching Linear issue.
Can I filter which attachments sync (e.g., only images, not documents)?
Yes. You can configure file type filters or attachment name patterns.
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.