Webhooks: Overview

You can create webhooks in Oomnitza that update records when events occur in vendor applications.

This means that you don't have to wait for Oomnitza to sync with the vendor application to update records when critical changes occur in vendor application records which improves data accuracy and operational efficiency.

For example, an HR vendor or identity provider (IdP) application like Okta syncs once daily with Oomnitza. You can, of course, change the frequency of the schedule to hourly, but that might impact performance. Instead, or in addition to, you can create webhooks in Oomnitza that trigger record updates for business-critical events when they occur.

Let's say you run Oomnitza's onboarding workflow when a user record is added to Oomnitza. You don't want to wait for Oomnitza to sync with your IdP, such as Okta, so you create a new user event hook In Okta and a webhook in Oomnitza. When a user is added to Okta, Oomnitza adds the record to Oomnitza and the onboarding workflow is triggered.

You can create Oomnitza webhooks for the following HR and IdP vendor applications:

• BambooHR
• Okta
• OneLogin 

Oomnitza webhooks can be triggered for the following types of Oomnitza events:

• Create user
• Update user
• Archive user

Important
You must create the event hooks in the vendor applications. An example of providing a deactivate hook event and deactivate webhook for Okta is provided in the tutorial Deactivating Okta users in Oomnitza.