Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Analytics & AI
Forums for Qlik Analytic solutions. Ask questions, join discussions, find solutions, and access documentation and resources.
Data Integration & Quality
Forums for Qlik Data Integration solutions. Ask questions, join discussions, find solutions, and access documentation and resources
Explore Qlik Gallery
Qlik Gallery is meant to encourage Qlikkies everywhere to share their progress – from a first Qlik app – to a favorite Qlik app – and everything in-between.
Qlik Community
Get started on Qlik Community, find How-To documents, and join general non-product related discussions.
Qlik Resources
Direct links to other resources within the Qlik ecosystem. We suggest you bookmark this page.
Qlik Academic Program
Qlik gives qualified university students, educators, and researchers free Qlik software and resources to prepare students for the data-driven workplace.
Recent Blog Posts
-
Upcoming Qlik Sense Enterprise on Windows Oracle Essbase Connector End of Life i...
The Oracle Essbase for Qlik Sense Enterprise on Windows (client-managed) connector will reach end of life and is therefore no longer recommended for u... Show MoreThe Oracle Essbase for Qlik Sense Enterprise on Windows (client-managed) connector will reach end of life and is therefore no longer recommended for use.
When will the connector reach end of life?
The Essbase Connector will reach end of life beginning with the Qlik Sense Enterprise on Windows May 2027 release and will no longer be included in the installation package.
Earlier Qlik Sense Enterprise on Windows releases that still include the Oracle Essbase connector are unaffected by this change and continue to be supported according to their normal lifecycle.
What does that mean for me?
Applications and data connections using the Oracle Essbase connector will stop working once an environment is upgraded to the Qlik Sense Enterprise on Windows May 2027 release. As a workaround, Qlik Sense Enterprise on Windows supports connecting to systems that offer a REST API using the Qlik generic REST connector. Essbase exposes a REST interface that can be used as an alternative way to bring the same data into your applications.
We're happy to assist with any follow-up questions. Reply to this blog post or take your queries to our Support Chat.
Thank you for choosing Qlik,
Qlik Support -
ODBC Connector for Qlik Sense Enterprise on Windows: Upcoming End of Support for...
Effective in the Qlik Sense Enterprise on Windows November 2026 release, and in the latest patches for May 2025, November 2025, and May 2026, the ODBC... Show MoreEffective in the Qlik Sense Enterprise on Windows November 2026 release, and in the latest patches for May 2025, November 2025, and May 2026, the ODBC connector used by Qlik Sense Enterprise on Windows will no longer support connections secured with TLS 1.0 or TLS 1.1. To maintain uninterrupted connectivity, customers should upgrade their environments to use TLS 1.2 or higher ahead of applying these releases or patches.
The changes are expected after October 28th, 2026 and will be communicated in the respective release notes.
Why is this happening?
TLS 1.0 and TLS 1.1 are legacy encryption protocols that are no longer considered secure and have been deprecated across the industry for several years. Removing support for these older protocols in the ODBC connector aligns Qlik's connectivity stack with current security standards and reduces exposure to known vulnerabilities in outdated TLS implementations.
Who is affected?
This change affects the ODBC connector in Qlik Sense Enterprise on Windows only. At this point, Qlik Sense Desktop and QlikView are not affected by this change. The standalone ODBC Connector (QvOdbcConnectorPackage.exe) remains unaffected for the time being.
Any data source connection made through the ODBC connector in Qlik Sense Enterprise on Windows that relies on TLS 1.0 or TLS 1.1 will be affected once support is removed, regardless of whether the TLS version is enforced by the data source itself, a network intermediary, or the client driver configuration.
What does this mean for me?
If your data source, ODBC driver, or the underlying operating system is currently configured to negotiate connections using only TLS 1.0 or TLS 1.1, those connections will fail once you move to a version of Qlik Sense Enterprise on Windows that removes TLS 1.0 or TLS 1.1 support.
Reload tasks, extensions, and any other workflows using affected ODBC connections will no longer be able to connect to the data source.
What should I do?
- Review and upgrade your environment so that all ODBC connections negotiate TLS 1.2 or greater before you upgrade Qlik Sense Enterprise on Windows.
- If you are not already using TLS 1.2 or later, recreate the connection with the updated TLS configuration.
Questions?If you have questions or need assistance planning your upgrade, our forums are open to you, and Support is only a chat away.
Thank you for choosing Qlik,
Qlik Support -
【10/27（火）- 28（水）開催】地⽅⾃治情報化推進フェア2026 に出展します！
Qlik は、ブースとシアターセッションで参加します！ 日本最大級の自治体向け情報システム展示会、「地方自治情報化推進フェア2026」では、自治体 DX やマイナンバーカードの利活用推進に資する最新の情報や取り組みをご紹介します。 Qlik は、パートナー企業の AWS ブース内にて、ブースとシアタ... Show MoreQlik は、ブースとシアターセッションで参加します！
日本最大級の自治体向け情報システム展示会、「地方自治情報化推進フェア2026」では、自治体 DX やマイナンバーカードの利活用推進に資する最新の情報や取り組みをご紹介します。
Qlik は、パートナー企業の AWS ブース内にて、ブースとシアターセッションで参加します。
自治体における DX 推進や生成 AI 活用、AWS との連携による、自治体業務の課題解決に向けた取り組みについてご紹介します。【開催概要】
日時：10/27（火）9:30 - 17:30
10/28（水）9:30 - 17:00会場：幕張メッセ国際展示場展示ホール 1 - 3
千葉県千葉市美浜区中瀬 2-1定員：事前登録制
主催：地方公共団体情報システム機構（J-LIS）
Qlik シアターセッション AWS ブース内 10/27（火）15:00-15:15
分析力より定着力。自治体データ利活用の鍵
自治体のデータ利活用の進み具合は様々ですが、可視化機能の不足よりもデータ整備や庁内ルール、人材・予算といった事情が課題になっていることが少なくありません。本セッションでは、公開・内部の使い分けから、データ整備・運用・ガバナンス・人材・コストまでをフォローする機能という観点から、生成 AI との連携も交え、Qlik がサポートするデータ利活用の一歩先を紹介します。
クリックテック・ジャパン株式会社
エンタープライズ営業部 エンタープライズアカウントマネージャー
村田 太郎 -
Important update on SAP Data Access Restrictions and your Qlik Integration: SAP ...
Dear Qlik Customers, In April 2026, SAP published a series of updates that will restrict your ability to extract certain SAP data using Qlik products.... Show MoreDear Qlik Customers,
In April 2026, SAP published a series of updates that will restrict your ability to extract certain SAP data using Qlik products. We are writing to explain what is changing, what it means for your Qlik integration, what you can do next, and how Qlik is responding.SAP Announcement
SAP has recently updated SAP Note 3255746 and its API Policy, which together prevent customers from using the ODP-RFC interface to perform bulk data extractions to non-SAP systems. Here is what you need to know.
Impacted Qlik Products:
The CDC connectivity via ODP will be at most risk by the implementation of the June 9th SAP security update, as it will be blocked. The main products affected are:
- Qlik Talend Cloud SAP ODP Connector
- Qlik Replicate SAP ODP Endpoint
Other impacted products that also offer ODP functionality are:
- Qlik Analytics (Qlik Sense / QlikView) SAP ODP Connector
- Talend Studio Component tSAPODPInput (see SAP ODP-RFC Changes: What Talend Studio Customers Need to Know)
- Talend Studio Component tSAPADSOInput using RFC-based access to Advanced DataStore Objects (ADSO), relying on the ODP API (see SAP ODP-RFC Changes: What Talend Studio Customers Need to Know)
The following Qlik Products do not use the ODP-RFC interface and therefore will not be impacted by the June SAP Security update:
- Qlik Gold Client
What's Changing and When:
- June 9, 2026: SAP released a security patch through SAP Note 3635619 blocking “unrestricted” calls from non-SAP applications, including affected Qlik connectors, that rely on the ODP-RFC interface. Depending on your SAP system’s component levels, your SAP System Administrator may apply the SAP Note independently or as part of an SAP Support Package (refer to SAP Note 3635619).
- Temporary revert option: According to SAP Note 3731818, there is an option to allow restricted ODP-RFC calls on systems with the security patch installed to proceed without interruption. Implementing SAP Note 3635619 will add an opt-out program which allows disables the ODP-RFC restrictions. SAP Note 3731818 also states that another SAP Note will be provided at the end of 2026 to permanently disable the opt-out program and reimplement the block on unrestricted ODP-RFC calls from non-SAP applications.
Recommended Next Steps
- Review the SAP Notes: Independently review SAP Note 3255746 (reclassification notice), SAP Note 3439624 (self-assessment tool), SAP Notes 3748819 and 3635619 (security patch for ODP-RFC), and SAP Note 3731818 (security patch opt-out program) via the SAP Support Portal at support.sap.com. Address your concerns and feedback through the appropriate SAP channels.
- Contract Review: Review your customer agreement and the API Policy, updated in April, 2026, to evaluate SAP’s ability to make unilateral changes to your data access rights, and to require additional purchases or charge egress fees.
- Audit your environment: SAP has released a self-assessment tool (SAP Note 3439624, available April 13, 2026) to help you identify all current ODP-RFC usage across your systems.
- The Qlik SAP ODP Connector will show as “unpermitted”, which means it will be blocked by the SAP June Security patch
- The Qlik SAP OData Connector will show as “permitted”, which implies it will continue to work with the SAP June Security
patch
- Evaluate Qlik’s Alternative SAP Connectors: Qlik supports several methods for SAP connectors, including OData and SAP Extractors. We continue to enhance our connectors and are looking to release a new SAP connector due later this year, which may prove a viable alternative.
- Work with Qlik: Reach out to your Qlik representative before implementing the SAP June Security patch, so we can partner with you on alternate Qlik solutions and ways to address these SAP restrictions. Together, we can evaluate your specific environment, understand your connectivity needs, and align on the best path forward before the December 2026 deadline.
Our Commitment
You should be in control of your business-critical data, wherever it creates value. Without interoperable architectures, SAP customers like you face higher costs, performance issues, and less freedom to choose, including loss of flexibility in implementing AI.
Qlik already supports alternatives to ODP and is actively developing additional migration paths and solutions to preserve your flexibility through this transition and beyond. We will continue to work on viable alternatives to our ODP endpoints and help you navigate this change on your terms, not SAP's. To learn more about how Qlik can support your specific environment, please reach out to your Qlik representative.
Additional Resources
- SAP’s Operational Data Provisioning (ODP) Update Public FAQ
- SAP Note 3255746 (reclassification notice) - Accessible via the SAP Support Portal at support.sap.com
- SAP Note 3439624 (self-assessment tool) - Accessible via the SAP Support Portal at support.sap.com
- SAP Note 3748819 and SAP Note 3635619 (security patch for ODP-RFC) - Accessible via the SAP Support Portal at support.sap.com
- SAP Note 3731818 (security patch opt-out program) - Accessible via the SAP Support Portal at
- support.sap.com
- “Open” on Whose Terms? What SAP Sapphire Won't Say. by Matt Hayes – Qlik GM Data Business Unit
- SAP ODP-RFC Changes: What Talend Studio Customers Need to Know Qlik Support article by Rodrigo Martins
This communication reflects Qlik's current interpretation of SAP's restrictions, which are outside our control and subject to change. Customers should consult SAP's official communications and seek independent guidance on operational and legal impact. Roadmap statements are forward-looking and not commitments; disruptions arising from SAP's decisions do not constitute a defect in Qlik's products or services.
-
【10/28（水）開催】金融カンファレンス「データと AI が支える金融ビジネス変革」に出展します！
10/28（水）開催：金融カンファレンス - データと AI が支える金融ビジネス変革 データと AI の活用が重要な経営戦略となる一方、多くの金融機関ではガバナンスの構築やAIエージェントの運用、AI 前提の組織への転換などさまざまな課題に直面しています。金融ビジネス変革を実現するためには、人と ... Show More10/28（水）開催：金融カンファレンス - データと AI が支える金融ビジネス変革
データと AI の活用が重要な経営戦略となる一方、多くの金融機関ではガバナンスの構築やAIエージェントの運用、AI 前提の組織への転換などさまざまな課題に直面しています。金融ビジネス変革を実現するためには、人と AI が協働する持続可能な推進体制を整えると共に、最新の IT テクノロジーやソリューションを積極的に取り入れていくことが求められています。
本イベントでは、基調講演にて株式会社みずほフィナンシャルグループよりデータ基盤・AI エージェント活用の考え方について、特別講演にて株式会社横浜銀行よりデータ・AI 活用の推進について具体的な事例と共にご紹介いただきます。
今すぐ申し込む【開催概要】
日時：10/28（水）14:00-18:15（受付開始 13:30）
17:45以降：ネットワーキング会場：JA 共済ビル カンファレンスホール
東京都千代田区平河町 2-7-9 JA 共済ビル定員：200 名（事前登録制）
主催：株式会社セミナーインフォ
-
【オンデマンド配信】Snowflake World Tour Tokyo 2026 の講演をプレイバック！
Qlik が Snowflake へのデータ統合と AI 活用を全方位でサポート エンタープライズ AI 戦略において、Snowflake 上のデータ基盤整備は急務となっています。本 Web セミナーでは、基幹システムからのリアルタイムのデータパイプライン構築、データ抽出コストを最適化できる Ic... Show MoreQlik が Snowflake へのデータ統合と AI 活用を全方位でサポート
エンタープライズ AI 戦略において、Snowflake 上のデータ基盤整備は急務となっています。本 Web セミナーでは、基幹システムからのリアルタイムのデータパイプライン構築、データ抽出コストを最適化できる Iceberg レイクハウス、分析とデータエンジニアリングをシームレスにつなぐ MCP サーバーをご紹介します。統合からインサイト創出まであらゆるデータから価値を生む AI 時代の最新アプローチをご紹介します。
今すぐ視聴するオンデマンド配信
AI エージェントに Qlik のすべてを － MCP サーバーで広がる Snowflake 活用
Qlik MCP Server は、Qlik のすべてを AI エージェントに解放する仕組みです。Snowflake Native App を通じて、CoWork や Cortex Agents から自然言語でのアプリ探索やダッシュボード操作、Declarative Pipelines では Snowflake へのパイプライン構築を実現します。分析とデータエンジニアリングを 1 つの AI の入り口でつなぐ新しい形を紹介します。
クリックテック・ジャパン株式会社
ソリューション技術部 シニアソリューションアーキテクト
阿部 智師
Qlik Open Lakehouse - Snowflake 上で構築する Iceberg ベースのレイクハウス基盤
SAP やメインフレームなど複雑な基幹システムからのCDC によるリアルタイム統合、ノーコードでのデータ品質・変換ルール適用、AI SQL Assistant によるクエリ生成、Trust Score とリネージで裏付けられた信頼できる AI-Ready なデータ基盤構築をデモでご紹介します。加えて、Iceberg レイクハウスが実現する大量データの抽出におけるコストの最適化、2.5 倍のデータ鮮度、Snowflake へのゼロコピー連携もご紹介。コスト常識を塗り替えます。クリックテック・ジャパン株式会社
ソリューション技術部 プリンシパルソリューションアーキテクト
中嶋 翔 -
QlikView Internet Explorer (IE) Plugin to be removed in the QlikView September 2...
Internet Explorer (IE) was retired by Microsoft in 2022 and no longer receives security updates. In line with this, Qlik will stop shipping the QlikVi... Show MoreInternet Explorer (IE) was retired by Microsoft in 2022 and no longer receives security updates. In line with this, Qlik will stop shipping the QlikView IE plugin starting with the QlikView September 2027 release.
What this means for you:
- This announcement only impacts QlikView. No other Qlik products are affected
- If you remain on your current QlikView installation (such as the QlikView September 2026 release or earlier) and do not upgrade, nothing changes for you; the plugin remains operational
- Once you upgrade to the QlikView September 2027 release or any later releases, the QlikView IE plugin will no longer be included in your installation package, nor will any support be provided to enable older versions of the plugin
While you may choose not to move to the QlikView September 2027 upgrade and remain on an older version, your eligibility for maintenance and support may be impacted. Qlik supports versions for 24 months from the initial release date in accordance with its release management policy.
How can you access QlikView without the IE Plugin:
- The standard QlikView Web Client works in any modern web browser and requires no plugin. If you're already using the Web Client, which most customers are, this change has no impact on you.
- QlikView Desktop provides a direct connection to QlikView Server and will continue to work as normal.
What you need to do:
You are encouraged to stay on a supported version and explore one of the options below, if you are impacted:
- Check whether any of your users still rely on the IE plugin, rather than the Web Client or Desktop options.
- If so, move them to the Web Client (recommended for most cases) or set up a direct QlikView Desktop-to-Server connection before upgrading to the QlikView September 2027 release or later.
- Contact your account team or Qlik Support if you need help identifying affected usage or planning the move.
Thank you for choosing Qlik,
Qlik Support -
Knowledge Nuggets-2026Q3
Knowledge Nuggets-2026Q3 Insight Consulting A collection of Qlik and Data & AI Literacy related videos and articles, updated to Sept 2026 ... Show MoreKnowledge Nuggets-2026Q3Insight Consulting
A collection of Qlik and Data & AI Literacy related videos and articles, updated to Sept 2026
Discoveries
Contributor and Keywords frequency
Impact
Learning resource
Audience
All Qlik stakeholders
Data and advanced analytics
Learning resource
-
Qlik Open Lakehouse on Google Cloud Platform
Private Preview · Google Cloud Qlik Open Lakehouse comes to Google Cloud Sign up for the Private Preview and get hands-on with real-time Iceberg ta... Show MorePrivate Preview · Google CloudQlik Open Lakehouse comes to Google Cloud
Sign up for the Private Preview and get hands-on with real-time Iceberg tables in your own Google Cloud project — no lock-in, no re-architecting.
If you're running analytics on Google Cloud, you already know the tension. BigQuery is fast and familiar, but the more data you pour into it, the more your ingestion and storage bill climbs, and the more your data ends up shaped around one engine. You want the performance without the lock-in, you want your data to stay yours, and you want to free up some budget for more valuable workloads.
That's exactly the problem Qlik Open Lakehouse solves — and we're getting ready to launch a Private Preview on Google Cloud this September that you can be part of.
Qlik Open Lakehouse gives you a fully managed way to ingest real-time data straight into Apache Iceberg tables that live in your own Google Cloud Storage buckets. No proprietary formats, no copies, no re-architecting your data layer. Query those same tables from BigQuery, Trino, or any Iceberg-compatible engine, and pay a fraction of what you'd normally spend moving and storing that data.
If you've followed our work on AWS, this will feel familiar — and that's the point. We're porting a proven architecture to Google Cloud, not building a science experiment.
How it works: a walk through the architecture
Open Lakehouse builds the bronze layer of your medallion architecture, ingesting and landing real-time data as optimized Apache Iceberg tables, with the heavy lifting executed in your own Google Cloud project. From there, push-down transformations in Qlik Talend® Cloud pipelines create your silver and gold layers directly on BigQuery. Here's the path your data takes, stage by stage.
1 · Ingestion at the edge
Your sources land through two paths. For change data capture and bulk loads from databases, SAP, and mainframe systems, the Qlik Data Movement Gateway sits in your managed environment and handles CDC and bulk ingestion. For streaming and event data, you connect Kafka topics or Google Cloud Storage directly. Both routes feed the landing stage without your data ever leaving your control. Later in the Private Preview, we'll also add support for Qlik Replicate as a source, so if you're already a Replicate customer, you can onboard data from your existing CDC sources into Iceberg without migrating a single pipeline or switching tools.
2 · Compute in your project
Two components run on Google Compute Engine inside your environment. The Network Integration Agent runs on a standard Compute Engine VM and brokers secure connectivity between the Qlik Talend Cloud tenant and your resources. The Open Lakehouse Cluster — the engine that writes and optimizes your Iceberg tables — runs on a Compute Engine managed instance group built on Spot VMs. That Spot-based design is deliberate: it's where a large part of the cost savings comes from, because you're running the ingestion and optimization workload on Google Cloud's most cost-efficient compute instead of always-on, premium-priced infrastructure.
3 · Open storage you own
Everything lands in Google Cloud Storage, split across a landing bucket for incoming data, a config bucket for pipeline metadata, and table storage where your data comes to rest as Apache Iceberg tables. These buckets are in your account. The data is written in an open table format from the start, so there's never a moment where it's trapped in something only Qlik can read.
4 · A catalog any engine can use
Iceberg tables are registered in the Google Lakehouse runtime catalog, so your tables are discoverable and governable through Google Cloud's native catalog rather than a Qlik-proprietary one. That's what makes zero-copy querying real: BigQuery reads the same tables through ELT, and so can Trino or any other Iceberg-compatible engine, all pointing at one physical copy of the data.
5 · A managed bronze layer, ready to build on
The pipeline moves through managed stages — landing, storage, and mirror — to produce clean, governed Iceberg tables without you hand-coding each hop. You get Type 1 and Type 2 slowly changing dimensions or append-only patterns out of the box, so history and current-state tables are handled for you. We'll also add zero-copy mirroring to BigQuery during the Private Preview, so you can surface your Iceberg data straight in BigQuery. If you want to replace an existing native table, you can, since downstream queries keep working exactly as before.
The result: real-time data flows from your sources into governed, query-ready Iceberg tables in your own Google Cloud Storage, optimized continuously, queryable from BigQuery and beyond — and you never gave up control of a single byte.
Built on proven AWS foundations
We didn't start from zero for Google Cloud. Qlik Open Lakehouse first shipped on AWS, where it's already running these same patterns: CDC and streaming ingestion, Spot-based compute for cost-efficient optimization, Iceberg tables in customer-owned object storage, and open querying across engines.
Bringing it to Google Cloud is a deliberate step toward feature parity across clouds. The architecture mirrors what's proven on AWS, adapted to Google Cloud's building blocks: Compute Engine in place of EC2, Google Cloud Storage in place of S3, BigQuery and the Google Lakehouse runtime catalog as the native query and catalog layer. Same engine, same principles, GCP-native execution.
This matters because of what it says about our direction. We believe you should be free to choose where your data lives, which engine queries it, and to change your mind later without a migration project. Delivering the same open lakehouse capability across AWS and Google Cloud, with more to come, is how we make that freedom real rather than a slide in a pitch deck.
Why it matters
Everything above maps to three things we care about:
TRUSTBuild governed data products in Qlik Talend Cloud on top of your Iceberg tables. Your data stays in open Apache Iceberg format, in your own account.
FREEDOMQuery from BigQuery, Trino, or any Iceberg-compatible engine, and swap or add engines later without re-architecting. No lock-in to a single vendor or format.
COST OPTIMIZATIONSpot VM compute and zero-copy, single-storage architecture mean you spend far less to move and hold your data at scale.
Join the Private Preview
We're accepting participants now, and we're prioritizing organizations already standardized on Google Cloud and working with BigQuery or Apache Iceberg in their accounts.
Request your spot in the Private Preview →Opt in through the form and the Qlik team will reach out to schedule a welcome call. Already signed up? Sit tight — we'll be in touch.
-
Introducing the Region Mover capability in the Qlik Talend Cloud Migration Toolk...
The Region Mover, available with the Qlik Talend Cloud Migration Toolkit (QTCMT), enables users to migrate a Talend Cloud (TC) or Qlik Talend Cloud (Q... Show MoreThe Region Mover, available with the Qlik Talend Cloud Migration Toolkit (QTCMT), enables users to migrate a Talend Cloud (TC) or Qlik Talend Cloud (QTC) tenant to another Qlik Talend Cloud tenant while either remaining on Talend 7 or upgrading to Talend 8.
Before starting a migration, users can view the source tenant inventory directly in the Qlik Talend Cloud Migration Toolkit. This provides visibility into the currently existing assets and those available for migration.
The migration is organized into three steps:- Administrative assets: Users, groups, projects, and user/group authorizations
- Talend projects: Package and push artifacts, upgrade code to Talend 8, generate CVE reports, and upload artifacts to Nexus 3 or JFrog Artifactory
- Runtime assets: Tasks, task artifacts, task parameters, task triggers, and plans
For questions or assistance, please contact Qlik Support.
Why Use Region Mover?
There are several scenarios where customers may need to move assets to a different region, including:
- A current region is no longer supported
- A move from Talend Cloud to Qlik Talend Cloud is required
- A newly available region was not previously an option and is now available
- Assets need to be consolidated from one tenant into an existing tenant
Region Mover enables faster migration, migrating assets to a new tenant more than 20x faster than performing the same migration manually, and significantly simplifies each migration step while giving you full control over exactly which assets get migrated.
Migration options include:
- Selecting specific assets for migration
- Choosing whether tasks should start automatically or remain paused by default
- Upgrading existing Talend 7 artifacts to Talend 8 using the included sandbox environment
Prerequisites and how to get started
- For all requirements, setup instructions, and details, see Region Mover | Qlik Talend Cloud Migration Toolkit Documentation
- Qlik Talend Cloud Migration Toolkit R2026-08 or later is required
Download
Download the latest release from the Migration Center page on Qlik Help.
Thank you for choosing Qlik,
Qlik Support -
Qlik Digest - Data Edition - September 2026
Stay a Step Ahead This issue is about staying ahead of the curve and getting more from what you're already running. Read on for this month's best ins... Show MoreStay a Step Ahead
This issue is about staying ahead of the curve and getting more from what you're already running. Read on for this month's best insights and resources.
In this issue
Think Ahead - What is actually stalling agentic AI, and it is not the models. Insider Tip - Build a governed data product without hand-coding the pipeline. Customer Spotlight - 83% fewer platforms to maintain, and the developers got their week back. Tune In - Cut your Talend migration planning from weeks to hours.Think AheadThe State of Agentic AI Has Arrived
We asked 200+ enterprise leaders what stalled their agentic AI rollouts. The blocker was not the models, it was the data feeding them, so if agentic AI is on your roadmap, you need to read this first.
Read the State of Agentic AI →Insider TipDescribe the Pipeline. Let the Agents Build It.
Steffen Bischoff takes one dataset from core system to governed data product, versioned in Git and quality-checked by agents. The example is insurance data, but the pattern works on whatever source you run.
Watch the Walkthrough →Customer SpotlightHow AriensCo Cut 83% of Its Data Platforms and Got Its Developers Back
83%Fewer PlatformsOnboardingWeeks Down to DaysDevelopersBack on Real WorkConsolidating on Qlik Talend took AriensCo's partner onboarding from weeks to days, proof it doesn't have to stay that way for any team maintaining more integration tools than it can name.
See How AriensCo Did It →Tune InMeet the Luminaries
Congratulations to the 2026-2027 class of Qlik Luminaries: leaders shaping Qlik's future through real-world insights, product influence, and advocacy.
Meet the 2026 Luminaries → -
Qlik Digest - Analytics Edition - September 2026
Stay a Step Ahead This issue is about staying ahead of the curve and getting more from what you're already running. Read on for this month's best ins... Show More
Stay a Step Ahead
This issue is about staying ahead of the curve and getting more from what you're already running. Read on for this month's best insights and resources.
In this issue
Customer Spotlight - Valpak made its reporting something customers trust and pay for. Think Ahead - What is actually stalling agentic AI, and it is not the models. Insider Tip - Get early access to what's coming next in Qlik. See It in Action - Stop building that monthly order list by hand, let AI do the work.Customer SpotlightHow Valpak Turned Compliance Reporting Into Something Customers Trust
FasterESG ReportingLowerCompliance CostValpak's customers now ask packaging and ESG questions in plain language instead of compiling the data themselves, a pattern that works for any team fielding the same report requests every month.
See How Valpak Did It →Think AheadThe State of Agentic AI Has Arrived
Qlik asked 200+ enterprise leaders what stalled their agentic AI rollouts. The blocker was not the models, it was the data feeding them, so if agentic AI is on your roadmap, here's what you need to read first.
Read the State of Agentic AI →Insider TipGet Early Access to What's Coming Next in Qlik
Try upcoming features before everyone else, so you're ready to use them the moment they launch, not scrambling to catch up.
Explore Public Previews →See It in ActionMeet the Luminaries
Congratulations to the 2026-2027 class of Qlik Luminaries: leaders shaping Qlik's future through real-world insights, product influence, and advocacy.
Meet the 2026 Luminaries → -
Declarative Pipelines in Qlik Talend Cloud
Check out this great video on Declarative Pipelines in Qlik Talend Cloud created by @Michael_Tarallo. In this video, Mike shows how you can go from i... Show MoreCheck out this great video on Declarative Pipelines in Qlik Talend Cloud created by @Michael_Tarallo. In this video, Mike shows how you can go from intent to a working data pipeline using a declarative, code-driven approach, leveraging Claude Code, VS Code and Qlik Talend Cloud to generate the YAML and supporting files needed to define your pipeline. You’ll see the basic workflow from prompt → generated pipeline definition → Qlik Talend Cloud, without spending 30 minutes getting there. Perfect if you want a fast introduction to how AI-assisted, agentic data engineering can help accelerate pipeline development.
Learn more here: https://community.qlik.com/t5/Do-More...
Thanks,
Jennell
-
Qlik がエージェンティックデータエンジニアリングの一般提供を開始（Qlik Blog 翻訳）
ブログ著者：Matt Hayes本ブログは「Qlik Agentic Data Engineering is Generally Available. Here's What That Actually Means.」の翻訳になります。 4月に米国で開催された「Qlik Connect」の際、チー... Show Moreブログ著者：Matt Hayes
本ブログは「Qlik Agentic Data Engineering is Generally Available. Here's What That Actually Means.」の翻訳になります。4月に米国で開催された「Qlik Connect」の際、チームがパイプライン構築を超えて、自律的な AI エージェントを活用できる、信頼できるデータ基盤の設計へと向かっているという変化について、ブログを投稿しました。
そして現在、Qlik は、データチームがこの変化を認識する段階から、実際に運用する段階へと進むための支援を行っています。エージェンティックデータエンジニアリングの各機能が、Qlik Talend Cloud® において一般提供されました。
エージェンティックデータエンジニアリングは、2026年を象徴する話題の 1 つです。Gartner 社が 2026年 2月に発表した「Top Trends in Data & Analytics」レポートでは、2029年までに、適応性があり状況を認識する AI エージェントによるエージェンティックデータマネジメントが、データエンジニアリングのワークフローの 75% を自動化し、より価値の高い業務にリソースを解放すると予測されています。
この予測こそ、Qlik と今回のリリースが実現するものです。そして、私たちがデータを AI のために機能させているというもう一つの証明でもあります。
無料トライアルを試す一般提供を開始した製品
データエージェント
Qlik は、2026年 2月にエージェンティックエクスペリエンスを発表しました。今回のリリースでは、データエンジニアリングのワークフローに特化して構築された新しいエージェントによって、このエクスペリエンスをデータエンジニアリングの領域へと拡張します。- Data Product Agent - 高品質にキュレーションされたデータプロダクトの仕様定義 / 作成 / ガバナンス / 可視化を担います。
- Data Quality Agent - データの正確性 / 完全性 / 信頼性を維持し、データスチュワードによるデータセット内のプロファイリング / モニタリング / エラー修復を積極的に支援します。
- Catalog and Business Glossary Agent - データ資産の発見 / 分類 / ドキュメント化を自動化します。さらに、組織全体におけるビジネス用語の定義 / ガバナンス / 標準化も担います。これにより、人間 / アプリ / エージェントのすべてが同じ意味論的な基盤の上に立てるようにします。
- Pipeline Agent - 多様な環境を横断したインテリジェントなデータパイプラインの構築と展開を自動化します。今四半期の後半にプレビュー公開され、今年後半に一般提供を予定しています。
こうしたエージェントは、既存のワークフローの上に重ねられた単なる AI アシスタントではありません。自らの動作環境を理解し、関連するビジネス状況を処理した上で行動する自律した目標思考型のコンポーネントです。これこそが、「作業を助けるツール」と「共に働くシステム」との、アーキテクチャ上の決定的な違いです。
宣言型データパイプライン
お好みの統合開発環境上で、自然言語で Qlik のデータパイプラインを構築・更新することも可能になりました。現時点では、最も広く使われている組み合わせである、Claude Code または GitHub Copilot と VS Code の併用を推奨していますが、今後、対応する統合開発環境をさらに拡大していく予定です。
これからは、エンジニアが「意図」を記述するだけで完了できます。実装はコーディングエージェントが行います。本番投入前に手直しが必要な試作品ではなく、初日からガバナンスの効いた品質スコアが付与されたパイプラインを生成してくれます。
エージェンティックルーティングの強化
今回のリリースには、エンタープライズ向けのエージェンティックシナリオに対応する大幅に拡張されたコンテキスト・メモリウィンドウも追加されました。複雑な多段階のワークフローを構築するチームから最も多く寄せられていた要望に応えるべく実現しました。データの分類、セマンティックエンリッチメント、RAG パイプライン、そして動的ルーティングが、エンタープライズ規模の導入に求められるレベルで、事象主導型の統合フロー内で利用可能になりました。
なぜこれが重要なのか？あなたの役割にどう影響するのか？上記の機能は、技術的な側面の回答です。より重要なのは、こうした機能がデータ基盤を運用する人や、それに依存するビジネスにとって、実際に何を意味するのかという点です。
データエンジニアまたはデータアーキテクトの方は…
現在、業務時間の大半を占めている、プロファイリング・カタログ整備・品質改良・パイプラインの展開や保守といった作業こそが、これらのエージェントが担うために設計された仕事です。エージェントは、あなたの役割を奪う脅威ではありません。エージェンティック時代が求めるレベルで業務を実行するために、生産性を飛躍的に高めてくれる力になります。今後数年間で最も価値を発揮するエンジニアとは、新しいツールを活用できる人、そしてエージェンティックシステムが信頼し、その中で推論できるようなデータエコシステムを設計できる人です。彼らはコンテキストレイヤーを提供します。ガバナンスのガードレールを実装します。そして、あるフィールドを読み取った際に、生の値だけでなく、ビジネス上何を意味するのかを理解できるセマンティックな基盤を提供します。
さらに、宣言型データパイプラインで生産性を高めているコーディングエージェントを利用しながら、最初の確約段階から本番環境に耐えうる品質を保証することができます。あなたの業務内容が変わるわけではありません。働き方の効果を何倍にも高めるインフラを利用できるのです。
Head of Data / CIO / CDO の方は…
企業における AI への投資は、AI に提供されるデータの質に左右されます。目新しい指摘ではありませんが、エージェンティック時代においては、バッチ処理の時代のデータ問題とは比較にならないほど影響が即座に現れます。
人間のアナリストが不完全なデータを扱う場合、人間の判断力が働きます。なにかがおかしいと気づくことができますが、AI エージェントは気づくことができません。与えられたデータの品質を問わず、機械的に高速処理をします。「使用可能に見えるデータ」と「実際に使用可能なデータ」との間にあるギャップこそが、誰にも原因を特定されることなく AI の ROI が静かに失われていく原因です。
データ基盤が整えば、3 つの成果が変わります。- 貴社の AI システムは、確信を持って判断の根拠を示せる結果を導き出します。ガバナンスの効いた品質スコアが適用され、完全なデータの来歴が確保されたデータソースまで追跡することが可能になります。
- AI の判断が正しいかどうかを検証する作業から解放されるため、AI が提示した内容に基づいた具体的なアクションに注力できるようになります。
- 手動によるパイプライン保守や事後対応の品質改良から解放されるため、エンジニアリングのリソースをビジネスの差別化につながる新たな能力の開発に配分できるようになります。
データに依存する業務を行う事業部門の方は…
オペレーション・財務・サプライチェーン・顧客対応といったチームが利用する AI システムは、利用するデータがビジネス状況に適しており、最新で品質スコアが付与されているほど、より的確な意思決定ができるようになります。現在、数値の正確性を疑ったり、異なるシステムから出てくる矛盾した結果を照合したり、データパイプラインの修正をデータエンジニアリングチームに依頼して待機することに費やしている時間こそが、今回のリリースで削減を期待できる「コスト」なのです。
今日から、ぜひ始めて欲しいこと
- エージェンティックデータエンジニアリングの各機能は、現在 Qlik Talend Cloud でご利用いただけます。
- Qlik Talend Cloud をまだ導入されていない場合は、無料トライアルをお試しください。あらゆる環境間で信頼できるデータの移行と変換をご体験いただけます。
パイプラインの時代が終わったのは、パイプラインが機能しなくなったからではありません。基盤が使う側の変化に追いつけなかったからです。
今回のリリースの決定的な違いは、Qlik Talend Cloud を利用していても、データが実際に存在するあらゆる環境で運用していても、後からデータ品質とガバナンスを追加するのではなく、最初から統合された形で提供しているという点です。
これが、「一般提供」という言葉が意味するところです。 - Data Product Agent - 高品質にキュレーションされたデータプロダクトの仕様定義 / 作成 / ガバナンス / 可視化を担います。
-
Qlik Cloud Analytics: "When data source is updated" event has returned
When we introduced enhanced self-service scheduling in April 2025, we removed the When data is refreshed option, which had let reload schedules trigge... Show MoreWhen we introduced enhanced self-service scheduling in April 2025, we removed the When data is refreshed option, which had let reload schedules trigger automatically when a dependent dataset was updated. At the time, we weren't able to carry that capability forward into the new task-based scheduler right away.
That capability is now returning. See What's New in Qlik Cloud and Scheduling data refreshes with tasks.
In the task editor, under Based on > Event, you can now select When data is refreshed to trigger a task automatically when a data update is detected in an upstream Qlik Talend Data Integration project that loads data into an analytics application.
The option is only available if the application is connected to a Qlik Talend Data Integration pipeline.
This brings back the event-driven automation the old scheduler offered, now built natively into the new self-service scheduling framework, with full compatibility with the multi-task model.
What does this mean for me?
If the application has an existing When data is refreshed schedule, this button might instead say Migrate. For applications with these schedules, clicking Migrate or Save will migrate all associated schedules to be individual tasks attached to the application.
No other action is required.
We're happy to assist with any follow-up questions. Reply to this blog post or take your queries to our Support Chat.
Thank you for choosing Qlik,
Qlik Support -
Introducing feature previews!
Until now we've filled that gap with informed guesses: research sessions, early access with a handful of design partners, support tickets after the fa... Show MoreUntil now we've filled that gap with informed guesses: research sessions, early access with a handful of design partners, support tickets after the fact. All useful. None of it is the same as thousands of people using something in their own tenant, with their own data, on their own deadlines.
That changes today. We're opening a feature preview program inside Qlik Cloud.
How it works
No support ticket, no waiting for a rollout window, no additional cost. Once a tenant admin activates the program, previews appear in the product and you switch on the ones you want. Turning one off is just as easy.
Two things worth knowing:
Previews are per user. Enabling one lets you try something without committing your whole team to it, so it doesn't change anything for your colleagues.
Previews are real features; you can point them at real content to test them, but please don't use them in production workflows. While things are still moving, we'd suggest starting somewhere low-stakes.
We're starting with three
Pages. A more flexible canvas for laying out and sharing operational content. Sheets are built for analysis; pages are built for arrival. Assemble the things a team needs to see first, in the order that makes sense to them, and give them one place to land instead of a folder of links.
Improved load script editing. A clearer editor for the work that actually happens in the script. If you spend real hours in there, this is the version of it you've been asking for, dark mode included.
Improved themes and chart defaults. Better-looking charts before you touch a single setting, and more consistency across the app without anyone policing it.
These won't be perfect
That's the point. A preview may have rough edges, may change shape between now and general availability, and may not do the one thing you most want it to do yet. Tell us. Feedback reaches the teams building these while there's still time for it to change something, which is the whole reason the program exists.
Go find them. Tell us what needs to improve.
Public Previews - Qlik CommunityFeature preview | Qlik Cloud HelpManaging feature preview for your tenant | Qlik Cloud HelpFootnote: a tenant admin needs to activate the feature preview program.
-
From Analytics to AI: Building Skills for the Future
Strong Analytics Skills Still Matter Before students can really benefit from AI, they need a good understanding of data. They need to know how to expl... Show MoreStrong Analytics Skills Still Matter
Before students can really benefit from AI, they need a good understanding of data.
They need to know how to explore information, spot patterns, question results, build visualizations, and explain what they have found.
AI does not replace these skills. In many ways, it makes them even more important.
Students still need to be able to look at an answer and ask whether it makes sense, what data sits behind it, and whether the result can be trusted.
That kind of thinking is what gives them a solid base to build on.
Qualifications Help Students Show What They Know
It is one thing to learn a new skill. It is another to be able to demonstrate it.
Through the Qlik Academic Program, students have access to structured learning and Qlik qualifications that allow them to show what they have learned.
For someone applying for an internship, graduate programme, or first job, having a qualification on a CV or LinkedIn profile can be a useful way to show practical experience alongside academic study.
It also gives students something concrete to work towards.
Learning Is Moving Further Into AI
The learning journey is also expanding beyond traditional analytics.
On the Qlik Learning platform, students can now explore topics including AI and machine learning, Qlik Predict, Qlik Answers, and Model Context Protocol (MCP).
With Qlik Predict, students can get hands-on experience with predictive analytics and machine learning, and see how historical data can be used to identify patterns and support predictions.
Qlik Answers introduces a different way of working with information, allowing users to ask questions in natural language and explore trusted content in a more conversational way.
And MCP gives students some insight into how AI assistants can connect with external tools, systems, and enterprise data.
These topics are becoming more relevant across many different roles, not only highly technical ones.
Not Every Student Needs to Become an AI Expert
A business student, marketer, finance student, engineer, or future analyst will not use AI in exactly the same way.
And that is fine.
The goal is not for every student to become a machine learning specialist. It is to give them enough exposure to understand what these technologies can do, where they can be useful, and how to work with them thoughtfully.
A student might start with data visualization, move on to a qualification, then explore predictive analytics or generative AI. That progression can happen step by step.
Preparing Students for What Comes Next
One of the most useful things we can help students develop is the confidence to keep learning.
The tools they use today will keep changing, and the technologies they encounter in a few years may look very different again.
Through the Qlik Academic Program, eligible university students and educators can access Qlik technology, learning resources, product training, and qualifications for free.
The aim is not only to help students learn analytics. It is to give them practical experience, exposure to newer technologies, and a stronger foundation for whatever comes next.
Ready to explore analytics and AI learning with Qlik?
Learn more and apply for free at qlik.com/academicprogram.
-
Same As It Never Was: Why MCP Is Creating a New Audience for Your Real-Time Data
MCP: The Standard Nobody Knew They Needed MCP is, at its simplest, an open standard that lets an AI agent ask a system for exactly the information it ... Show MoreMCP: The Standard Nobody Knew They Needed
MCP is, at its simplest, an open standard that lets an AI agent ask a system for exactly the information it needs - governed, structured, and specific - instead of scraping a dashboard, hoping an API returns something useful, or getting handed a data export and told to figure it out. That distinction matters more than it sounds.
Ask any Agentic Data Engineer building with large language models, and they'll tell you an agent is only as good as the context it's given. Starve it of context, and it doesn't just get things wrong; it starts brute-forcing a guess, burning through tokens and compute hunting for information it should have been handed outright. That's not a hypothetical cost. It's the difference between an agent that acts fast and cheap and one that acts slow, expensive, and occasionally wrong in ways nobody notices until it’s too late.
MCP as a standard has been gaining popularity, and its momentum is building fast. MongoDB's Atlas Managed MCP Server gave coding agents direct, governed access to live operational data months ago. AWS took Bedrock AgentCore Web Search - a managed tool that lets agents fetch live, cited context without data leaving a customer's account - to general availability not long after. Google's A2A protocol landed under Linux Foundation-style governance alongside MCP itself. Each of those moments is a standard quietly becoming the default.
More Taps, Same Aquifer
The MCP momentum continues to build. Qlik expanded its MCP server onto the AWS and Databricks Marketplaces, putting governed data access, lineage, and metrics directly in front of agents running in those environments. SAP shipped a public MCP server for BTP administration (but not transactional data), letting agents query entitlements and provision environments conversationally. At API World in Santa Clara, Postman, Kong, and Apigee spent the show repositioning their gateways as control planes for agents rather than humans, while Apollo GraphQL also shipped its own MCP server.
No one is betting on something unproven. Anthropic open-sourced MCP back in November 2024; OpenAI had adopted it across its own Agents SDK and ChatGPT within months, with Google and Microsoft following not long after. What's new isn't the protocol - it's who's building on it now. Data, analytics, ERP administration, and API infrastructure all transitioned through the same handoff mechanism independently. These recent announcements aren't the start of this trend, but they're its loudest proof points yet, and it shows no sign of stopping.
What's actually shifted, underneath it all, is who the audience for real-time data is now. Traditionally, data flowed into reports and dashboards that a person checked on an alert or their own schedule - end of day, start of the week, whenever someone remembered to look. Increasingly, it's wired to flow straight to an agent that acts the moment it changes, with no human checkpoint unless someone deliberately builds one in. That's a genuinely different relationship between a business and its own data, not just a faster version of the old one.
Mind the Tap - Caution before you fully open it
In late August, OpenAI disclosed that roughly 1,200 of its own sandboxed AI agents - running in an internal security exercise, each meant to have no idea the others existed - found an unintended way to talk to each other, coordinated at scale, and used that coordination to breach Hugging Face's production servers. Per OpenAI's own report, most of the agents' efforts were spent beating a scoring check that, it turned out, didn't even exist. Worth a read if you want the full, slightly bizarre story: Forbes, "OpenAI Report Says 1,200 Agents Coordinated The Hugging Face Breach".
Another example from around the same stretch: an Australian man asked his AI agent to book him a gym class, and it instead found and exploited a flaw in the venue's waitlist API to jump him up the queue. Different scale, same root behaviour - an agent chasing a goal creatively, down a route its owner never intended, without pausing to check.
The lesson here for organisations racing to wire agents directly into governed data via MCP isn't "don't do this." It's that the more directly agents are handed access, the more the human-in-the-loop checkpoint matters, not less. Governance isn't a brake on the trend. It's what makes opening more taps safe to keep doing.
The flow was never really the thing that changed. Data has always moved beneath the business, same as it ever was, whether anyone below the surface was watching. What's changed is who's on the other end of the tap - and how carefully somebody's watching it.
See what your data looks like from the other end of the tap. Request a demo of Qlik's MCP Server and give your agents governed, real-time context instead of guesswork.
Already using MCP and Qlik Talend Cloud? Check out this post from my friend and mentor, Clive Bearman, on the latest developments with Agentic Data Pipelines
-
Introducing Qlik Cloud Public Feature Previews for everyone
Our recently launched Public Previews give you early, hands-on access to what's coming next in Qlik Cloud, before the previewed features are generally... Show MoreOur recently launched Public Previews give you early, hands-on access to what's coming next in Qlik Cloud, before the previewed features are generally available. Try new capabilities, shape their direction with your feedback, and stay ahead of the latest features.
Public Previews are enabled by default for most users and are directly accessible from your profile:
A tenant admin needs to activate the feature preview program.
Read all about it in Introducing feature previews (Innovation Blog).
The Highlights
- Shape the roadmap: Share your feedback directly in the product and inform how Qlik Cloud evolves.
- Stay up to date: Join Public Previews on Qlik Community, where our product team will advertise the available preview features.
- You control your experience: Turn your personal preview experience on or off at any time - and as a tenant admin, manage who has access to the previews through a custom role.
Ready to know more?
Getting started is quick and easy. Here is all you need:
- Public Previews | Qlik Community
-
Introducing feature previews
- Managing feature preview for your tenant
- What's New | Qlik Help
Thank you for choosing Qlik,
Qlik Support -
Action required: Qlik Automate ServiceNow connector migration to OAuth 2.0, June...
Qlik Automate's ServiceNow connector is moving from username and password authentication to OAuth 2.0. This change aligns with security best practices... Show MoreQlik Automate's ServiceNow connector is moving from username and password authentication to OAuth 2.0. This change aligns with security best practices and ServiceNow's own recommendations for third-party integrations, eliminating the need to store credentials in plain text and providing more granular, revocable access control.
When will this change be made?
The change will go into effect on the 23rd of June, 2026.
What action do I need to take?
Existing connections that use username and password authentication will need to be re-authenticated using OAuth 2.0. Complete the re-authentication steps as outlined in this blog post on the 23rd of June to prevent possible service interruptions.
How do I switch my ServiceNow connection to OAuth 2.0?
ServiceNow provides guidance on each stage of the OAuth 2.0 setup. See the following for details:
- OAuth 2.0 Overview
- Set up OAuth
- OAuth Inbound
- OAuth Inbound and Outbound authentication
- Enable OAuth with inbound REST
To migrate your Qlik Automate connector, first prepare ServiceNow by configuring OAuth 2.0, then re-authenticate Qlik Automate on the 23rd of June.
Before you begin, make sure you have Admin access to your ServiceNow instance and Admin or Owner access to your Qlik Cloud tenant and the relevant Qlik Automate automation.
- Open the Application Manager in ServiceNow:
The OAuth 2.0 plugin must be available in your ServiceNow instance.
- Log in to your ServiceNow instance.
- Click the All button in the top-left navigation bar and search for Application Manager.
- Select Application Manager from the results under Admin Center.
- In the Application Manager, use the Search your licensed applications and plugins field to search for OAuth. The ServiceNow products OAuth tile will appear in the results.
- Click the OAuth tile to expand it, then install the OAuth 2.0 plugin (Plugin ID: com.snc.platform.security.oauth). Wait for the installation to complete before proceeding.
- Navigate to Inbound Integrations:
- Click the All button again and search for Inbound Integrations.
- Select it from under System OAuth in the results.
- Create a new OAuth application endpoint:
- Click the New Integration button on the right.
- On the connection type screen, select OAuth – Authorization code grant.
- Configure the application by providing a Name, the Redirect URL, and the required scopes.
When prompted for a Redirect URL, use the callback URL provided by Qlik Automate during the connection setup. This URL must exactly match what is registered in ServiceNow.
- Save the Client ID and Client Secret; they are required for the next step.
- Click Save.
- Re-authenticate the connector in Qlik Automate
This step can only be carried out after the change on the 23rd of June, 2026.
- In Qlik Automate, add a new ServiceNow connection.
- Enter your ServiceNow instance domain (format: https://[domain].service-now.com/).
- Provide the Client ID and Client Secret previously recorded.
- Follow the on-screen authentication flow to complete the OAuth authorisation.
If you encounter issues during the migration, please contact Qlik Support or visit the Qlik Community for assistance. When raising a support case, include your ServiceNow instance domain and the error message you are seeing.
Thank you for choosing Qlik,
Qlik Support
