← All N8N workflows
Media & contentCodeHTTP RequestIfRespond To WebhookWebhook

Dynamically Replace Images in Google Slides

Configured with HTTP Request, Respond To Webhook, Webhook. Review the connections and setup before adapting this template.

Workflow preview
Web / APIReplace ImagesHTTP RequestWeb / APIError Missing FieldsRespond To WebhookWeb / APIRespond to WebhookRespond To WebhookTriggerWebhookWebhookCodeRetrieve matchingImages ObjectIdsCodeWeb / APIRetrieve All SlideElementsHTTP RequestRoutingCheck if all params areprovidedIf

Node categories in this workflow

  • Web / API
  • Trigger
  • Code
  • Routing

Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.

Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.

How it works

The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.

Workflow node names, types, and operations
NodeCategoryTypeOperation
Replace ImagesWeb / APIHTTP RequestPOST
Error Missing FieldsWeb / APIRespond To WebhookSee node parameters
Respond to WebhookWeb / APIRespond To WebhookSee node parameters
WebhookTriggerWebhookSee node parameters
Retrieve matching Images ObjectIdsCodeCodeSee node parameters
Retrieve All Slide ElementsWeb / APIHTTP RequestSee node parameters
Check if all params are providedRoutingIfSee node parameters

Setup

  1. Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
  2. Connect your own credentials through n8n’s credential store. Replace REPLACE_WITH_* values with your resource identifiers.
  3. Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
  4. Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.

Requirements

An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.

Credential types declared in the source

  • googleSlidesOAuth2Api

Workflow notes

Dynamically Replace Images in Google Slides

Dynamically Replace Images in Google Slides

This workflow exposes an API endpoint that lets you dynamically replace an image in Google Slides, perfect for automating deck presentations like updating backgrounds or client logos.

Step 1: Set Up a Key Identifier in Google Slides

Add a unique key identifier to the images you want to replace.

  1. Click on the image.
  2. Go to Format Options and then Alt Text.
  3. Enter your unique identifier, like client_logo or background.

Step 2: Use a POST Request to Update the Image

Send a POST request to the workflow endpoint with the following parameters in the body:

  • presentation_id: The ID of your Google Slides presentation. You can find it in the URL of your Google presentation : https://docs.google.com/spreadsheets/d/REPLACE_WITH_DOCUMENT_ID/edit#slide=id.p)
  • image_key: The unique identifier you created.
  • image_url: The URL of the new image.

That's it! The specified image in your Google Slides presentation will be replaced with the new one from the provided URL.

This workflow is designed to be flexible, allowing you to use the same identifier across multiple slides and presentations. I hope it streamlines your slide automation process!

Happy automating! The n8Ninja

Dynamically Replace Images in Google Slides

Dynamically Replace Images in Google Slides

Purpose and structure

This folder contains the Dynamically Replace Images in Google Slides workflow. Its executable nodes use code, httpRequest, if, respondToWebhook, webhook. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.

Setup

Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.

Entry points

Webhook

Verification

Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.

Attribution

https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Code/0491_Code_Webhook_Monitor_Webhook.json MIT; preserve source notices.

More in Media & content