How to use and configure Webhooks to keep your master data in sync?

How to use Webhooks?

When it comes to master data, it is important to keep your data in sync across your services and applications. Monkey Master Data is especially designed to assist you handling this by triggering external Webhooks on inserts or updates (even on specific fields). When fully implemented, an update in a Consumer-record (e.g. User, Customer, etc.) will trigger external Webhooks which are pre-configured via our API.

Your custom ‘job’ (which is triggered by Monkey Master Data) will then receive the updated record and process it accordingly.

TIP: When you’re on Azure, we recommend using Azure Logic Apps. An instruction video can be found here.

Each service or application will basically has two ‘jobs’:

  • Inbound: one job will insert or update data via our API when data is produced
  • Outbound: another job will be triggered upon changes by Monkey Master Data

A service or application that doesn’t produce or modify data, will only need a single (outbound) job. A batch-oriented service may use the read-only subscription key to fetch data based on the @modifiedsince query parameter.

How to configure Webhooks?

It is very easy to configure Webhooks via our API. A few examples can be found in our Postman Collection.

Start by specifying the name of the entity and which fields our change detection mechanism will monitor for any changes (or use ‘*’ to select all fields). Now give it a proper description and add the URI. Optionally you can also specify a HeaderKey and HeaderValue when required. You’re ready to go!

If you have any questions, feel free to contact us. We’re happy to help!