event.request Not Present in Custom-Email-Provider Action

Last Updated: Sep 10, 2025

Overview

This document says that the event.request object should be present in the custom-email-provider Action. However, it is not always present. This article explains why.

Applies To

Custom-Email-Provider
Action

Cause

Currently, this is expected. There is a specific set of emails that do not populate the request object; it depends heavily on how the NUL is configured and how the request to execute the flow is being triggered.

Solution

This is currently acknowledged internally, and efforts are being made to standardize the presence of this value across executions, but the attribute should be considered optional for the time being.