Connecting to SaaS applications

You can land or replicate data from a large number of SaaS applications in Qlik Talend Data Integration.

To see all supported applications, go to Supported SaaS applications.

Limitations and considerations of SaaS application connectors

When using a SaaS application connector, you should be aware of the following limitations and considerations:

General limitations and considerations

• It is not possible to use the same SaaS application connector for more than one task, regardless of the task type

• Replication of LOB columns is not supported

• JSON column payloads in source datasets are not denested automatically on the target. The full fidelity of the source data is preserved: Nested and semi-structured content is delivered as native JSON for targets that support it, or as VARCHAR for those that do not.

SaaS application Lite connectors

A small number of SaaS application connectors are categorized as Lite connectors. Lite connectors are marked with a Lite label, both in the UI and in the help.

Qlik may initially develop some connectors for a specific use case and then release them with a Lite label. Lite connectors are fully supported by Qlik in accordance with Qlik’s Service Level Agreement (SLA) for critical issues related to data integrity, security, and reliability. The primary distinction between standard connectors and Lite connectors is that Lite connectors are tested against a limited set of use cases.

Change tables in landing and lake landing tasks

Typically, Change Tables are created only for source tables that support Change Data Capture (CDC). However, when the source is a SaaS application and the task type is Landing (data pipeline use case) or Lake Landing (replication use case), Change Tables are also created for tables that support only Full Load. This behavior is designed to address the increased likelihood of duplicate records when ingesting data from SaaS application sources. Duplicate records are added to the Change Tables before the data is propagated downstream, helping to ensure data quality and consistency.

Connecting to a SaaS application

Connecting to SaaS applications might require you to set up Data Movement gateway, depending on your use case. For more information, see When is Data Movement gateway required?.

1. The first step of connecting to a SaaS application is to add a connection to the data source. You can do this in several ways.

   • In Connections, click Create connection.

   • Click Create connection where source connections are listed (for example, in the data task setup wizard).

   Select Application in Category to filter the list of connectors to SaaS application connectors.

   You can also select from recently used connectors.

2. Select which application to connect to.

3. Complete the connection details to authenticate the connection. The connection details and authentication process are different for each SaaS application.

   For more information, go to Connecting to SaaS applications and select your data source.

   Warning noteIf you are using Data Movement gateway and need to create a new task with a SaaS application connector, you must upgrade to Data Movement 2025.11.66 or later. Otherwise, the task will not run.

After you have configured your connection, you can use that connection in a pipeline project.

Refreshing the metadata after new columns are added

When new columns are added to a SaaS application source after a task is already running, you need to refresh the metadata to prevent data loss.

To do this:

1. Open and re-save the connection.

2. Prepare the task as described in Creating and managing data pipeline projects.