Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

I’ve built some zaps that that would trigger when a specific email is assigned to a label, so the flow structure is very basic. it simply get the “Raw Payload Header Message ID” and pass to a sub zap which then retrieves the email again using a gmail filter rfc822msgid:<payload> and do further processing with it.

 

The problem is that the Raw Payload Header Message ID is not always populated by the Gmail trigger and I end up with errors due to the fact that the “Raw Payload Header Message ID” is blank….

Upon checking the flows and reviewing the email that was parsed by the trigger I can see that the “Raw Payload Header Message ID” is present for almost all failed emails however its not being parsed to the next block in my zap.

 

Has anyone had a similar problem ? How have you addressed it ?

Is there a better way to store the whole email content including attachments and retrieve it in a submodule, so I don’t need to pull it multiple times on my submodules  ? (I’ve attempted the zap Storage however its clearly designed for simple KVP and not for whole emails. Tables are also being considered however I’m not sure if there is a better way for achieving this.)

 

Thank you all in advance,

a912

Hi @a912 not sure about the issue with Raw Payload Header Message ID, but for storing the content, you might try the following:

https://zapier.com/apps/storage/help

Hi @a912 

To troubleshoot, check your Zap Runs history to see the DATA IN/OUT for each Zap step: https://zapier.com/app/history/

You may need to remap a variable between Zap steps.

 

Post screenshots to give us more context about how the Zap steps are outlined and configured.

No, I have the same issue, definitely a zap problem - email headers are not always exactly the same and the gmail app has an issue where it does not always recognise them, see below, the no data header is the standard implementation, usually works and has data but not always … found a message where there was no data and used it to edit zap … recognised a NEW Message-ID header in addition to old and that had data in it

 

 

Hi ​@Claelly,

Before we dig deeper into this, could you please let me know if the headers fields are present in the Zap History? I have a hunch that when the Zap triggers sometimes getting an inconsistent label for the Message-ID Header field, breaking Zaps when it changes.

Could you please send a screenshot of the headers field in the Zap History?

I'll be keeping an eye out for your response!

You mean this ​@ken.a? The Message ID is definitely there it’s just not recognised with the usual parameter that was used to set the zap up … seems like there’s a new one

 

Hi ​@Claelly,

We might need to map the Payload Headers twice on the field since the Gmail step is inconsistently returning those data.

Could you please check if the Raw Payload Headers References and Raw Payload Headers In Reply To changes in the Zap run? If so, we might need to utilize custom pill mapping to fix the issue that you’re encountering.

I'll be keeping an eye out for your response!

Reply


Terms & Conditions