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

Crop Anomaly Detection Workflow

Crop Anomaly Detection Workflow is a 9-node automation blueprint connecting Qdrant API. Inspect its trigger, execution graph, branches, and implementation requirements.

Qdrant 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.

9

Nodes

8

Links

1

Run groups

Connected tools

1 integrations

  • Qdrant API

Canvas controls

Fit wide systems, then zoom into any run group.

Crop Anomaly Detection Workflow execution lanes1 run groups containing 9 workflow nodes and 8 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.Execute Workflow Trigger. trigger node, executeWorkflowTrigger. 0 incoming and 1 outgoing connections.STARTExecute Workflow TriggerTRIGGEREXECUTEWORKFLOWTRIGGER0 IN / 1 OUTImage URL hardcode. transform node, set. 1 incoming and 1 outgoing connections.STEP 02Image URL hardcodeTRANSFORMSET1 IN / 1 OUTVariables for medoids. transform node, set. 1 incoming and 1 outgoing connections.STEP 03Variables for medoidsTRANSFORMSET1 IN / 1 OUTTotal Points in Collection. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 04Total Points in CollectionINTEGRATIONHTTPREQUEST1 IN / 1 OUTEach Crop Counts. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 05Each Crop CountsINTEGRATIONHTTPREQUEST1 IN / 1 OUTInfo About Crop Labeled Clusters. transform node, set. 1 incoming and 1 outgoing connections.STEP 06Info About Crop Labeled C…TRANSFORMSET1 IN / 1 OUTEmbed image. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 07Embed imageINTEGRATIONHTTPREQUEST1 IN / 1 OUTGet similarity of medoids. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 08Get similarity of medoidsINTEGRATIONHTTPREQUEST1 IN / 1 OUTCompare scores. transform node, code. 1 incoming and 0 outgoing connections.OUTCOMECompare scoresTRANSFORMCODE1 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.9 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

Execute Workflow Trigger

8 Execution Links

  1. Start

    Execute Workflow Trigger

    Trigger

  2. Step 2

    Image URL hardcode

    Transform

  3. Step 3

    Variables for medoids

    Transform

  4. Step 4

    Total Points in Collection

    Integration

  5. Step 5

    Each Crop Counts

    Integration

  6. Step 6

    Info About Crop Labeled Clusters

    Transform

  7. Step 7

    Embed image

    Integration

  8. Step 8

    Get similarity of medoids

    Integration

  9. Outcome

    Compare scores

    Transform

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