Okta Workflows - App Catalog Access Request
This custom action example illustrates a JSON payload that could trigger an app assignment in Okta
Use this guide to build a custom action to assign a user to an application in Okta when requested via the Torii app catalog.
When Okta receives the details for the access request via webhook, it will trigger the underlying workflow and use the data in the payload to run through a multi-step approval process, followed by assigning the user to the requested app.
More information on triggering Okta workflows through a webhook can be found here.
Custom Action Configuration
Method : POST
URL : <your_okta_workflows_webhook_url>
Query Parameters
Parameter | Variable Mapping |
---|
Headers
Header | Value |
---|---|
Content-Type | application/json |
Body
{
"appName": "[Trigger.App.Name]",
"approver1": "[Trigger.App.Details.Approver.Email]",
"approver2": "[Trigger.App.Details.Approver2.Email]",
"approver3": "[Trigger.App.Details.Approver3.Email]",
"approver4": "[Trigger.App.Details.Approver4.Email]",
"requesterEmail": "[Trigger.User.Email]",
"requesterFirstName": "[Trigger.User.First-name]",
"requesterLastName": "[Trigger.User.Last-name]",
"details": "[Trigger.Details-about-request]"
}
Tips
These Okta Workflow guides in the documentation provide more information on app assignments.
Congratulations!
You have successfully created a Custom Action for App Catalog Access Request using Okta Workflows.
Updated over 1 year ago