Overview

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.

Step-by-step guide

Prerequisites

Item	Description
Permissions	Super admin with access to Okta Workflows
Configure your API endpoint settings	- Create a flow in your Workflows Console and click Add event. - From the Pick an app to start your flow dialog, select API Endpoint. - In the API endpoint settings dialog, select Secure with OAuth 2.0 as the security level.

Creating the webhook

In the Apono admin portal, click your avatar at the bottom left corner, click Settings and pick Webhooks

Click Add Webhook
Fill in the following fields:
Method - POST
URL
```
https://<DOMAIN>.workflows.okta.com/api/flo/<clientToken>
```
Replace <DOMAIN> with your company domain.
Replace <clientToken> with the clientToken generated in Okta Workflows. *See the prerequisites section for more information.
The webhook body:

{
  "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}}"
	}
}

This is an example body. You may use other fields according to your needs. See the schema to the right of the screen to learn more about available data fields.

Headers
- You may supply the clientToken in the x-api-client-token header instead of passing it in the Invoke URL if you prefer.
Triggers - you may pick one or more triggers. Triggers correspond to Apono access request statuses:

Created
Approved
Rejected
Granted
Expired
Failed

Name - any name of your choosing. This will be displayed in the webhooks table.
Status - if you save the webhook as active, it can be triggered immediately. If you prefer, you may also save it as inactive and activate it later.
Optional: Test your webhook configuration. You should see Success as the response status.
Please note: The Test will send a mock event to your Okta Workflows.

Results

Your webhook should now start sending events payloads to the workflow once triggered.