Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
Event-Driven AutomationAI systemIntermediate

Linear Ticket Classification and Notification

Linear Ticket Classification and Notification is a 10-node automation blueprint connecting Linear, Slack, OpenAI. Inspect its trigger, execution graph, branches, and implementation requirements.

LinearSlackOpenAI

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.

10

Nodes

10

Links

1

Run groups

Connected tools

3 integrations

  • Linear
  • Slack
  • OpenAI

Canvas controls

Fit wide systems, then zoom into any run group.

Linear Ticket Classification and Notification execution lanes1 run groups containing 10 workflow nodes and 10 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.Linear Trigger. trigger node, linearTrigger. 0 incoming and 1 outgoing connections.STARTLinear TriggerTRIGGERLINEARTRIGGER0 IN / 1 OUTSet me up. transform node, set. 1 incoming and 1 outgoing connections.STEP 02Set me upTRANSFORMSET1 IN / 1 OUTOnly tickets that need to be classified. decision node, filter. 1 incoming and 2 outgoing connections.STEP 03Only tickets that need to…DECISIONFILTER1 IN / 2 OUTOpenAI. OpenAI node, openAi. 1 incoming and 1 outgoing connections.STEP 04OpenAIOPENAIOPENAI1 IN / 1 OUTGet all linear teams. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 04Get all linear teamsINTEGRATIONHTTPREQUEST1 IN / 1 OUTMerge data. decision node, merge. 2 incoming and 1 outgoing connections.STEP 05Merge dataDECISIONMERGE2 IN / 1 OUTCheck if AI was able to find a team. decision node, if. 1 incoming and 2 outgoing connections.STEP 06Check if AI was able to f…DECISIONIF1 IN / 2 OUTSet team ID. transform node, set. 1 incoming and 1 outgoing connections.STEP 07Set team IDTRANSFORMSET1 IN / 1 OUTNotify in Slack. Slack node, slack. 1 incoming and 0 outgoing connections.STEP 07Notify in SlackSLACKSLACK1 IN / 0 OUTUpdate team. integration node, linear. 1 incoming and 0 outgoing connections.OUTCOMEUpdate teamINTEGRATIONLINEAR1 IN / 0 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.10 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

Linear Trigger

10 Execution Links

  1. Start

    Linear Trigger

    Trigger

  2. Step 2

    Set me up

    Transform

  3. Step 3

    Only tickets that need to be classified

    Decision

  4. Step 4

    OpenAI

    AI reasoning

    Get all linear teams

    Integration

  5. Step 5

    Merge data

    Decision

  6. Step 6

    Check if AI was able to find a team

    Decision

  7. Step 7

    Set team ID

    Transform

    Notify in Slack

    Integration

  8. Outcome

    Update team

    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