Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
Event-Driven AutomationIntermediate

GitHub Issue Auto-Assignment Workflow

GitHub Issue Auto-Assignment Workflow is a 10-node automation blueprint connecting GitHub. Inspect its trigger, execution graph, branches, and implementation requirements.

GitHub

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

9

Links

1

Run groups

Connected tools

1 integrations

  • GitHub

Canvas controls

Fit wide systems, then zoom into any run group.

GitHub Issue Auto-Assignment Workflow execution lanes1 run groups containing 10 workflow nodes and 9 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.Github Trigger1. GitHub node, githubTrigger. 0 incoming and 1 outgoing connections.STARTGithub Trigger1GITHUBGITHUBTRIGGER0 IN / 1 OUTSwitch. decision node, switch. 1 incoming and 2 outgoing connections.STEP 02SwitchDECISIONSWITCH1 IN / 2 OUTIF no assignee?. decision node, if. 1 incoming and 2 outgoing connections.STEP 03IF no assignee?DECISIONIF1 IN / 2 OUTIF wants to work?. decision node, if. 1 incoming and 2 outgoing connections.STEP 03IF wants to work?DECISIONIF1 IN / 2 OUTAssign Issue Creator. GitHub node, github. 1 incoming and 0 outgoing connections.STEP 04Assign Issue CreatorGITHUBGITHUB1 IN / 0 OUTNoOp. integration node, noOp. 1 incoming and 0 outgoing connections.STEP 04NoOpINTEGRATIONNOOP1 IN / 0 OUTIF not assigned?. decision node, if. 1 incoming and 2 outgoing connections.STEP 04IF not assigned?DECISIONIF1 IN / 2 OUTNoOp1. integration node, noOp. 1 incoming and 0 outgoing connections.STEP 04NoOp1INTEGRATIONNOOP1 IN / 0 OUTAssign Commenter. GitHub node, github. 1 incoming and 0 outgoing connections.OUTCOMEAssign CommenterGITHUBGITHUB1 IN / 0 OUTAdd Comment. GitHub node, github. 1 incoming and 0 outgoing connections.OUTCOMEAdd CommentGITHUBGITHUB1 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

Github Trigger1

9 Execution Links

  1. Start

    Github Trigger1

    Trigger

  2. Step 2

    Switch

    Decision

  3. Step 3

    IF no assignee?

    Decision

    IF wants to work?

    Decision

  4. Step 4

    Assign Issue Creator

    Integration

    NoOp

    Integration

    IF not assigned?

    Decision

    NoOp1

    Integration

  5. Outcome

    Assign Commenter

    Integration

    Add Comment

    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