<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
Using a Request Type ID to Configure Conditional Workflow Actions
Workflows
Identity Governance
Okta Classic Engine
Okta Identity Engine
Overview

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.

Applies To
  • Okta Workflows
  • Okta Identity Governance
Solution

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

  1. Navigate to Identity Governance > Access Requests.
  2. Locate the specific request type to identify in the workflow and click to Edit the Request Type.
  3. Look at the browser's URL address bar. The Request Type ID is the unique string of characters before last /edit of the URL.

Example URL:
https://your-tenant.at.okta.com/next/request-types/68e4d064bda195401fb3e4ee/edit

  1. In the example above, the Request Type ID is 68e4d064bda195401fb3e4ee.
  2. Copy this ID to the clipboard.

Part 2: Use the ID in a Workflow Condition

  1. In the workflow, the Access Request Created card contains output data from the triggering event.
  2. The ID for the submitted request type is located in the card's output's Debug Context object, under the field requestTypeId.
  3. 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).

  1. 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.

Workflows

Loading
Using a Request Type ID to Configure Conditional Workflow Actions