Trying to upload attachments from Gmail to S3

Miquel_Colomer · August 30, 2020, 12:27pm

Hi,

I am testing new Gmail Integration via OAuth2 with s3.

Currently, I have this workflow

This workflow gets all emails with attachments from my Gmail account (with resolved method, that includes all email details as well as attachments) and try to upload them to s3, as you can see here:

The problem is that I am not sure how to define where is located binary data of attachments on s3 step at these fields:

Does anybody test it properly?

Thanks!

jan · August 30, 2020, 2:28pm

Does it only have to work for one attachment or also for multiple ones?

Miquel_Colomer · August 30, 2020, 2:38pm

Hi Jan,

Currently, every email has just one attachment and multiple emails can be recovered at the same time.

jan · August 30, 2020, 2:40pm

In this case it is easy as you would have to only set “Binary Property”, which is currently set to “data”, to “attachment_0”. Then everything should work fine.

Miquel_Colomer · August 30, 2020, 2:45pm

I am trying this

and I get

jan · August 30, 2020, 3:01pm

@RicardoE105 as you are the one which created the S3-Node do you know what the problem could be here? Maybe you saw it before. But sounds like a bug.

RicardoE105 · August 30, 2020, 5:31pm

@jan will check this out today.

RicardoE105 · August 30, 2020, 7:58pm

@Miquel_Colomer checked this and it works fine for me. I wonder if you set up any of the additional fields on the S3 node? If so could you please let me know which ones you set?

Miquel_Colomer · August 30, 2020, 8:13pm

Not sure why, but now it copies attachments to folder

Now, after starting workflow, s3 never ends (loading gif appears always)

Additionally, OAuth2 session is lost and must be reconnected manually.

RicardoE105 · August 30, 2020, 10:05pm

Can you share that workflow with me?

Miquel_Colomer · August 31, 2020, 5:04am

Now workflow works. I think it is related to network latency problems.
If I detect the same issue again, I will notify you.

jan · August 31, 2020, 6:30am

Ah great to hear that it works now!

Yes, please keep us updated if you have issues again.

Miquel_Colomer · August 31, 2020, 8:26am

I’ve got same error 400 again:
ERROR: AWS error response [400]: 400 - "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\nXAmzContentSHA256MismatchThe provided ‘x-amz-content-sha256’ header does not match what was computed.

I share my workflow:
Workflow to upload attachments to s3

jan · August 31, 2020, 8:28am

Is it dependent on the file or file-type? Or did it not work with a specific file before and then suddenly started working?

Miquel_Colomer · August 31, 2020, 8:43am

Perhaps this helps you:

Gmail recovers up to 8 different emails.
Every email has only one attachment.
First attachment/email is uploaded properly to S3.
Second attachment/email returns commented failure on s3 node.