Adding webhooks

In Oomnitza, you create the webhook which will be triggered when an event occurs in a vendor application. 

Before you start

Read the Process for creating webhooks in the Authenticating webhooks: Header secret and HMAC secret article.

Procedure

1. Click Configuration.
2. From the Integrations menu, click Webhooks. A list of the webhooks that were created is displayed.
3. Click Add webhook . A list of the vendor applications and their presets are displayed.
4. Select a preset.
5. On the Configuration Details page, complete the following steps:
   1. Add a unique name for the webhook.
   2. Depending on the type of authentication that is supported by the vendor application, you must enter or paste a a secret into the Header Secret or the HMAC Secret field.
      • Header Secret. In the Header Secret field, enter a string value. Type the secret in a text editor before you enter it because you will need it when you create the event hook. The secret you enter in the Header Secret field for the Oomnitza webhook must match the secret you enter for the event hook in the vendor application. In this case, create the Oomnitza webhook first and ensure you keep a copy of the Header Secret and when the Oomnitza webhook is created a copy of the webhook URL.
      • HMAC Secret. You must copy the secret that is generated when the event hook is created in the vendor application and paste it into the HMAC Secret field on the Configuration Details page for the webhook. In this case, have both applications opens - Oomnitza and the vendor application - so you can switch between screens to enter the required information.   
   3. Select an Oomnitza event such as create, update, or archive user.
   4. Optional. Modify the body of the preset. You can use Jinja templating to manipulate the data sent by the vendor application or to add additional fields and values to Oomnitza records when an event is triggered.
   5. Click NEXT.
   6. By default a sync key has already been added. You can add two or more sync keys to ensure that records aren't skipped if a sync key doesn't contain a value. 
6. Click SAVE.