Create Linear tickets from Notion content
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
Nodes used (13)
- Loop Over Items (Split in Batches)
n8n-nodes-base.splitInBatches - GraphQL
n8n-nodes-base.graphql - Notion
n8n-nodes-base.notion - Aggregate
n8n-nodes-base.aggregate - Edit Fields (Set)
n8n-nodes-base.set - Linear
n8n-nodes-base.linear - Code
n8n-nodes-base.code - If
n8n-nodes-base.if - HTTP Request
n8n-nodes-base.httpRequest - OpenAI
@n8n/n8n-nodes-langchain.openAi - Filter
n8n-nodes-base.filter - n8n Form Trigger
n8n-nodes-base.formTrigger - Respond to Webhook
n8n-nodes-base.respondToWebhook
What it does
This workflow allows you to define multiple tickets/issues in a Notion page, then easily import them into Linear. Why is it useful? We use this workflow internally at n8n for collaboration between Product and Engineering teams: - Engineering needs all work to be in our ticketing system (Linear) in order to keep track of it - Product prefers to review features in Notion. This is because it and can be used to dump all your thoughts and organise them into themes afterwards, plus it better supports rich content like videos Features - Supports rich formatting (bullets, images, videos, links, etc.) - Keeps links between the Notion and Linear version, in case you need to refer back - Allows you to assign each issue to a team member in the Notion definition - Avoids importing the same issues twice if you run it again on the same page (meaning you can issues incrementally) You can see an example of the required format of the Notion page here.