Integration · Analytics and data
AI agents for Qlik Cloud
Find apps, spaces and other content in a Qlik Cloud tenant, read an app's data model, and reload an app's data and follow the reload, with an API key.
- Actions
- 9
- Read
- 7
- Write
- 2
Actions
What your agents can do in Qlik Cloud
9 actions. Each one is a tool your agents can call and a step your workflows can run.
Read 7
Look things up. Nothing changes.
Get the API key's user
Returns the user this API key belongs to: id, name, email, tenantId, status and assignedRoles.
Search content
Searches the tenant's content the key's user may see: apps, data sets, automations, notes, scripts, glossaries and more.
List spaces
Lists the shared, managed and data spaces the key's user may see, as data: each with id, name, type, description, ownerId and createdAt; links.next.href when there are more.
Get an app
Reads one app's details in attributes: name, description, ownerId, published, publishTime, createdDate, modifiedDate and lastReloadTime; and privileges, what the key's user may do with it.
Get an app's data model
Describes the data loaded into an app: tables (each name, no_of_rows, no_of_fields, byte_size) and fields.
Get a reload
Reads one reload: status (QUEUED, RELOADING, CANCELING while it runs; SUCCEEDED, FAILED, CANCELED or EXCEEDED_LIMIT when done), startTime, endTime, errorCode, errorMessage and the script log.
List an app's reloads
Lists an app's reloads, newest first, as data (each like get_reload, without the log), with links.next.href when there are more.
Write 2
Create, change or send.
Reload an app
Queues a reload of an app's data from its load script.
Cancel a reloadDeletes data
Asks Qlik to stop a queued or running reload.
A person can approve first
Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything. Actions that delete data ask first by default.
Connection
How it connects
Connect it once in the console, then give it to the agents and workflows that need it.
Paste an API key from your Qlik Cloud account.
What you enter
- API key
Settings
- Tenant address
Kept safe
- Credentials are stored encrypted with your organization's own keys.
- They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
- Calls go only to the tool's own servers.
Ideas
Ideas to start with
Starting points made only from the actions above. Mix them with any other tool your agents can use.
- 01
Ask about your Qlik Cloud data
Ask a question in plain words. The agent can get the API key's user, search content or list spaces in Qlik Cloud, then answers with what it found.
- 02
Let an agent update Qlik Cloud
Have the agent cancel a reload in Qlik Cloud as part of a larger task. Turn on approval and a person signs off on each change first.
- 03
Share what it finds in Slack
Give one agent Qlik Cloud and Slack: it can get the API key's user in Qlik Cloud and post a summary to a Slack channel in the same run.
FAQ
Qlik Cloud and MyDeepAgents
Can MyDeepAgents connect to Qlik Cloud?
Yes. The Qlik Cloud connector has 9 actions: 7 read and 2 make changes. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect Qlik Cloud?
Paste an API key from your Qlik Cloud account. You'll need: API key. The connection also asks for: Tenant address. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.
Can an agent change data in Qlik Cloud without asking?
Only if you let it. Each of the 2 actions that change data can be set to wait for a person's approval before it runs, and the one that deletes data asks first by default.
Can I use Qlik Cloud in workflows as well as agents?
Yes. Every Qlik Cloud action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put Qlik Cloud to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.