Skip to main content
Subflows are the concrete building blocks inside a flow and are auto-discovered by Corbado Observe based on the event types you send. They represent a specific authentication step, for example password login, passkey enrollment, or email OTP login.
Install and set up the Corbado Observe SDK, including your first tracked event, in Getting started. This page focuses only on subflow-to-event mapping.

​
1. Provide identifier

The provide identifier subflow can be used to track when users enter and submit their identifier, such as an email address or phone number. The following events map to the provide identifier subflow:

​
2. Password login

The password login subflow can be used to track password-based login attempts from start to success or error. The following events map to the password login subflow:

​
3. Passkey login

The passkey login subflow can be used to track passkey-based sign-in attempts. The following events map to the passkey login subflow:

​
4. Social login

The social login subflow can be used to track authentication with social identity providers. The following events map to the social login subflow:

​
5. Passkey enrollment

The passkey enrollment subflow can be used to track passkey registration and setup. The following events map to the passkey enrollment subflow: The email link subflow can be used to track authentication flows where users sign in through a link sent by email. The following events map to the email link subflow:

​
7. Email OTP

The email OTP subflow can be used to track one-time-password verification sent by email. The following events map to the email OTP subflow:

​
8. Set password

The set password subflow can be used to track password creation or updates during authentication journeys. The following events map to the set password subflow: