Event Hooks
Receives real-time event data from Okta via webhooks for immediate security monitoring and incident response.
Sync Type: Push (Webhook)
Overview
This input receives events directly from Okta via their Event Hooks feature, providing real-time data ingestion instead of polling the Okta API. Events are pushed to Monad as they occur in your Okta tenant.
Prerequisites
- Okta account with administrative privileges
- Monad API key (API Key Requirements)
Setup
Step 1: Create the Input in Monad
- Create an Okta Event Hooks input and add it to a pipeline.
- Copy the Pipeline ID from the pipeline details page.
Step 2: Configure the Event Hook in Okta
- Log into your Okta Admin Console.
- Navigate to Workflow > Event Hooks.
- Click Create Event Hook.
- Fill in the following details:
- Name: Enter a name for the event hook (e.g., "Monad Event Hook")
- URL:
https://<pipeline-id>.data.monad.com(replace<pipeline-id>with your Pipeline ID) - Authentication field:
Authorization - Authentication secret:
ApiKey {api-key}(replace{api-key}with your Monad API key) - Custom header fields: Leave blank (additional headers will be ignored)
- Subscribe to events: Select the events you want to send to Monad
- Click Save & Continue.
- Click Verify to confirm the connection is working.
Self-hosted deployments
A per-pipeline ingest host needs the *.data.<your Monad domain> wildcard in place: a DNS record plus a matching certificate SAN. Monad Cloud has this. A self-hosted deployment has it only if whoever installed Monad set it up, so check with them if you are not sure. See Customer Helm Install for the setup.
Without it, send exactly the same request to your own Monad hostname, with the pipeline ID in the path:
https://<your-monad-host>/api/v2/http/send/<pipeline-id>
Authentication, request body, and responses are the same either way.
Important Notes
- Okta event hooks are sent in batches with multiple events at the JSON path
data.events. Monad processes each event in the batch individually.
Related Articles
Sync frequency
This is a push (receiver) input: Monad ingests records as the source sends them, so there is no polling interval. See Input Sync Frequency for details.