Back to marketplace catalog
Workday to Idira Identity LCM - Future Hires
By: Community
Use case Identity Governance
Category SaaS & business apps
Certification Community
Version 1
Released Jun 25, 2024
Last updated Oct 3, 2025

Overview

The flow retrieves a list of users and, if the list is not empty, iterates through each user while calling two APIs to fetch manager and user information. For each user, it checks if the user already exists in the records. If the user exists, it compares the values from the webhook with the datastore, proceeding without changes if there is no mismatch and updating the information if there is a mismatch. If the user does not exist, it creates a new user entry. If a manager ID is provided, it is used during both the creation and update processes to map the user to their manager; if no manager ID is provided, the user is created without a manager mapping. The system also checks for the user's role, iterating through the role list if the role exists, and ending the flow if it does not. An email is sent to inform relevant parties about the new hire. This process ensures accurate user management and proper notification for new hires.
Version 1
Current

Published Jun 25, 2024

We also recommend

Orchid Security for Idira PAM Discovery By: Idira

Overview Idira protects the privileged accounts it knows about — Orchid finds the ones it doesn't. Orchid discovers privileged accounts found in applications outside any IdP or PAM - local admins, service accounts, app-native identities, then reports them straight into Idira's Discovered Accounts queue, ready to onboard. Together, they close the privileged-access blind spot that attackers count on. Business Problem Idira secures the privileged accounts it knows about, but it can't protect what it can't see. Local admins, orphaned accounts, service accounts, and app-native privileged identities live inside applications that manage identities in their own local databases — never onboarded, never scanned, entirely outside PAM control. It's a large, growing attack surface, and exactly where attackers look first. Solution Orchid is the discovery layer that extends Idira's reach. Using passive scanning and AI-based analysis, Orchid determines which accounts are privileged across homegrown, COTS, and SaaS applications — including those Idira's native scanners never reach. From the Orchid console, these accounts are reported into Idira's Discovered Accounts queue, flagged as reported by orchid for instant filtering, ready for the admin's standard onboarding workflow. Orchid never modifies the vault — the customer stays in full control of every decision. Key Benefits Discover privileged accounts beyond Idira's native scanning reach — across the full application estate, including apps that manage identities in their own local stores. Close the PAM coverage gap by feeding Orchid-discovered accounts straight into Idira's Discovered Accounts queue. Accelerate onboarding with context-rich, source-tagged accounts ready for review. Prove coverage to auditors with a continuously updated picture of every privileged account and its management status.

Workday to Idira Identity LCM - Active Employees By: Community

Create and update user entries and map them with their manager IDs

Workday to Idira Identity LCM - Terminated Employees By: Community

Check and disable inactive users