Before
An operator likely had to determine whether an account needed enrichment, search several identity and directory systems for matching account information, and account for domain-qualified versus non-qualified usernames. They then had to locate the user's manager and copy the manager email into the working record or context.
How it works
- Receive the account event and check whether a qualifying account requires enrichment.
- Search the available identity and directory sources for account information, then choose the user lookup path based on whether a domain is present.
- Retrieve manager details, place the manager email in context, and complete the workflow.
Workflow details
- Trigger and eligibility: The workflow starts when an email event is received and checks whether an account is available for enrichment without a domain prefix. If no qualifying account is found, the process completes without continuing through the enrichment branches.
- Account discovery: When enrichment is required, conditional paths check available identity and directory sources for account information, including cloud directories, identity management platforms, and an AWS-backed account source. These checks allow the workflow to save or identify account usernames from the source that contains relevant data.
- Domain-aware lookup: The workflow determines whether a domain was provided and selects the corresponding user lookup path. This avoids treating domain-qualified and non-qualified account identifiers as the same lookup case.
- Manager resolution: After the user record is located, directory-specific manager-detail steps retrieve the user's manager information. A transformation then sets the manager email address in the workflow context.
- Completion: The workflow ends successfully after the available account and manager information has been processed. It does not show a notification or human approval step, so the resulting context is prepared for use by subsequent workflow logic.
What changed
Account eligibility checks, multi-source account lookups, domain-based routing, and manager-email capture now occur within one workflow run. The human handoff changes from manually gathering and copying identity details to receiving a completed enrichment context for any subsequent process.
Work removed
Repeatedly checking whether an account needs enrichment, searching multiple identity and directory systems for usernames, deciding which domain-specific lookup to use, locating manager details, and copying the manager email into workflow context.
Expected outcome
For each qualifying request, the workflow can consolidate up to seven configured account-information source checks and one domain decision into a single run, with the actual time saved depending on the source systems involved.
