Moving binary data (downloaded Gmail attachment) to final node

[danielrosehill]

Almost there but stuck on the last hurdle!

Workflow Model

Description

This is a workflow for processing business expenses:

• I add a Gmail label to biz expenses
• They enter into Gmail trigger
• Attachment is pulled at first step

Then:

• Attachment gets sent to Gemini so that it can be labelled with an identifiable file name

And the coup de grace (at least it was supposed to be)

• That gets uploaded to Gdrive

Something like this (with the data from the invoice as the binary):

The issue:

• The binary data from the attachment needs to make it to the final upload node, but … that doesn’t happen by itself.

Any help appreciated!

[Grot]

Hi, I think I can help. The node before to the Gdrive does it output the binary?

Also the workflow you pasted has the gdrive as move. Is it the same workflow?

[danielrosehill]

Ah, thanks but i just figured it out.

But basically, no.

Gmail label = invoices with attachments (as PDF).

So the binary is received after the trigger matches.

What worked was a merge node passing that and the result of the Gemini processing.

This merge strategy seems to have done the trick: