Skip to main content Skip to complementary content


Webhooks are a way of triggering an action in one application when something happens in another application. Qlik Application Automation for OEM supports Webhooks in various ways.

Incoming webhooks

Example: you want to configure a Webhook in your CRM to trigger an action in Qlik Application Automation for OEM when a new lead is created. This can be accomplished by creating an automation and calling the automation via its API endpoint URL.

For more information see: Calling an automation via a webhook URL (REST API endpoint)

Outgoing webhooks

Example: you want to call a Webhook URL from another system, inside an automation inQlik Application Automation for OEM. This can be accomplished by using a block of type Call URL inside your Blend.

Alternatives to Webhooks

Webhooks are often used to sync data, e.g. a Webhook On new lead in a CRM is used to make sure that lead is also created in another system.

In some cases, Webhooks are not optimal (e.g. for large amounts of data), not desired or simply not supported. Webhooks also does not support replay. For example, it's impossible to use a Webhook to push existing leads from your CRM to another system. Webhooks can typically only be used for new data.

Here are some alternatives to consider when a Webhook is not possible:

Create a scheduled automation that runs e.g. every 15 minutes or every hour. In the automation use a block of type List new records incrementally - only once. This block will retrieve only new records on each run.

For more information see: Process new data incrementally You can also schedule an automation that retrieves all data and schedule it to run e.g. once a day. Inside the Blend, you can add logic to check if individual records already exist in the destination platform, and insert or update records accordingly.