Before
A support or IT operator likely had to review the incoming email, identify the user account, and manually initiate the password reset. When applicable, the operator also had to generate a new password and update the user's profile before handling any failure.
How it works
- Receive the email-triggered request and extract the user information.
- Attempt the password reset and check whether the account was found.
- For a found account, generate a new password and update the user profile; otherwise, route the request to failure handling.
Workflow details
- Request intake: An email-triggered event starts the workflow, and the relevant information is extracted from the incoming webhook data.
- Password reset: The workflow attempts to reset the user's password and then evaluates whether the account was found.
- Account-based routing: If the account is found, the automation generates a new password and proceeds with a user-profile update; if not, it builds an output and routes the branch to failure handling.
- Operational result: The process produces an execution result for the password-reset sequence, with downstream failures stopped and directed through the defined failure path.
What changed
The password-reset sequence now begins automatically from an incoming email, performs the account check, and follows the appropriate branch without requiring an operator to move between steps manually. Human involvement is reduced to handling cases that reach the failure path or require further review.
Work removed
Reviewing each password-reset email, extracting the user information, locating the account, initiating the password reset, generating a new password, updating the user profile, and manually routing unsuccessful requests to failure handling.
Expected outcome
At least one manual password-reset workflow and account lookup can be removed for each successfully processed email request.
