Monthly Backlog Sync and Team Review
First day of the month? All your Notion changes sync to Linear automatically, and your team gets a summary for planning.
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
Monthly planning is chaotic. You accumulate ideas in Notion for a month, and team doesn't know what's coming. No one sees the full backlog until the last minute. Planning rush creates mistakes.
- Predictable ritual: monthly sync keeps planning on track
- Full visibility: team sees entire month's accumulated work
- Batch processing: accumulate ideas all month, sync once
- Planning prep: team has visibility ahead of planning meeting
Setup
Build it in a few focused steps.
- 1Connect Notion and Linear to Notis.
- 2Ask Notis: 'On the first of each month at 9 AM, sync all new or updated Notion tasks to Linear and send me a summary.'
- 3Notis will confirm the schedule and ask for the Notion database to monitor.
- 4Choose Linear project and summary recipients (email, Slack, etc.).
- 5On the first of the month, verify the sync runs and summary is generated.
Questions about this workflow
Can I change the frequency from monthly to something else (e.g., quarterly)?
Yes. Choose the schedule that fits your planning cycle.
What does the summary include?
Notis lists all new tasks, updated tasks, key changes, and metrics (count of new tasks, changes, etc.).
Does this include tasks that were synced previously?
No. Notis tracks what's been synced and only includes new or recently updated items.
Can I manually trigger the monthly sync outside the scheduled time?
Yes. Ask Notis to run it immediately if you need an on-demand review.
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
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create linear attachment
Creates a new attachment and associates it with a specific, existing linear issue.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create a comment
Creates a new comment on a specified linear issue.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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.
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.
Get create issue default params
Fetches a linear team's default issue estimate and state, useful for pre-filling new issue forms.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Create a label
Creates a new label in linear for a specified team, used to categorize and organize issues.
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.
Delete issue
Archives an existing linear issue by its id, which is linear's standard way of deleting issues; the operation is idempotent.
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.
Get all teams
Retrieves all teams from the linear workspace without requiring any parameters.
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.
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.
Notion and Linear, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Linear.