Mapping error

[life.tripod]

I have workflow that works in this way:

1. Check and download new PDf files from Gdrive
2. Create an HTTP Request to PDF Stirling and Remove specific pages
3. Rename the file as File-1
4. Repeat the process using the originally downloaded file from Gdrive and remove different pages
5. Rename the file File-2
6. Repeat the process using the originally downloaded file from Gdrive and remove different pages
7. Rename the file File-2
8. and so on
9. Email everything using Gmail.

The workflow works for the first part (up point 3) then I am unable to properly map the original file: even if i select the downloaded file from Gdrive, n8n changes the setting of the next HTTP Request (or does not apply my selection) and chooses the file from the last node.

Here is my workflow:

Here, it shows my selection of Gdrive

Here it shows that after the workflow runs, the system switches the input node:

How do i fix it?

[n8n]

It looks like your topic is missing some important information. Could you provide the following if applicable.

• n8n version:
• Database (default: SQLite):
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• Running n8n via (Docker, npm, n8n cloud, desktop app):
• Operating system:

[ihortom]

Hey @life.tripod , to access binary files in HTTP Request node you do need to have that binary file present in the preceding node. It won’t work if you try accessing it from any other nodes.

There are a few ways to bring the binary to the node preceding the one you need to access it from. See [onedrive via Graph HTTP] why binary don't upload if not exactly previous node? - #2 by ihortom for details.

[life.tripod]

thanks, is there a way to aggregate all the files (not merging) so that Gmail waits for all the process to complete and does not send multiple emails but just one with multiple attachments?

[ihortom]

Hey @life.tripod , there are two way to approach it:

1. You could compress all the files into a single archive file and send it out like that. Use Compression node for that.
2. Use separate files. GMail node allows to list all the attachments (comma-separated)

In the letter case you would need to programmatically determine all the binary names and compose a string accordingly.