How to Properly Map and Send File Attachments Between Scenarios Using Sub-Scenario Calls

How To
1

Hi everyone!

I’m working on a Make.com scenario that processes incoming email attachments. The goal is to:

  1. Monitor incoming emails.
  2. Capture and sort the attachments.
  3. Analyze the content of those files.
  4. Route and save them into the appropriate folders based on that content.

Since I noticed that the same file analysis logic was repeating in multiple branches, I decided to optimize it using sub-scenarios. This would help reduce redundancy and make the main scenario cleaner.

The Issue

The challenge I’m running into is sending the actual file data from the main scenario to the sub-scenario. Specifically:

  • In the sub-scenario’s input fields, I don’t see an input type that corresponds directly to a file (binary data).
  • I’ve tried setting the type to “Text” and referencing 1.data, as seen in the main scenario mapping. But this doesn’t seem to transfer the file properly to the sub-scenario.
  • I’m not sure if Make even supports sending files between scenarios like this — or if I’m missing something about how to do it correctly.

What I’ve Tried

  • I mapped the data and filename fields explicitly, using the output of the email parser module.
  • I used “Text” as the type for the Data input in the sub-scenario because there’s no obvious “File” type option.
  • I confirmed that 1.data is working when used in modules like CloudConvert inside the main scenario.

What I Need Help With

  • Can sub-scenarios in Make receive actual files (not just metadata or filenames)?
  • If so, what’s the correct way to define and map these fields?
  • Should I be converting the file into Base64 or some other encoding first?

Any guidance, examples, or even confirmation of whether this is possible would be massively appreciated!

Thanks in advance! :folded_hands:

image
image1469×641 97.5 KB

image
image1033×629 121 KB

image
image555×896 63 KB

image
image470×685 27.8 KB

2

Hi @Augusto_Alegre,

actually a very interesting issue. I’m not sure if files generally I supported, at least they are not supported using the very intuitive file upload input we’re used to in other modules. Some files, as you already thought of, are basically only encoded text, those could work.

Sadly, I cannot give you a definitive answer but my approach here would be to maybe pass a URL and then download the file in the subsenario? This way you work around this unknown or the limitation.

Best,
Richard

1 Like