Thanks for summarizing, Tyler! I think we mean the same thing, allow me to give another example: Think of the out-of-the-box "Event Registration Created" trigger: today, if you want to use the event or registration data in a downstream Power Automate flow, you have to manually declare and map each field as a custom attribute in the Custom Trigger and then actually set those values when using the trigger within the journey.With this idea, that context would be available in the flow automatically — just as it already is in the email editor. You could directly reference the event registration or event in the flow without having to manually pass them through custom attributes or retrieve them through additional Dataverse lookups in the flow itself.