Ory is the largest open source community in the world for cloud software application security. We maintain advanced open source security software solving authentication, authorization, access control, application network security, and delegation. Ory implements a variety of industry and best-practice standards including OAuth 2.0 / OAuth 2.1, OpenID Connect, Zero Trust Networking, Google Zanzibar Policy Framework, FIDO2 U2F, WebAuthn, TOTP, and more.

Ory Community

Hey, I am currently looking at the PW recovery feature and realized that after the user started a Recovery Flow (recovery email triggered) only the recovery code itself is transferred (not the `flowId`, or messageId or similar). I looked at the webhook functionality, but unfortunately only either the recovery code or the flow id is available, depending on the hook being used.

`courier.http.request_config` "hook" -&gt; properties `recipient` and `recovery_code` get send, but not flowId
`selfservice.flows.recovery.before.hooks` / `selfservice.flows.recovery.after.hooks` -&gt; flowId is available, but the context of the email/recoveryCode is not existing (before) or already gone (after)

Question: is it somehow possible to enrich the data for the first general hook (`courier.http.request_config`), so that the flowId is also transferred?
Context: when having both the recoveryCode and flowId at hand, I could implement a better UX together with my custom UI.

I also had a look at the Kratos Go Code (`SendRecoveryCodeTo`) and adding the flowId there would be quite easy. It does not even need to be part of the `EmailTemplate` 's. But before creating an upstream PR I wanted to get in touch with you. Thx!