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

DingTalk PR Notification Workflow

DingTalk PR Notification Workflow is a 4-node automation blueprint connecting MySQL, DingTalk, TFS. Inspect its trigger, execution graph, branches, and implementation requirements.

MySQLDingTalkTFS

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.

4

Nodes

3

Links

1

Run groups

Connected tools

3 integrations

  • MySQL
  • DingTalk
  • TFS

Canvas controls

Fit wide systems, then zoom into any run group.

DingTalk PR Notification Workflow execution lanes1 run groups containing 4 workflow nodes and 3 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.ReceiveTfsPullRequestCreatedMessage. trigger node, webhook. 0 incoming and 1 outgoing connections.STARTReceiveTfsPullRequestCrea…TRIGGERWEBHOOK0 IN / 1 OUTLoadDingTalkAccountMap. MySQL node, mySql. 1 incoming and 1 outgoing connections.STEP 02LoadDingTalkAccountMapMYSQLMYSQL1 IN / 1 OUTBuildDingTalkWebHookData. transform node, code. 1 incoming and 1 outgoing connections.STEP 03BuildDingTalkWebHookDataTRANSFORMCODE1 IN / 1 OUTSendDingTalkMessageViaWebHook. integration node, httpRequest. 1 incoming and 0 outgoing connections.OUTCOMESendDingTalkMessageViaWeb…INTEGRATIONHTTPREQUEST1 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.4 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

ReceiveTfsPullRequestCreatedMe…

3 Execution Links

  1. Start

    ReceiveTfsPullRequestCreatedMessage

    Trigger

  2. Step 2

    LoadDingTalkAccountMap

    Integration

  3. Step 3

    BuildDingTalkWebHookData

    Transform

  4. Outcome

    SendDingTalkMessageViaWebHook

    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