Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
Conditional AutomationBeginner

Close Date Management Workflow

Close Date Management Workflow is a 6-node automation blueprint. Inspect its trigger, execution graph, branches, and implementation requirements.

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.

6

Nodes

6

Links

1

Run groups

Canvas controls

Fit wide systems, then zoom into any run group.

Close Date Management Workflow execution lanes1 run groups containing 6 workflow nodes and 6 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.On clicking 'execute'. trigger node, manualTrigger. 0 incoming and 1 outgoing connections.STARTOn clicking 'execute'TRIGGERMANUALTRIGGER0 IN / 1 OUTSet Close Date. transform node, set. 1 incoming and 1 outgoing connections.STEP 02Set Close DateTRANSFORMSET1 IN / 1 OUTCheck for Close Date. decision node, if. 1 incoming and 2 outgoing connections.STEP 03Check for Close DateDECISIONIF1 IN / 2 OUTSet Close Date To Original. transform node, set. 1 incoming and 1 outgoing connections.STEP 04Set Close Date To OriginalTRANSFORMSET1 IN / 1 OUTSet Close Date 3 Weeks Later. transform node, set. 1 incoming and 1 outgoing connections.STEP 04Set Close Date 3 Weeks La…TRANSFORMSET1 IN / 1 OUTNoOp. integration node, noOp. 2 incoming and 0 outgoing connections.OUTCOMENoOpINTEGRATIONNOOP2 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.6 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

On clicking 'execute'

6 Execution Links

  1. Start

    On clicking 'execute'

    Trigger

  2. Step 2

    Set Close Date

    Transform

  3. Step 3

    Check for Close Date

    Decision

  4. Step 4

    Set Close Date To Original

    Transform

    Set Close Date 3 Weeks Later

    Transform

  5. Outcome

    NoOp

    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