Skip to Workflow Atlas
ETL PipelineIntermediate

Automated Docx Image Replacement Workflow

Automated Docx Image Replacement Workflow is a 9-node automation blueprint connecting Google Drive, Custom HTTP API. Inspect its trigger, execution graph, branches, and implementation requirements.

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

2 integrations

  • Google Drive
  • Custom HTTP API

Canvas controls

Fit wide systems, then zoom into any run group.

Automated Docx Image Replacement 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.When clicking ‘Test workflow’. trigger node, manualTrigger. 0 incoming and 1 outgoing connections.STARTWhen clicking ‘Test workf…TRIGGERMANUALTRIGGER0 IN / 1 OUTOwn datasource. integration node, noOp. 1 incoming and 1 outgoing connections.STEP 02Own datasourceINTEGRATIONNOOP1 IN / 1 OUTImage URL. transform node, set. 1 incoming and 1 outgoing connections.STEP 03Image URLTRANSFORMSET1 IN / 1 OUTFind & Copy Docx Template. Google Drive node, googleDrive. 1 incoming and 1 outgoing connections.STEP 04Find & Copy Docx TemplateGOOGLE DRIVEGOOGLEDRIVE1 IN / 1 OUTFind Image ID in Docx. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 05Find Image ID in DocxINTEGRATIONHTTPREQUEST1 IN / 1 OUTReplace Image in Docx. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 06Replace Image in DocxINTEGRATIONHTTPREQUEST1 IN / 1 OUTMake file shareable publically (optional). Google Drive node, googleDrive. 1 incoming and 1 outgoing connections.STEP 07Make file shareable publi…GOOGLE DRIVEGOOGLEDRIVE1 IN / 1 OUTDownload File - Docx. Google Drive node, googleDrive. 1 incoming and 1 outgoing connections.STEP 08Download File - DocxGOOGLE DRIVEGOOGLEDRIVE1 IN / 1 OUTDownload File - PDF. Google Drive node, googleDrive. 1 incoming and 0 outgoing connections.OUTCOMEDownload File - PDFGOOGLE DRIVEGOOGLEDRIVE1 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

When clicking ‘Test workflow’

8 Execution Links
  1. Start

    When clicking ‘Test workflow’

    Trigger

  2. Step 2

    Own datasource

    Integration

  3. Step 3

    Image URL

    Transform

  4. Step 4

    Find & Copy Docx Template

    Integration

  5. Step 5

    Find Image ID in Docx

    Integration

  6. Step 6

    Replace Image in Docx

    Integration

  7. Step 7

    Make file shareable publically (optional)

    Integration

  8. Step 8

    Download File - Docx

    Integration

  9. Outcome

    Download File - PDF

    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.