Create Linear Issues On-Demand Via Webhook
Send a webhook to Notis with task details, and it creates a Linear issue instantly. Perfect for custom scripts or third-party tools.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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
Sometimes you need to sync a Notion task manually, or you have a custom tool that needs to create Linear issues. Fixed automations don't fit every use case. You need flexibility.
- On-demand control: trigger syncs exactly when you need them
- Custom workflows: use Zapier, Make, or custom scripts to feed Notis
- Flexible data: send any task data in the webhook payload
- No polling needed: push-based integration is instant
Setup
Build it in a few focused steps.
- 1Connect Linear to Notis and ask for a webhook endpoint.
- 2Create the webhook receiver: 'Generate a webhook URL that creates a Linear issue when called.'
- 3Notis will provide a unique endpoint and explain the JSON payload structure.
- 4In Notion, Zapier, Make, or a custom script, configure a webhook POST to Notis's endpoint with task data.
- 5Test by sending a webhook and verifying the Linear issue is created.
Questions about this workflow
What data should I include in the webhook payload?
Notis will provide documentation showing required fields (title, description) and optional fields (priority, assignee, etc.). You send JSON data.
Can I use this from Zapier or Make instead of custom scripts?
Yes. Both support webhooks. You'd create a Zapier/Make workflow that sends data to Notis's webhook endpoint.
Is the webhook endpoint secure? Can anyone send data to it?
Notis provides a unique endpoint. You can configure additional security (API keys, IP whitelisting) if needed.
What happens if the webhook fails? Is there a retry mechanism?
Notis will return an error response. You handle retries on your end (Zapier and Make have built-in retry logic).
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.