Okta Workflows
Create an outgoing webhook in Apono that will send Apono access requests data to Okta Workflows
The steps below describe how to create an outgoing webhook in Apono that will send data on Apono access requests to Okta Workflows. Then, configure any workflow you'd like in Okta Workflows.
Prerequisites
Item | Description |
---|---|
Permissions | Super admin with access to Okta Workflows |
Configure your API endpoint settings | Follow these steps to configure API endpoint settings:
|
Client Token | Okta API token |
Create the webhook
- On the Webhooks page, click Add Webhook. The Add Webhook page appears.
- Enter a unique, alphanumeric, user-friendly Name for identifying this webhook.
- Click the Status toggle to Active.
- From the Method dropdown menu, select POST.
- In the URL field, enter https://<DOMAIN>.workflows.okta.com/api/flo/<CLIENT_TOKEN>.
Be sure to replace<DOMAIN>
with your company domain and<CLIENT_TOKEN>
with theclientToken
generated in Okta Workflows.
The webhook URL must adhere to the following requirements:
- Uses the HTTPS protocol
- Does not specify any custom ports
- In the Body Template field, enter the JSON payload data for the webhook.
{ "fields":{ "event type": "{{event_type}}", "event time": "{{event_time}}", "requestor email": "{{data.requester.email}}", "integration name": "{{data.access_groups.[0].[integration].name}}", "resource type": "{{data.access_groups.[0].[resource_types].[0].name}}", "access units": "{{data.access_groups.[0].access_units.[0].resource.name}}" } }
Click View event's payload schema to reveal the payload schema and available data fields. You can also refer to the Webhook Payload Schema Reference to read the descriptions of each data field.
-
(Optional) Under Headers, use the following Key and Value value to set the header. You set the
clientToken
as a header value instead of passing it in the Invoke URL in step 5.
Be sure to replace the<CLIENT_TOKEN>
placeholder.Key Value x-api-client-token <CLIENT_TOKEN>
- From the Triggers dropdown menu, select one or more of the following event triggers, which correspond to Apono access request statuses:
- RequestCreated
- RequestApproved
- RequestRejected
- RequestGranted
- RequestExpired
- RequestFailed
- Manual
- Under Filters, define one or several filter from the listed dropdown menus.
- Click Test to generate a test event to trigger your webhook. A Test successful or Test failed response status will appear at the bottom of the page. A successful test will send a mock event to Okta Workflows.
For more information about the test, click View Invocation Data. A panel opens revealing the request, response, and other relevant details.
Should your test fail, view these tips to troubleshoot your webhook.
- Click Save Webhook.
Results
Your webhook should now start sending events payloads to the workflow once triggered.
Updated about 1 month ago