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

Follower Image Processor

Follower Image Processor is a 12-node automation blueprint connecting Follower data API, Image storage API. Inspect its trigger, execution graph, branches, and implementation requirements.

Follower data APIImage storage 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.

12

Nodes

11

Links

1

Run groups

Connected tools

2 integrations

  • Follower data API
  • Image storage API

Canvas controls

Fit wide systems, then zoom into any run group.

Follower Image Processor execution lanes1 run groups containing 12 workflow nodes and 11 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.Fetch bg. integration node, httpRequest. 0 incoming and 1 outgoing connections.STARTFetch bgINTEGRATIONHTTPREQUEST0 IN / 1 OUTOn clicking 'execute'. trigger node, manualTrigger. 0 incoming and 1 outgoing connections.STARTOn clicking 'execute'TRIGGERMANUALTRIGGER0 IN / 1 OUTFetch new followers. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 02Fetch new followersINTEGRATIONHTTPREQUEST1 IN / 1 OUTItem Lists. transform node, itemLists. 1 incoming and 1 outgoing connections.STEP 03Item ListsTRANSFORMITEMLISTS1 IN / 1 OUTFetching images. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 04Fetching imagesINTEGRATIONHTTPREQUEST1 IN / 1 OUTResize. integration node, editImage. 1 incoming and 1 outgoing connections.STEP 05ResizeINTEGRATIONEDITIMAGE1 IN / 1 OUTCrop. integration node, editImage. 1 incoming and 1 outgoing connections.STEP 06CropINTEGRATIONEDITIMAGE1 IN / 1 OUTResize1. integration node, editImage. 1 incoming and 1 outgoing connections.STEP 07Resize1INTEGRATIONEDITIMAGE1 IN / 1 OUTFunction. transform node, function. 1 incoming and 1 outgoing connections.STEP 08FunctionTRANSFORMFUNCTION1 IN / 1 OUTMerge. decision node, merge. 2 incoming and 1 outgoing connections.STEP 09MergeDECISIONMERGE2 IN / 1 OUTEdit Image. integration node, editImage. 1 incoming and 1 outgoing connections.STEP 10Edit ImageINTEGRATIONEDITIMAGE1 IN / 1 OUTHTTP Request. integration node, httpRequest. 1 incoming and 0 outgoing connections.OUTCOMEHTTP RequestINTEGRATIONHTTPREQUEST1 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.12 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'

11 Execution Links

  1. Start

    Fetch bg

    Integration

    On clicking 'execute'

    Trigger

  2. Step 2

    Fetch new followers

    Integration

  3. Step 3

    Item Lists

    Transform

  4. Step 4

    Fetching images

    Integration

  5. Step 5

    Resize

    Integration

  6. Step 6

    Crop

    Integration

  7. Step 7

    Resize1

    Integration

  8. Step 8

    Function

    Transform

  9. Step 9

    Merge

    Decision

  10. Step 10

    Edit Image

    Integration

  11. Outcome

    HTTP Request

    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