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

Video Intensity Analysis Workflow

Video Intensity Analysis Workflow is a 14-node automation blueprint connecting Intensity data API. Inspect its trigger, execution graph, branches, and implementation requirements.

Intensity data API

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

13

Links

1

Run groups

Connected tools

1 integrations

  • Intensity data API

Canvas controls

Fit wide systems, then zoom into any run group.

Video Intensity Analysis Workflow execution lanes1 run groups containing 14 workflow nodes and 13 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.Webhook. trigger node, webhook. 0 incoming and 1 outgoing connections.STARTWebhookTRIGGERWEBHOOK0 IN / 1 OUTInput variables. transform node, set. 1 incoming and 1 outgoing connections.STEP 02Input variablesTRANSFORMSET1 IN / 1 OUTHTTP Request. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 03HTTP RequestINTEGRATIONHTTPREQUEST1 IN / 1 OUThas intensity data?. decision node, if. 1 incoming and 2 outgoing connections.STEP 04has intensity data?DECISIONIF1 IN / 2 OUTSplit Out. transform node, splitOut. 1 incoming and 1 outgoing connections.STEP 05Split OutTRANSFORMSPLITOUT1 IN / 1 OUTNo intensity data available for video. integration node, noOp. 1 incoming and 1 outgoing connections.STEP 05No intensity data availab…INTEGRATIONNOOP1 IN / 1 OUTintensity > 0.6. decision node, filter. 1 incoming and 1 outgoing connections.STEP 06intensity > 0.6DECISIONFILTER1 IN / 1 OUTRespond with "no results". trigger node, respondToWebhook. 1 incoming and 0 outgoing connections.STEP 06Respond with "no results"TRIGGERRESPONDTOWEBHOOK1 IN / 0 OUTmillisecs to seconds. transform node, set. 1 incoming and 1 outgoing connections.STEP 07millisecs to secondsTRANSFORMSET1 IN / 1 OUTFilter out moments close to each other. decision node, filter. 1 incoming and 1 outgoing connections.STEP 08Filter out moments close …DECISIONFILTER1 IN / 1 OUTCreate each moment (human readable). transform node, set. 1 incoming and 1 outgoing connections.STEP 09Create each moment (human…TRANSFORMSET1 IN / 1 OUTAggregate. transform node, aggregate. 1 incoming and 1 outgoing connections.STEP 10AggregateTRANSFORMAGGREGATE1 IN / 1 OUTprepare response. transform node, set. 1 incoming and 1 outgoing connections.STEP 11prepare responseTRANSFORMSET1 IN / 1 OUTRespond with moments. trigger node, respondToWebhook. 1 incoming and 0 outgoing connections.OUTCOMERespond with momentsTRIGGERRESPONDTOWEBHOOK1 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

Respond with moments

13 Execution Links

  1. Start

    Webhook

    Trigger

  2. Step 2

    Input variables

    Transform

  3. Step 3

    HTTP Request

    Integration

  4. Step 4

    has intensity data?

    Decision

  5. Step 5

    Split Out

    Transform

    No intensity data available for video

    Integration

  6. Step 6

    intensity > 0.6

    Decision

    Respond with "no results"

    Trigger

  7. Step 7

    millisecs to seconds

    Transform

  8. Step 8

    Filter out moments close to each other

    Decision

  9. Step 9

    Create each moment (human readable)

    Transform

  10. Step 10

    Aggregate

    Transform

  11. Step 11

    prepare response

    Transform

  12. Outcome

    Respond with moments

    Trigger

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