JPG attachments not opening when sent via Make + Gmail (works fine when forwarded manually)

We have a scenario where we use an API to request a ZIP file containing several JPG images and one XML file. The ZIP file is then unpacked, and the contents are sent as attachments via Gmail.

Some customers report that they can’t open the JPG files. Strangely, if I forward the same email manually through Gmail, they can open the images without any problem.

I’ve read that this could be related to a difference in file encoding, but I’m not sure how to adjust that within Make. Are there any tools or modules in Make that can help fix or normalize the encoding of these files before sending them?

How are you attaching the files in the Gmail module?

We’d love to help, however, you have not provided sufficient information to demonstrate the problem that would allow us to reproduce the scenario and any issue/s and/or error/s.

To allow others to assist you with your scenario, please provide the following:

1. All Relevant Screenshots

We need to see what you’re working with to give you the best advice. Screenshots are extremely important because Make is a visual editor — a picture provides us with more context.

It would help us identify the issue by having screenshots of:

  • the full scenario,
  • the zoomed in section of the scenario that you are referring to (if your scenario is huge),
  • a full scenario run/execution (showing output “speech” bubbles),
  • any error messages,
  • individual module fields,
  • relevant filter settings (conditions), and
  • each module’s output bundles
  • any external services (spreadsheet headers, sample data, regex101.com, etc.)

You can upload images here using the Upload icon in the text editor:

We would appreciate it if you could upload screenshots here instead of linking to them outside of the forum. This allows us to zoom in on the image when clicked, and avoid tracking cookies from third-party websites.

2. Scenario Blueprint

Please export the scenario blueprint. Providing your scenario blueprint file will allow others to quickly recreate and see how you have set up the mappings in each module, and also allows us take screenshots or provide module exports of any solutions we have for you in return - this would greatly benefit you in implementing our suggestions as you can simply paste module exports back into your scenario editor!

To export your scenario blueprint, click the three dots at the bottom of the editor then choose ‘Export Blueprint’.

You can upload the file here by clicking on this button:

3. Module Output Bundles

Please provide the output bundles of each of the relevant modules by running the scenario (you can also get this without re-running your scenario from the History tab).

Click on the white speech bubbles on the top-right of each module and select “Download input/output bundles”.

A. Upload as a Text File

Save each bundle contents in a plain text editor (without formatting) as a bundle.txt file.

You can upload the file here by clicking on this button:

B. Insert as Formatted Code Block

If you are unable to upload files on this forum, alternatively you can paste the formatted bundles.
Here are some ways to provide text content in a way that it won’t be modified by the forum.

  • Method 1: Type code fence manually
    Add three backticks ``` in a separate line before and after the content, like this,

    ```
    text goes here
    ```
    
  • Method 2: Highlight and click the “preformatted text” button in the editor

  • Method 3: Upload your file and share the public link
    (this method is only recommended for large files exceeding the forum upload limit)

Providing the input/output bundles will allow others to replicate what is going on in the scenario, especially if there are complex data structures (nested arrays and collections) or if external services are involved, and help you with mapping the raw property names from collections.

Sharing these details will make it easier for others to assist you.

Hi Samliew,

thanks for your message. I can share some information with you, but the output files and the blueprint also contain API keys, and I’d rather not make those public. I hope you understand!

Below is an overview of the full workflow, does this help?

I have a feeling the issue is with the file type. This is the output of a JPG file that’s being extracted from a zip.

    "name": "178651297_industrieweg_oo_begane_grond_begane_grond_20251103_beb0ed.jpg",
    "path": ".",
    "data": "IMTBuffer(395972, binary, c68658be88978e3fc5a39729a1ef33eaa19f8813): ffd8ffe000104a46494600010101004800480000ffdb00430001010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101ffdb004301010101010101",
    "size": 395972,
    "modified": "2025-11-03T13:31:12.000Z"

Do you see anything unusual here?

If you need more info just let me know. I can send you specific details.