Overview

The Email Events trigger fires on opens and clicks, but the event never carried anything that identified which email produced it. If you pushed those events to an external system with the Send Webhook action, there was no Message ID variable to pick.

What's new

Email Events now carries a unique Message ID, and you can select it as a custom value inside the Send Webhook body.

How it works

Open the Send Webhook action in a workflow that starts with Email Events, then pick Message ID from the custom value picker when you build the payload. Every open and click on the same email sends the same ID. A different email sends a different one. The ID rides along with the event itself, so an open that arrives late still points back to the email that generated it.

Why this matters

Teams feeding email engagement into an external dashboard had no reliable way to dedupe. Email Opened fires on every open, including repeat opens of the same message, and resolving the email through the API by "most recently sent" got the wrong answer whenever a contact opened something older.

Simple example

A marketing agency sends two campaign emails in the same week and pipes open and click events into its own reporting dashboard. With Message ID in the webhook body, each open lands against the specific email it came from, and the same contact opening one email four times collapses into a single engagement record instead of four.

Additional Notes

• Applies to both Email Opened and Email Clicked on the Email Events trigger.
• The ID is stable per message. Repeat opens send the same value every time.

Preview