> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/destinations/categories/dashboards/qlik-sense.md).

# Qlik Sense

Learn how to connect Coupler.io to Qlik Sense, automate data imports, and build dashboards with data from apps, databases, and spreadsheets.

Qlik Sense is Qlik's business intelligence platform for building interactive dashboards and analytics apps. It connects to a wide range of data sources, but pulling from marketing, sales, or analytics tools usually means building a custom connector or exporting files by hand — that's where Coupler.io comes in.

With Coupler.io as the bridge, you can send data from any supported source into Qlik Sense through its built-in REST connector using a single integration URL. No custom connector development, no manual exports.

## Why use Qlik Sense as a Coupler.io destination?

* **Any source, one app** — send data from Google Ads, Facebook Ads, HubSpot, Shopify, Airtable, and dozens of other sources into a single Qlik Sense app
* **Uses Qlik's native REST connector** — nothing to install on the Qlik side; the connection is standard functionality
* **No coding required** — the integration is URL-based, so you paste one link into Qlik Sense and your data appears
* **Automatic refresh** — schedule Coupler.io to run on a recurring basis, then schedule your Qlik reload after it, keeping apps current without manual work
* **Combine before you load** — use Coupler.io's Join, Append, Aggregate, and SQL transformations so Qlik receives a single prepared table instead of several raw feeds

## Prerequisites

* A Qlik Sense account with permission to create data connections
* A Qlik space to create the connection in — your Personal space works, or a shared space if you want colleagues to reuse the connection

## Quick start

{% hint style="success" %}
Run your data flow before you set up the connection in Qlik Sense. The integration URL returns no data until the first run has completed successfully, and a connection tested against an empty URL will look broken when it isn't.
{% endhint %}

## How to connect

{% stepper %}
{% step %}

## Create a data flow and add your source

In Coupler.io, create a new data flow and connect the source you want to pull data from — for example, Facebook Ads, GA4, or Shopify. Configure the entity and any filters or date ranges you need.
{% endstep %}

{% step %}

## Select Qlik Sense as your destination

In the Destinations step of your data flow, choose **Qlik Sense** from the list.
{% endstep %}

{% step %}

## Choose the data set to share

Under **Data set to share**, pick the data view you want to send to Qlik Sense. If your flow has several prepared views, click **Change** to select a different one.
{% endstep %}

{% step %}

## Follow the steps in the setup wizard

{% stepper %}
{% step %}
Login into [Qlik Sense ](https://www.qlik.com/us/products/qlik-sense)
{% endstep %}

{% step %}
Select "+ Create" 
{% endstep %}

{% step %}
Click the "+" in the "Data connection" tile 
{% endstep %}

{% step %}
Search for "REST" and select it
{% endstep %}
{% endstepper %}
{% endstep %}

{% step %}

## Generate the Integration URL and wait for the flow to complete it's first run

Coupler.io will generate a unique integration URL for this data flow. The data flow will auto-run to populate the link that you just generated.
{% endstep %}

{% step %}

## Copy your integration URL

The URL looks like this:

```
https://app.coupler.io/export/w/<data-flow-id>.json?access_token=<token>
```

{% endstep %}

{% step %}

## Create a REST data connection in Qlik Sense

Log in to Qlik Sense, click **+ Add new**, and choose **Data connection**. In the **Add data connection** dialog, pick a **Space**, search the data sources for `REST` and select the **REST** tile.
{% endstep %}

{% step %}

## Paste the URL into Qlik Sense

In the REST connection form paste the integration URL into the **URL** field. Leave **Method** set to `GET`. The **Name** field fills in automatically from the URL — you can rename it to something readable, such as `Coupler_FacebookAds`, so you can identify it later.
{% endstep %}

{% step %}

## Create and analyze

Click **Test connection** to confirm Qlik can reach the endpoint, then click **Create** to save the connection.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
The Qlik REST connector defaults to a 30-second connection timeout and a 300-second read/write timeout. Large exports can take longer than that to transfer — if the connection times out on a big data set, raise the read/write timeout before assuming the URL is at fault.
{% endhint %}

## Keeping your app up to date

The integration URL is stable: it stays the same across runs while the data it serves updates each time your data flow completes. That means you set the connection up once in Qlik Sense and never touch it again.

To keep the app current, schedule both sides:

{% stepper %}
{% step %}

## Set a refresh interval on the Coupler.io data flow

The shortest available interval depends on your plan — manual runs only on Free, daily on Starter and Active, hourly on Pro, and every 15 minutes on Agency & Enterprise.
{% endstep %}

{% step %}

## Schedule your Qlik Sense reload

Schedule your Qlik Sense reload to run *after* the Coupler.io run is expected to finish. Allow at least 5-10 minutes depending on your source, so Qlik doesn't reload against data that's still being written.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
The integration URL contains an access token, so treat it like a password. If it's ever exposed, click **Update** next to the Integration URL field to generate a new one — but note that this invalidates the old URL, and any Qlik Sense connection still using it will stop returning data until you paste in the new link.
{% endhint %}

## Supported features

| Feature              | Supported |
| -------------------- | --------- |
| Replace mode         | Yes       |
| Append mode          | No        |
| Automatic scheduling | Yes       |
| Type enforcement     | No        |
| Templates            | No        |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.coupler.io/destinations/categories/dashboards/qlik-sense.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.