Prerequisites
The connector should already be set up, with a Connector Profile and a Linked Account. See Getting Started on the Qlik connector page.How StackOne sets up Qlik webhooks
Nothing needs configuring in Qlik Cloud. When you connect a Qlik account with events enabled, StackOne creates a tenant-level webhook automatically and deletes it again when the connection is removed. A single subscription covers every event you enable.
Confirm the account has tenant admin rights
The user who authorizes the connection must be a tenant administrator. Without that, StackOne cannot create the webhook and events will not be delivered.
Find the webhook in Qlik if you need to check it
The subscription StackOne creates is named StackOne and appears in the webhooks section of the Qlik Cloud administration area. Leave it alone — StackOne manages its whole lifecycle and removes it when the connection is deleted.
- The address StackOne registered is also shown read-only as Native Webhook URL on the linked account.
Available webhook events
The following Qlik Cloud events can be enabled. Only events selected in StackOne are included in the subscription — Qlik sends nothing for events that are not subscribed.
Enable app events
Events covering analytics apps and their data.
- App Created (
com.qlik.v1.app.created) — Fired when an app is created. - App Deleted (
com.qlik.v1.app.deleted) — Fired when an app is deleted. - App Published (
com.qlik.v1.app.published) — Fired when an app is published to a managed space. - App Exported (
com.qlik.v1.app.exported) — Fired when an app is exported. - App Data Updated (
com.qlik.v1.app.data.updated) — Fired when an app’s data is updated. - App Reload Finished (
com.qlik.v1.app.reload.finished) — Fired when an app reload finishes, whether it succeeded or failed.
Enable reload events
Events covering reload execution.
- Reload Finished (
com.qlik.v1.reload.finished) — Fired when a reload finishes. Carries the reload, the app it belongs to and any error detail.
Enable automation events
Events covering automations and their runs.
- Automation Created (
com.qlik.v1.automation.created) — Fired when an automation is created. - Automation Updated (
com.qlik.v1.automation.updated) — Fired when an automation is updated. - Automation Deleted (
com.qlik.v1.automation.deleted) — Fired when an automation is deleted. - Automation Run Started (
com.qlik.v1.automation.run.started) — Fired when an automation run starts. - Automation Run Ended (
com.qlik.v1.automation.run.ended) — Fired when an automation run finishes successfully. - Automation Run Failed (
com.qlik.v1.automation.run.failed) — Fired when an automation run fails.
Enable user events
Events covering user accounts in the tenant.
- User Created (
com.qlik.v1.user.created) — Fired when a user is created. - User Deleted (
com.qlik.v1.user.deleted) — Fired when a user is deleted.
Enable data integration and API key events
These require features that not every tenant has. Data integration task events need Qlik Data Integration, and the API key event needs API keys enabled on the tenant. They are delivered where those features are available.
- Data Integration Task Started (
com.qlik.v1.di-projects.di-tasks.started) — Fired when a data integration task starts. - Data Integration Task Completed (
com.qlik.v1.di-projects.di-tasks.completed) — Fired when a data integration task completes. - Data Integration Task Failed (
com.qlik.v1.di-projects.di-tasks.failed) — Fired when a data integration task fails. - Data Integration Task Stopped (
com.qlik.v1.di-projects.di-tasks.stopped) — Fired when a data integration task is stopped. - API Key Validation Failed (
com.qlik.v1.api-key.validation.failed) — Fired when validation of an API key fails.