Automate Google Docs Logo Updates with Make.com

When your company rebrands, updating every logo in every Google Doc can be overwhelming. With make.com, you can automatically find and replace old logos with a new one across many documents, saving time and reducing manual work.

This step-by-step guide is based on the official scenario example from the make.com how-to section and shows you how to set up a no-code workflow to handle logo replacement during a rebranding.

What You Need Before You Start in Make.com

Before building the automation, prepare a few essential items. This will keep your scenario simple, reliable, and easy to maintain.

• A make.com account with access to the scenario editor
• A Google account with access to the relevant Google Docs
• The new logo stored as an image in Google Drive
• Knowledge of where the old logo images are stored or how they appear in the documents

The original tutorial on the make.com how-to page demonstrates a typical rebranding process that you can adapt to your own organization.

How the Make.com Scenario Works

The core idea of the automation is simple: find all documents that need the new branding, identify the old logo, and replace it with the new image. Make.com orchestrates this process by chaining several modules together.

The scenario follows this general logic:

1. Search for all relevant Google Docs.
2. Retrieve each document and locate the old logo.
3. Insert the new logo from Google Drive.
4. Remove or replace the old logo instance.

The exact modules and configuration can vary, but this structure gives you a reliable framework to copy and modify.

Step 1: Create a New Scenario in Make.com

Start by creating a fresh scenario in the make.com dashboard.

1. Log in to your make.com account.
2. Click on Create a new scenario.
3. When prompted to add your first module, choose Google Docs.

At this point you will connect your Google account if you have not done so already. Make.com guides you through an authorization flow to grant access to your documents.

Choosing the Right Trigger in Make.com

There are two common ways to start the logo replacement process in make.com:

• Scheduled trigger: Run daily, weekly, or at specific intervals to keep documents up to date.
• Manual trigger: Start the scenario on demand whenever a rebranding batch is ready.

For a one-time company rebranding, a manual or on-demand run is usually enough. For future brand updates, a scheduled trigger can keep new files aligned automatically.

Step 2: Search for Target Google Docs

Once the trigger is set, add a module to locate the documents that contain the old logo or belong to the rebranding batch.

1. Insert a new module and select Google Docs > Search documents or a similar search operation.
2. Filter by folder, document name pattern, or other metadata that identifies documents requiring the new logo.

Your goal is to feed a list of documents into the rest of the make.com workflow. If your documents are organized in a specific Drive folder for rebranding, filter by that folder ID to reduce noise and speed up the scenario.

Best Practices for Document Selection in Make.com

To avoid updating the wrong files, use these strategies:

• Keep all rebranding documents in a dedicated folder.
• Use naming conventions such as “Brand2025_” in titles.
• Test your search filters with only a few documents first.

Refining the search step in make.com makes the rest of the scenario more predictable and easier to troubleshoot.

Step 3: Prepare the New Logo in Google Drive

The new brand logo must be accessible as an image file in Google Drive so the scenario can insert it into multiple documents.

1. Upload the new logo image (for example, PNG or JPEG) to Google Drive.
2. Note the file ID or select the file directly from the module picker inside make.com.

You can use a Google Drive module in make.com to reference the image, or you can paste its file ID into a mapping field when inserting the new logo.

Handling Different Logo Variants

If your rebranding involves multiple logo versions (e.g., dark and light variants), you can extend the make.com scenario to:

• Look up the correct logo variant based on document folder or naming rules.
• Store logo IDs in a data store or spreadsheet and reference them dynamically.

This advanced configuration gives you fine-grained control while still relying on the same underlying logo replacement logic.

Step 4: Replace the Old Logo with Make.com

Next, configure modules to open each document, find the old logo, and insert the new one.

1. Add an iterator or array processing module if the search step returns multiple documents.
2. For each document, retrieve its content via a Google Docs module.
3. Identify the position or placeholder where the old logo appears.
4. Insert the new logo image using the Google Docs insert or update content operation.

In the official example from make.com, the workflow focuses on replacing image elements representing the old logo. Depending on your template structure, you might also look for specific text placeholders or markers around the logo area.

Techniques to Identify the Old Logo in Make.com

There are several approaches for detecting what needs to be replaced:

• By image ID or URL: If the old logo image is consistent across documents, you can look for its specific reference.
• By surrounding text: Search for a heading or label near the logo and use that location as an anchor.
• By template placeholder: Use a custom string like {{LOGO}} that the scenario can replace with the new image.

Whichever method you choose, make.com modules can map the identified region and then insert the new file from Google Drive.

Step 5: Test and Refine Your Make.com Scenario

Before running the automation on all documents, thoroughly test the scenario in make.com using a limited sample.

1. Duplicate a few representative documents.
2. Run the scenario step-by-step or in test mode.
3. Verify that the new logo appears correctly in the intended position.
4. Confirm the old logo is removed or replaced as expected.

If something does not look right, adjust your search filters, anchor text, or image placement options, then repeat the test. Make.com allows you to inspect each module execution to see exactly what data is being passed between steps.

Running the Final Logo Replacement in Make.com

Once the test passes, you can:

• Switch the scenario on in make.com.
• Run it manually for the full set of documents.
• Monitor the execution log to ensure all items are processed successfully.

After completion, spot-check several updated documents to verify the new branding is consistent everywhere.

Tips for Managing Future Rebranding with Make.com

Rebranding rarely happens only once. By keeping your make.com scenario well organized, you can reuse it whenever your brand changes again.

• Store logo file IDs in variables or configuration modules for easy updates.
• Document each module’s purpose with clear notes.
• Group related steps into logical sections so others can maintain the workflow.

If you need professional help designing advanced automation or integrating multiple systems around make.com and Google Docs, you can consult specialists such as ConsulTevo for tailored support.

Conclusion: Streamline Rebranding with Make.com

Updating logos in every Google Doc no longer has to be a manual, document-by-document task. By following the scenario structure demonstrated in the official make.com tutorial, you can:

• Automatically locate documents that require brand updates.
• Replace old logos with a new image from Google Drive.
• Maintain consistent branding across large document libraries.

With a single scenario in make.com, your marketing and operations teams can complete complex rebranding projects in minutes instead of days.

Need Help With Make.com?

If you want expert help building, automating, or scaling your Make scenarios, work with ConsultEvo — certified workflow and automation specialists.

Get Help