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

Batch Upload to Qdrant Crop Dataset

Batch Upload to Qdrant Crop Dataset is a 13-node automation blueprint connecting Google Cloud Storage, Qdrant. Inspect its trigger, execution graph, branches, and implementation requirements.

Google Cloud StorageQdrant

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.

13

Nodes

13

Links

1

Run groups

Connected tools

2 integrations

  • Google Cloud Storage
  • Qdrant

Canvas controls

Fit wide systems, then zoom into any run group.

Batch Upload to Qdrant Crop Dataset execution lanes1 run groups containing 13 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.When clicking ‘Test workflow’. trigger node, manualTrigger. 0 incoming and 1 outgoing connections.STARTWhen clicking ‘Test workf…TRIGGERMANUALTRIGGER0 IN / 1 OUTQdrant cluster variables. transform node, set. 1 incoming and 1 outgoing connections.STEP 02Qdrant cluster variablesTRANSFORMSET1 IN / 1 OUTCheck Qdrant Collection Existence. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 03Check Qdrant Collection E…INTEGRATIONHTTPREQUEST1 IN / 1 OUTIf collection exists. decision node, if. 1 incoming and 2 outgoing connections.STEP 04If collection existsDECISIONIF1 IN / 2 OUTCreate Qdrant Collection. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 05Create Qdrant CollectionINTEGRATIONHTTPREQUEST1 IN / 1 OUTPayload index on crop_name. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 06Payload index on crop_nameINTEGRATIONHTTPREQUEST1 IN / 1 OUTGoogle Cloud Storage. integration node, googleCloudStorage. 2 incoming and 1 outgoing connections.STEP 07Google Cloud StorageINTEGRATIONGOOGLECLOUDSTORAGE2 IN / 1 OUTGet fields for Qdrant. transform node, set. 1 incoming and 1 outgoing connections.STEP 08Get fields for QdrantTRANSFORMSET1 IN / 1 OUTFiltering out tomato to test anomalies. decision node, filter. 1 incoming and 1 outgoing connections.STEP 09Filtering out tomato to t…DECISIONFILTER1 IN / 1 OUTSplit in batches, generate uuids for Qdrant points. transform node, code. 1 incoming and 1 outgoing connections.STEP 10Split in batches, generat…TRANSFORMCODE1 IN / 1 OUTBatches in the API's format. transform node, set. 1 incoming and 1 outgoing connections.STEP 11Batches in the API's formatTRANSFORMSET1 IN / 1 OUTEmbed crop image. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 12Embed crop imageINTEGRATIONHTTPREQUEST1 IN / 1 OUTBatch Upload to Qdrant. integration node, httpRequest. 1 incoming and 0 outgoing connections.OUTCOMEBatch Upload to QdrantINTEGRATIONHTTPREQUEST1 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.13 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’

13 Execution Links

  1. Start

    When clicking ‘Test workflow’

    Trigger

  2. Step 2

    Qdrant cluster variables

    Transform

  3. Step 3

    Check Qdrant Collection Existence

    Integration

  4. Step 4

    If collection exists

    Decision

  5. Step 5

    Create Qdrant Collection

    Integration

  6. Step 6

    Payload index on crop_name

    Integration

  7. Step 7

    Google Cloud Storage

    Integration

  8. Step 8

    Get fields for Qdrant

    Transform

  9. Step 9

    Filtering out tomato to test anomalies

    Decision

  10. Step 10

    Split in batches, generate uuids for Qdrant points

    Transform

  11. Step 11

    Batches in the API's format

    Transform

  12. Step 12

    Embed crop image

    Integration

  13. Outcome

    Batch Upload to Qdrant

    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