A workflow triggered by the Access Request Created card often requires different actions depending on the submitted Request Type.
This guide explains how to find the unique ID for a specific Request Type and then use that ID within a workflow to build conditional logic.
- Okta Workflows
- Okta Identity Governance
The process involves two main parts: locating the unique ID for the request type in the Okta UI and then using that ID to build a condition in the workflow.
Part 1: Locate the Request Type ID
- Navigate to Identity Governance > Access Requests.
- Locate the specific request type to identify in the workflow and click to Edit the Request Type.
- Look at the browser's URL address bar. The Request Type ID is the unique string of characters before last
/editof the URL.
Example URL:https://your-tenant.at.okta.com/next/request-types/68e4d064bda195401fb3e4ee/edit
- In the example above, the Request Type ID is
68e4d064bda195401fb3e4ee. - Copy this ID to the clipboard.
Part 2: Use the ID in a Workflow Condition
- In the workflow, the Access Request Created card contains output data from the triggering event.
- The ID for the submitted request type is located in the card's output's Debug Context object, under the field requestTypeId.
- Add a conditional function card, such as Branch or Continue If, to the workflow.
Create a condition that compares the requestTypeId field from the event card with the ID copied from the URL in Part 1.
Example Condition:Debug Context.requestTypeId (from the event card) == 68e4d064bda195401fb3e4ee (the value that was just copied).
- This condition will now resolve to true only when the workflow is triggered by that specific access request type, allowing to build custom logic paths for different requests.
