Qlik Automate execution token changes

[Sonja_Bauernfeind]

Hello Qlik Users,

Execution tokens will become header parameters on February 1st, 2026.

On January 13th, 2025, Qlik introduced breaking changes to the execution token functionality for triggered automations. 

Contents

• What does this mean for my triggered automation?
• How do I configure the Run Mode?
• Additional change: Execution tokens become header parameters (February 1st, 2026)
• Related improvement: custom parameter support for button-triggered automations

What does this mean for my triggered automation?

Triggered automations will require their Run Mode to be set to triggered to continue to work as expected. Past January 13th, it will no longer be possible to use the below endpoint to trigger an automation not explicitly configured with a triggered run mode:

api/v1/automations/{id}/actions/execute

 

How do I configure the Run Mode?

The run mode can be configured in the Start block of an automation:

1. Open the Automation
2. Select the Start Block
3. Open the Inputs tab
4. Select Triggered as the Run Mode
   
   
   

Additional change: Execution tokens become header parameters (February 1st, 2026) 

An additional change to how execution tokens are used will be introduced on  February 1st, 2026. 

When triggering a triggered automation through the trigger URL (see the endpoint below), the execution token must be sent as a header parameter. Currently, it is possible to send the execution token as a query parameter. Starting February 1st, 2026, sending execution tokens as header parameters will be enforced.

api/v1/automations/{id}/actions/execute

 

Related improvement: custom parameter support for button-triggered automations

When triggering an automation from a button in an app it is now possible to provide additional input parameters that are defined in the button configuration. More information can be found here: custom input parameters for the native button.

Don't hesitate to reach out if you have any questions or address our experts directly in the Qlik Application Automation forum.

Thank you for choosing Qlik,
Qlik Support

[mshann01]

Will we be able to call a scheduled automation from a triggered automation?  This will ideally allow the scheduled version to run as necessary but have a "wrapper" that will allow for a button or link to manually fire off a reload like we do today.

Considering there is still no solution after all these years for sharing automations, admins rely on kicking off other users failed automations via the API endpoints.

[janyf]

You could do it other way around, set automation as triggered , and then schedule it via app and rest. 
That way automation will be triggered by scheduled reload of app, and you could still trigger it manually when needed. 

[Natalia_Kapelian]

How does it affect Automation triggered via a button in the app? 

[Emile_Koslowski]

Hi,

This restriction only applies to triggering automations through the /actions/execute endpoint. Starting Jan 13th, this will only be possible if the automation is also configured as triggered. It will still be possible to run automations through the /runs endpoint which requires an authenticated user.

The Run Automation blocks in the Qlik Cloud Services & Qlik Platform Operations connectors use the /run endpoint and will continue to work.

Today, you can only use the /runs endpoint to run automations you own. Once shared automations are delivered, it will be possible to add them to a shared space and allow other users in that space to run them.
Until then, if you want to be able to run a scheduled automation through a trigger, you could set up a second triggered automation that uses the Run Automation block from the QCS or QPO connector to run the scheduled automation.

Automations that are configured via a button in the app with the "Run mode: triggered" option checked, will also require the automation to be configured with the triggered run mode.

[Emile_Koslowski]

Adding additional FAQ:

• Q: When the Run Mode is set to "Triggered" is it still possible to run the automation manually?
• A: Yes, you can continue to use the Run button in the automation editor or the "/run" API endpoint to run the automation.

[Ken_T]

is there a way for an admin user  to get a list of which automations are impacted by this?  to see which ones are using a query parameter for the token

[Sonja_Bauernfeind]

Hello @Ken_T,

There isn’t a straightforward way for customers to obtain information about triggered automations that use the execution token as a query parameter. You would need to raise a support case and request this information from us.

All the best,
Sonja

[Ken_T]

would it be possible to add to this article, and  to show how exactly the execution token is sent as a header parameter, maybe with some screenshots?

and perhaps show the old way that no longer works, too (execution token being sent as a query parameter)