Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
ETL PipelineAI systemIntermediate

Notion to Linear Issue Automation

Notion to Linear Issue Automation is a 19-node automation blueprint connecting Notion, Linear, OpenAI. Inspect its trigger, execution graph, branches, and implementation requirements.

NotionLinearOpenAI

Interactive system map

Follow the runtime. Inspect what supports it.

Solid horizontal paths show main-channel execution. Violet dependencies sit beneath the exact step they configure or empower.

19

Nodes

19

Links

1

Run groups

Connected tools

3 integrations

  • Notion
  • Linear
  • OpenAI

Canvas controls

Fit wide systems, then zoom into any run group.

Notion to Linear Issue Automation execution lanes1 run groups containing 19 workflow nodes and 19 visible links. Solid horizontal lines are main-channel runtime links. Violet dashed lines connect typed dependencies beneath the runtime step they support. Focus any node to inspect its immediate path.n8n Form Trigger. trigger node, formTrigger. 0 incoming and 1 outgoing connections.STARTn8n Form TriggerTRIGGERFORMTRIGGER0 IN / 1 OUTFetch Linear team details. integration node, graphql. 1 incoming and 1 outgoing connections.STEP 02Fetch Linear team detailsINTEGRATIONGRAPHQL1 IN / 1 OUTTeam missing?. decision node, if. 1 incoming and 2 outgoing connections.STEP 03Team missing?DECISIONIF1 IN / 2 OUTRespond with error1. trigger node, respondToWebhook. 1 incoming and 0 outgoing connections.STEP 04Respond with error1TRIGGERRESPONDTOWEBHOOK1 IN / 0 OUTSet team ID. transform node, set. 1 incoming and 1 outgoing connections.STEP 04Set team IDTRANSFORMSET1 IN / 1 OUTGet issues. Notion node, notion. 1 incoming and 2 outgoing connections.STEP 05Get issuesNOTIONNOTION1 IN / 2 OUTRespond with error. trigger node, respondToWebhook. 1 incoming and 0 outgoing connections.STEP 06Respond with errorTRIGGERRESPONDTOWEBHOOK1 IN / 0 OUTUnimported, unchecked to_do blocks only. decision node, filter. 1 incoming and 1 outgoing connections.STEP 06Unimported, unchecked to_…DECISIONFILTER1 IN / 1 OUTLoop Over Items. integration node, splitInBatches. 2 incoming and 1 outgoing connections.STEP 07Loop Over ItemsINTEGRATIONSPLITINBATCHES2 IN / 1 OUTSet assignee and title. transform node, code. 1 incoming and 1 outgoing connections.STEP 08Set assignee and titleTRANSFORMCODE1 IN / 1 OUTGet issue contents. Notion node, notion. 1 incoming and 1 outgoing connections.STEP 09Get issue contentsNOTIONNOTION1 IN / 1 OUTPrepare issue data. transform node, set. 1 incoming and 1 outgoing connections.STEP 10Prepare issue dataTRANSFORMSET1 IN / 1 OUTShorten title. OpenAI node, openAi. 1 incoming and 1 outgoing connections.STEP 11Shorten titleOPENAIOPENAI1 IN / 1 OUTSet page URL. transform node, set. 1 incoming and 1 outgoing connections.STEP 12Set page URLTRANSFORMSET1 IN / 1 OUTCreate linear issue. integration node, linear. 1 incoming and 1 outgoing connections.STEP 13Create linear issueINTEGRATIONLINEAR1 IN / 1 OUTConvert contents to Markdown. transform node, code. 1 incoming and 1 outgoing connections.STEP 14Convert contents to Markd…TRANSFORMCODE1 IN / 1 OUTGet issue URL. integration node, graphql. 1 incoming and 1 outgoing connections.STEP 15Get issue URLINTEGRATIONGRAPHQL1 IN / 1 OUTAggregate. transform node, aggregate. 1 incoming and 1 outgoing connections.STEP 16AggregateTRANSFORMAGGREGATE1 IN / 1 OUTAdd link to Notion block. Notion node, httpRequest. 1 incoming and 1 outgoing connections.OUTCOMEAdd link to Notion blockNOTIONHTTPREQUEST1 IN / 1 OUT

Signal inspector

Focus, hover, or select a step to isolate its runtime and support links.

Main-channel runtimeTyped dependencytriggeraidecisiontransformintegration
Scroll horizontally to follow every connected flow.19 connected nodesEnter or click to lock · Escape to clear

Runtime breakdown

Read the execution spine before its dependencies.

Each run group separates main-channel steps from the models, tools, retrievers, and data services that support them. Start and outcome labels apply only to runtime nodes.

01

Run Group

Respond with error1

19 Execution Links

  1. Start

    n8n Form Trigger

    Trigger

  2. Step 2

    Fetch Linear team details

    Integration

  3. Step 3

    Team missing?

    Decision

  4. Step 4

    Respond with error1

    Trigger

    Set team ID

    Transform

  5. Step 5

    Get issues

    Integration

  6. Step 6

    Respond with error

    Trigger

    Unimported, unchecked to_do blocks only

    Decision

  7. Step 7

    Loop Over Items

    Integration

  8. Step 8

    Set assignee and title

    Transform

  9. Step 9

    Get issue contents

    Integration

  10. Step 10

    Prepare issue data

    Transform

  11. Step 11

    Shorten title

    AI reasoning

  12. Step 12

    Set page URL

    Transform

  13. Step 13

    Create linear issue

    Integration

  14. Step 14

    Convert contents to Markdown

    Transform

  15. Step 15

    Get issue URL

    Integration

  16. Step 16

    Aggregate

    Transform

  17. Outcome

    Add link to Notion block

    Integration

Turn the map into a plan

Adapt this blueprint to your company.

Bring the system shape into a workspace, then define the production controls, data boundaries, owners, and delivery sequence around your context.

Create a build planReturn to the atlas