Gmail Zap not triggering for all emails only working for some
My trigger is new email matching search to trigger a bulk text message through text magic. It’s been hours since these emails came through in the evening and no trigger took place on all 3.
Search Email
“subject:starfish
in:inbox
from:reports@pushmetrics.io”
the email went through at 12:33pm and the text’s went out properly. Then another email with the same subject gets sent at 5pm and nothing happen. I tried two more times and again no Zap created and no Text. It was working twice a day all last week. Can anyone explain this? Customer support takes forever and I’m finding rarely has an answer for technical problems.
This post has been edited by a moderator to remove sensitive information. Please remember to obfuscate any personally identifiable information prior to posting as this is a public forum.
Page 1 / 1
Hi @kealyc
FYI: This Gmail trigger is NOT instant, and depending on your Zap plan can take from 1-15 minutes to trigger.
Each Gmail trigger has a specific length of time in the past that it can "see" emails in your Gmail account. If the email in question is older than the time limit, the trigger won't be able to detect that email.
These limits are as follows:
New Labeled Email - Unlimited
New Starred Email - 2 days
New Email - 1 hour
New Email Matching Search - 1 hour
New Thread - 1 hour
New Attachment - 1 hour
Please note that if you would like to trigger a Zap for starred emails that entered your inbox more than two days ago, you can use the New Labeled Email trigger and specify the STARRED label from the dropdown when setting up your Zap.
Gmail currently has a limit of 15 simultaneous connections per account. This effectively means only 15 Gmail trigger Zaps can be used at once assuming no other service is accessing Gmail on your behalf. This is a restriction from Gmail's API documented here. There are no known work arounds except some good old fashioned creativity! If you come up with something awesome, let us know.
To audit what other apps or services might be connecting to your Gmail account and remove any of them that may be unnecessary, check out this link
Hi @kealyc
FYI: This Gmail trigger is NOT instant, and depending on your Zap plan can take from 1-15 minutes to trigger.
ok but it's just not triggering at all in the evenings. i’ve waited hours let alone 1-15 minutes since the emails came through.
@kealyc
Can you post screenshots with how your Zap trigger step is configured?
From the screenshot, it’s unclear if those emails are in the Inbox.
Check that the Zap is still ON.
@kealyc
Can you post screenshots with how your Zap trigger step is configured?
Check that the Zap is still ON.
yes it’s been on like it was at 12:33pm when it worked. I only have 1 zap active.
So I have a rule where it goes to a subfolder in the Inbox to “push-metrics”.
I tried changing the criteria to match that label:inbox-push-metrics but it still didn’t work. I tried with quotes and without. It’s weird though because this was all working fine last week. I reached out to support but they are just like, we reported the problem but we don’t have an ETA on a solution and i haven’t heard back in 8 hours.
thanks for your persistence. I tried setting up a labeled email and selected the Push Metrics options but I’m getting another error.
Now the weird thing was when i manually when to the apps page to Gmail and Clicked “run” it actually did scan my new emails and sent out a ton of texts at the same time. But it only works when i click it manually it’s not working automatically on a schedule.
@kealyc
Best is to have ZapierSupport troubleshoot further by looking into the logs which I don’t have access to.
yeah it’s not a free account. alright thanks for trying. this is frustrating support@zapier takes forever to get back to me and when they do they rarely have a solution.
@kealyc
FYI: I’ve flagged this for ZapierCommunityAdmins to hopefully escalate with ZapierSupport.
One more thing to test: Try putting the search criteria into Gmail to see if emails are found.
Alright yeah it looks like it shows up in the search. I just got a huge glut of texts all at once again which would not be acceptable for our client.. this just really bumming me out.
Yeah it’s only working when i manually click “run” but i need it to be automatic.
@kealyc
Alternatively, you could try using Gmail New Email as Step 1 and a Filter as Step 2 to check the desired conditions.
Otherwise, at this point, you’ll need to get in touch with ZapierSupport for further troubleshooting: https://zapier.com/app/get-help
Hey @kealyc,
I’m really sorry you’re running into such trouble with your Zap here, that’s not what we want at all! :(
I’ve passed the thread here over to Support so they can reference all the troubleshooting that’s been discussed here their investigations into the Zap not triggering.
I can see that our Support Team previously added you to a bug report for the New Email Matching Search trigger not triggering when it should have done. There’s no ETA on when that issue will be resolved but we’ll definitely email to let you know as soon as it is.
In the meantime, I’ve been trying to replicate this issue in my own Gmail and Zapier account and I’m not running into the same issues. My Zap takes a few minutes before triggering but it does so automatically. I thought it might be to do with the sub folder (sub-label) which was moving the emails but I added a similar filter in Gmail to move emails into a sub label and they triggered the Zap fine.
One theory I had here is that if the Zap polls for new emails and sees the email before Gmail has applied the label then it might ignore it as it doesn’t match and not trigger on it, but equally it could just be that the behaviour your Zap is experiencing is due to the bug Support identified.
I would recommend switching to using the New Labeled Email trigger as Troy suggested for the time being as that trigger does not appear to be affected by the same bug. With the error that appeared, it looks like something may have glitched when switching the trigger event over. Refreshing the page when you see that error should get rid of it, and then allow you to test the step and turn the Zap on.
Can you give that a try and let us know if you have better success with that trigger?