Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.

How to run an automation with custom parameters through the Qlik Sense button

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
Emile_Koslowski
Employee
Employee

How to run an automation with custom parameters through the Qlik Sense button

Last Update:

Aug 12, 2025 3:09:31 AM

Updated By:

Sonja_Bauernfeind

Created date:

Dec 10, 2024 3:06:15 AM

This article explains how the Qlik Sense app button component can be used to send custom parameters directly to the automation without requiring a temporary bookmark. This can be useful when creating a writeback solution on a big app as creating and applying bookmarks could take a bit longer for big apps which adds delays to the solution. More information on the native writeback solution can be found here: How to build a native write back solution.

Contents

 

Button configuration

  1. In this example, we'll use an app that contains car sales opportunities from Salesforce. The straight table, the variable input dropdown, and the native button are important for this example.


    Example App.png

  2. Start editing the sheet and go to the button configuration section, set the action to "Execute automation" and specify the automation that should run when the button is clicked. If your automation isn't shown, you can copy and paste the automation id.

    execute automation.png

  3. Additional input parameters can now be added through the "Add parameter" button.

    add parameter.png

  4. Parameters require a key and a value, it's possible to use Qlik Expressions as input for the value. These expressions are evaluated when the button is clicked.

    add keys.png

  5. After adding the parameters, use the "Copy input block" button to copy the all parameters that will be sent to the automation to your clipboard.

    copy input block.png

Automation configuration

  1. If you want anyone who can access the button to be able to run the automation, then set the automation's run mode to "Triggered".
    If you want to limit this to a specific group of users, you can leave the automation in Manual run mode and place it in a shared space that this group of users can access. More information about this is available here: Introducing Automation Sharing and Collaboration. Make sure to disable the Run mode: triggered option in the button configuration.
    configure the run mode to triggered.png
  2. Right-click in the automation canvas and select "Paste Block(s)" to add the Inputs block to the automation. Connect the new Inputs block to the Start block. Apart from the default parameters, you'll also find your custom parameters as Inputs in the block.

    Paste Blocks.png

  3. You can now reference the custom parameters from the button in other blocks in the automation by selecting the output from the Inputs block.

    Set inputs.png

    inputs set.png

     

Limitations

  1. The maximum payload size when triggering an automation is 32kb. When using the GetCurrentSelections expression, every field value will be sent to the automation. This could exceed the 32kb limit. Use the temporary bookmark solution as described in this article instead: Native writeback solutions.
  2. Other automation limitations are available here: Platform limitations.
  3. More info on configuring the native button can be found here: Creating buttons.

 

Related Content

 

Environment

  • Qlik Cloud
  • Qlik Application Automation

The information in this article is provided as-is and will be used at your discretion. Depending on the tool(s) used, customization(s), and/or other factors, ongoing support on the solution below may not be provided by Qlik Support.

Labels (2)
Comments
Ken_T
Specialist
Specialist

is this process affected by the change to require use of header parameter for execution token?

Version history
Last update:
‎2025-08-12 03:09 AM
Updated by: