Email Integration Question: How are emails in multiple folders supposed to work?

Get Help
1

Hey there! I’ve been using the Gmail integration for a bit now, and I was pretty sure some of my automations were working previously but stopped, so it got me digging in a bit:

Some groundwork:

  1. My Gmail integration watches the folders “Inbox” and “Task”
  2. I have an automation that fires when an email is created / updated and the folder contains “Task”

For example, I have this email sitting in my Inbox, which I’ve labeled “Task” as well:
image

However, when that email gets pulled into the integration, Fibery only thinks it’s in “Inbox”, and the automation never fires:
image

If I remove the email from Inbox and leave “Task” label, then resync, it does then correctly pull in the message into my automation… but seemingly only if I remove the original message from Fibery entirely.

What’s especially odd is I swear that up until mid-October, this all worked perfectly fine. Has something changed recently in the handling of multiple folders on a message in the Gmail Integration?

2

I wonder if this could be an issue with the filters, or an issue of clashing/ordering of different rules. Could it be that there’s a rule that affects “Inbox” emails, thus making emails with both “Inbox” and “Task” not processed by the later “Task” rule?

Or could the filter be filtering out emails that have the “Inbox” label?

I wonder if it would work to create a rule that removes the Inbox label if the email also has the Task label, and move this rule to be above your desired automation.

1 Like
3

Hey! What kind of Authentication type are You using for Gmail? Is it via “OAuth” or “App Password”?

For “OAuth” it was always the case we select INBOX if it’s present in labels for an email.

For App Password, if You selected during filter setup both folders: INBOX and /Task, it is a known bug that it will sync the same email twice: once for INBOX and once for /Task.

4

I use OAuth integration for Gmail. So in that case, the ONLY folder sync will see is INBOX, is that correct? So for firing automations based on folder, then it sounds like the OAuth integration will not work for us (as “Task” will never be the folder unless we manually remove the INBOX version and resync)

I could switch this to App Password, but I don’t love the idea of getting duplicates either… Hmm.