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

GitHub Webhook Manager

GitHub Webhook Manager is a 13-node automation blueprint connecting GitHub, Slack, Telegram. Inspect its trigger, execution graph, branches, and implementation requirements.

GitHubSlackTelegram

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.

13

Nodes

9

Links

4

Run groups

Connected tools

3 integrations

  • GitHub
  • Slack
  • Telegram

Canvas controls

Fit wide systems, then zoom into any run group.

GitHub Webhook Manager execution lanes4 run groups containing 13 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.When clicking ‘Test workflow’. trigger node, manualTrigger. 0 incoming and 1 outgoing connections.STARTWhen clicking ‘Test workf…TRIGGERMANUALTRIGGER0 IN / 1 OUTRepos to Monitor. transform node, set. 1 incoming and 1 outgoing connections.STEP 02Repos to MonitorTRANSFORMSET1 IN / 1 OUTSplit Out. transform node, splitOut. 1 incoming and 1 outgoing connections.STEP 03Split OutTRANSFORMSPLITOUT1 IN / 1 OUTRegister Github Webhook. GitHub node, httpRequest. 1 incoming and 0 outgoing connections.OUTCOMERegister Github WebhookGITHUBHTTPREQUEST1 IN / 0 OUTRepos to Monitor1. transform node, set. 0 incoming and 1 outgoing connections.STARTRepos to Monitor1TRANSFORMSET0 IN / 1 OUTSplit Out1. transform node, splitOut. 1 incoming and 1 outgoing connections.STEP 02Split Out1TRANSFORMSPLITOUT1 IN / 1 OUTHook URL. transform node, set. 1 incoming and 1 outgoing connections.STEP 03Hook URLTRANSFORMSET1 IN / 1 OUTGet Existing Hook. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 04Get Existing HookINTEGRATIONHTTPREQUEST1 IN / 1 OUTDelete Github Webhook. GitHub node, httpRequest. 1 incoming and 0 outgoing connections.OUTCOMEDelete Github WebhookGITHUBHTTPREQUEST1 IN / 0 OUTNotify Slack. Slack node, slack. 0 incoming and 0 outgoing connections.CORE RUNTIMENotify SlackSLACKSLACK0 IN / 0 OUTWebhook Trigger. trigger node, webhook. 0 incoming and 1 outgoing connections.STARTWebhook TriggerTRIGGERWEBHOOK0 IN / 1 OUTFields. transform node, set. 1 incoming and 1 outgoing connections.STEP 02FieldsTRANSFORMSET1 IN / 1 OUTTelegram. Telegram node, telegram. 1 incoming and 0 outgoing connections.OUTCOMETelegramTELEGRAMTELEGRAM1 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.13 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

When clicking ‘Test workflow’

3 Execution Links

  1. Start

    When clicking ‘Test workflow’

    Trigger

  2. Step 2

    Repos to Monitor

    Transform

  3. Step 3

    Split Out

    Transform

  4. Outcome

    Register Github Webhook

    Integration

02

Run Group

Delete Github Webhook

4 Execution Links

  1. Start

    Repos to Monitor1

    Transform

  2. Step 2

    Split Out1

    Transform

  3. Step 3

    Hook URL

    Transform

  4. Step 4

    Get Existing Hook

    Integration

  5. Outcome

    Delete Github Webhook

    Integration

03

Run Group

Notify Slack

0 Execution Links

  1. Core Runtime

    Notify Slack

    Integration

04

Run Group

Webhook Trigger

2 Execution Links

  1. Start

    Webhook Trigger

    Trigger

  2. Step 2

    Fields

    Transform

  3. Outcome

    Telegram

    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