Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
ETL PipelineIntermediate

Monday.com Subitems and Pulses Automation

Monday.com Subitems and Pulses Automation is a 14-node automation blueprint connecting Monday.com API, HTTP Requests for custom API interactions. Inspect its trigger, execution graph, branches, and implementation requirements.

Monday.com APIHTTP Requests for custom API interactions

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.

14

Nodes

14

Links

1

Run groups

Connected tools

2 integrations

  • Monday.com API
  • HTTP Requests for custom API interactions

Canvas controls

Fit wide systems, then zoom into any run group.

Monday.com Subitems and Pulses Automation execution lanes1 run groups containing 14 workflow nodes and 14 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 OUTGET ITEM. integration node, mondayCom. 1 incoming and 6 outgoing connections.STEP 02GET ITEMINTEGRATIONMONDAYCOM1 IN / 6 OUTCOLUMN BY NAME. transform node, code. 1 incoming and 0 outgoing connections.STEP 03COLUMN BY NAMETRANSFORMCODE1 IN / 0 OUTCOLUMN BY ID. transform node, code. 1 incoming and 0 outgoing connections.STEP 03COLUMN BY IDTRANSFORMCODE1 IN / 0 OUTGET BOARD RELATION. transform node, code. 1 incoming and 1 outgoing connections.STEP 03GET BOARD RELATIONTRANSFORMCODE1 IN / 1 OUTPULL SUBITEMS. transform node, code. 1 incoming and 1 outgoing connections.STEP 03PULL SUBITEMSTRANSFORMCODE1 IN / 1 OUTConvert to File. integration node, convertToFile. 1 incoming and 1 outgoing connections.STEP 03Convert to FileINTEGRATIONCONVERTTOFILE1 IN / 1 OUTGET LINKEDPULSES. transform node, code. 1 incoming and 1 outgoing connections.STEP 04GET LINKEDPULSESTRANSFORMCODE1 IN / 1 OUTSPLIT SUBITEMS. transform node, splitOut. 1 incoming and 1 outgoing connections.STEP 04SPLIT SUBITEMSTRANSFORMSPLITOUT1 IN / 1 OUTMerge. decision node, merge. 2 incoming and 1 outgoing connections.STEP 04MergeDECISIONMERGE2 IN / 1 OUTSPLIT LINKED PULSES. transform node, splitOut. 1 incoming and 1 outgoing connections.STEP 05SPLIT LINKED PULSESTRANSFORMSPLITOUT1 IN / 1 OUTGET EACH SUBITEM. integration node, mondayCom. 1 incoming and 0 outgoing connections.STEP 05GET EACH SUBITEMINTEGRATIONMONDAYCOM1 IN / 0 OUTMONDAY UPLOAD. integration node, httpRequest. 1 incoming and 0 outgoing connections.STEP 05MONDAY UPLOADINTEGRATIONHTTPREQUEST1 IN / 0 OUTPULL LINKEDPULSE. integration node, mondayCom. 1 incoming and 0 outgoing connections.OUTCOMEPULL LINKEDPULSEINTEGRATIONMONDAYCOM1 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.14 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"

14 Execution Links

  1. Start

    When clicking "Test workflow"

    Trigger

  2. Step 2

    GET ITEM

    Integration

  3. Step 3

    COLUMN BY NAME

    Transform

    COLUMN BY ID

    Transform

    GET BOARD RELATION

    Transform

    PULL SUBITEMS

    Transform

    Convert to File

    Integration

  4. Step 4

    GET LINKEDPULSES

    Transform

    SPLIT SUBITEMS

    Transform

    Merge

    Decision

  5. Step 5

    SPLIT LINKED PULSES

    Transform

    GET EACH SUBITEM

    Integration

    MONDAY UPLOAD

    Integration

  6. Outcome

    PULL LINKEDPULSE

    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