Embedding scenarios for SaaS partners

The Qlik Application Automation for OEM Integration Hub for SaaS partners can be embedded in the SaaS platform of the partner using various scenarios.

Scenario 1: Link to your Hub

Add a link e.g. My integrations and link to your branded Hub:

Linking to your branded Hub.

An example of a branded hub with links to other services.

In this scenario, your customers will have to sign up on the hub (create a new account) before they can activate integrations. As part of the setup of integration, they will also have to link your platform, by entering e.g. an API key or by using oAuth.

You can choose what your Hub looks like, which home page to use (e.g. custom HTML or a list of integrations) etc.

Scenario 2: Link to your Hub with SSO (single sign-on)

In this scenario, you also link to your Hub as above, but SSO is applied so the user does not have to create an account on the Hub.

See SSO integration for more information.

Opening your integrations.

The My Integrations button opens your app as a pop-up.

Scenario 3: Embed using iframe with SSO (single sign-on)

In this scenario, the Hub is embedded using an iframe, with the general SSO link:

Embedding the Hub using an iframe.

The My Integrations button opens your app within the page.

Scenario 4: Embed using server-side code

In this scenario, you use the Qlik Application Automation for OEM API for SaaS partners to retrieve a list of integration templates and active integrations per account, and you implement these screens server-side in your own code:

Embedding the Hub using server-side code.

The My Integrations button shows a list of current integrations.

Adding an integration.

The My Integrations button shows a list of integrations that can be added.

Please note that for the Setup of an individual integration, and to access the Settings of an active integration, you still link to the white-label web page fromQlik Application Automation for OEM. This web page can be opened in a popup or embedded in an iframe.

The Qlik Application Automation for OEM SaaS Partner API can be used to retrieve the guid's of individual templates available for your customers, as well as the guid's of active integrations of one specific customer.

You can use these guid's in a deep link SSO URL, to link directly from your UI to one specific template or active integration from a customer. See the paragraph Direct SSO link to one specific integration in the article on SSO for more information.

Use a direct SSO link to an integration template so the user can activate it and start the Setup Wizard. Use a direct SSO link to an active integration so the user can access the Settings of the integration.

Example of embedded Settings of an active integration:

Integration settings.

Integration settings. The integration can be enabled, disabled, reconfigured, have its history shown, or be deleted.

Example of an embedded Setup Flow for a new integration:

Selecting a connector.

Step 1 of 3. A connector must be selected.

Authorizing a connector.

Step 1 of 3. The connector must be authorized.

Logging in to the connector.

Syncing historical leads.

Step 2 of 3. Enter whether you want to sync historical leads.

An active integration.

Step 3 of 3. The integration is now active.

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!

Leave your feedback here