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

Auto Background Removal for Drive Images

Auto Background Removal for Drive Images is a 12-node automation blueprint connecting Google Drive, Background removal API. Inspect its trigger, execution graph, branches, and implementation requirements.

Google DriveBackground removal 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

14

Links

1

Run groups

Connected tools

2 integrations

  • Google Drive
  • Background removal API

Canvas controls

Fit wide systems, then zoom into any run group.

Auto Background Removal for Drive Images execution lanes1 run groups containing 12 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.Watch for new images. Google Drive node, googleDriveTrigger. 0 incoming and 2 outgoing connections.STARTWatch for new imagesGOOGLE DRIVEGOOGLEDRIVETRIGGER0 IN / 2 OUTDownload Image. Google Drive node, googleDrive. 1 incoming and 1 outgoing connections.STEP 02Download ImageGOOGLE DRIVEGOOGLEDRIVE1 IN / 1 OUTConfig. transform node, set. 1 incoming and 1 outgoing connections.STEP 02ConfigTRANSFORMSET1 IN / 1 OUTGet Image Size. integration node, editImage. 1 incoming and 1 outgoing connections.STEP 03Get Image SizeINTEGRATIONEDITIMAGE1 IN / 1 OUTSplit Out. transform node, splitOut. 1 incoming and 1 outgoing connections.STEP 04Split OutTRANSFORMSPLITOUT1 IN / 1 OUTMerge. decision node, merge. 2 incoming and 1 outgoing connections.STEP 05MergeDECISIONMERGE2 IN / 1 OUTloop all over your images. integration node, splitInBatches. 3 incoming and 1 outgoing connections.STEP 06loop all over your imagesINTEGRATIONSPLITINBATCHES3 IN / 1 OUTcheck which output size method is used. decision node, if. 1 incoming and 2 outgoing connections.STEP 07check which output size m…DECISIONIF1 IN / 2 OUTremove background fixed size. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 08remove background fixed s…INTEGRATIONHTTPREQUEST1 IN / 1 OUTremove background. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 09remove backgroundINTEGRATIONHTTPREQUEST1 IN / 1 OUTUpload Picture to Google Drive. Google Drive node, googleDrive. 1 incoming and 1 outgoing connections.STEP 10Upload Picture to Google …GOOGLE DRIVEGOOGLEDRIVE1 IN / 1 OUTUpload Picture to Google Drive1. Google Drive node, googleDrive. 1 incoming and 1 outgoing connections.OUTCOMEUpload Picture to Google …GOOGLE DRIVEGOOGLEDRIVE1 IN / 1 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

Watch for new images

14 Execution Links

  1. Start

    Watch for new images

    Trigger

  2. Step 2

    Download Image

    Integration

    Config

    Transform

  3. Step 3

    Get Image Size

    Integration

  4. Step 4

    Split Out

    Transform

  5. Step 5

    Merge

    Decision

  6. Step 6

    loop all over your images

    Integration

  7. Step 7

    check which output size method is used

    Decision

  8. Step 8

    remove background fixed size

    Integration

  9. Step 9

    remove background

    Integration

  10. Step 10

    Upload Picture to Google Drive

    Integration

  11. Outcome

    Upload Picture to Google Drive1

    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