Automatically Set Up Linear Projects From Notion Databases
Create a new Notion database for a project? Linear project setup happens automatically. New projects stay consistent.
Trigger
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.
Action
Run Query or Mutation
Wildcard action that executes any graphql query or mutation against the linear api. use this as a fallback when no specific action exists for your use case, or when you need to perform complex operations not covered by other linear actions. supports full graphql capabilities including custom queries, mutations, and advanced filtering.
Why this helps
You create a new Notion database for a project, but have to manually set up a matching Linear project. Setup takes time and is inconsistent. Different projects have different structures in Linear.
- Automatic project creation: Linear project set up when Notion database is created
- Consistent structure: all projects follow the same template
- Faster setup: no manual Linear project configuration
- Sync from the start: project structures align from day one
Setup
Build it in a few focused steps.
- 1Connect Notion and Linear to Notis.
- 2Create the automation: 'When I create a new Notion database, create a matching Linear project with standard team and default settings.'
- 3Define your project template (default team, initial labels, states, cycles, etc.).
- 4Notis will map Notion database name to Linear project name.
- 5Test by creating a new Notion database and verifying the Linear project is created with expected structure.
Questions about this workflow
Can I customize the Linear project setup for different database types?
Yes. You can define multiple templates and tell Notis which template to use based on the database name or properties.
What Linear properties are automatically set up? Can I add more?
Notis sets up team, labels, and states based on your template. You can add custom fields to the automation prompt.
What if a Linear project with that name already exists?
Notis will either skip the creation or link to the existing project, depending on your configuration.
Can team members use this automation, or just the workspace admin?
Notis respects Linear permissions. Only users who can create projects will be able to trigger this automation.
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.