Skip to main content Skip to complementary content

How Qlik Application Automation for OEM connects to your SaaS platform

Saas companies use Qlik Application Automation for OEM to scale the creation, deployment and management of native integrations for their customers. For example, a CRM company can use Qlik Application Automation for OEM to deploy a large number of native integrations between their own CRM platform and other cloud applications such as Sales tools, advertising tools, social media tools etc.

This article describes how the Qlik Application Automation for OEM platform interacts with your SaaS platform in order to enable these integrations for your customers.

We make a distinction between two main architectures, depending on if your SaaS platform has an API or not:

  • Your SaaS platform has an API: Scheduled and Triggered automations are used
  • Your SaaS platform does not have an API: your platform will make API calls to automations

Your SaaS platform has an API

This the classic architecture where automations (workflows) communicate with your platform using your API, as well as with one or more other platforms using their API as well.

As part of the onboarding process, Qlik Application Automation for OEM will add a connector to your platform, based on your existing API. See API requirements to add your Connector onQlik Application Automation for OEM for more information.

The automations are scheduled or run on a trigger (webhook). In both cases, you could say that the automation is a middleware that takes care of all the required data synchronization. The automation will e.g. read data from your platform (for example recently created and updated contacts) and it will send data to another platform.

Connecting platforms through Blendr.

an automation will connect itself to the API of your SaaS platform and the API of another cloud application.

Your SaaS platform does not have an API

If your SaaS platform does not have an API, you can call automations using their API endpoint. This architecture means that the execution of automations is orchestrated from your platform and that you e.g. post data to the automations and/or get the response from the Blend.

Inside the Blend, API calls are made to other cloud platforms, using their API's.

Making an API call to another platform.

Your SaaS platform makes API calls to an automation. The automation receives an input JSON, connects to an API of another cloud application, and sends a response JSON back to you.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!