Problem with Resend Make Module Attachments: filename ignored, always shows as attachment-0

Hi everyone,

I’m using the official Resend integration in Make to send emails with PDF attachments. The emails are sent out, but I’ve run into two issues with attachments:

  1. Even when I specify a File name in the Resend module, the recipient always sees the attachment as attachment-0 instead of the filename I set (e.g., insight.pdf, which is the same name in the database).

  2. The file is stored in public Supabase bucket. The file itself can be downloaded and opened with the url link, but in clients like Gmail it cannot be previewed inline as a PDF.

    My expectation:

  • The attachment should arrive with the exact filename I entered.

  • Email clients should recognize it as a PDF (application/pdf) and allow inline preview.

Has anyone else run into this issue with Resend + Make?
Do I need to switch from the Path-based attachment to using the Resend API with base64 content instead?
Or is there a workaround inside the Make module that I’m missing?

Thanks a lot for any guidance!

Welcome to the Make community!

How does the Resend “Send an Email” module look like, and how have you set it up?

I have the same problem. Also the link to the file appears good in the request body and in the right location. Sent in the path in attachments. Same link is used to upload the file to Airtable and it works there. This is how it arrives to my email:

Puzzled.

For your question @samliew, This is how it looks like:

image

Welcome to the Make community!

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,
  • 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.)

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’.

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.

To provide code/text using Markdown format, you can type a code fence.
Add three backticks ``` in a separate line before and after the content, like this,

```
text goes here
```

Alternatively, you can 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 @wuxiwanzi I found what was the problem.

The resend send email make module has a mistype in it’s body json.
It should send “filename” but it sends “Filename”.

I workaround it by using the resend api call module.

Hi @Dan_Liebeschutz, @wuxiwanzi,

thank you for making me aware of the issue :folded_hands:
I’m the developer of the Resend App and I’m sorry for the mistake on it!

I’ve requested a review of the update so hopefully the new version is being deployed soon.

Best,

Richard

1 Like