Gmail trigger not populating message ID, causing Zap errors.

  • 18 January 2024
  • 2 replies

Userlevel 1

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,


2 replies

Userlevel 1

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

Userlevel 7
Badge +14

Hi @a912 

To troubleshoot, check your Zap Runs history to see the DATA IN/OUT for each Zap step:

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.