Automation & Qlik Embed

[LorisLombardo87]

Hi everyone,

has anyone ever tried to launch an automation from a sheet embedded in a webapp using Qlik Embed?

I've tried to do so, but when i click on the the action button set to execute the automation nothing happens, and if i look in the browser console i can see i'm getting a 302 and a request to login.

the automation i'm trying to execute is something like this https://community.qlik.com/t5/Official-Support-Articles/How-to-build-a-write-back-solution-with-nati... 

any suggestion ?

thanks,
Loris

[Dave_Channon]

Hi @LorisLombardo87 

If this is multi-user writeback, are you testing with the checkbox enabled for "Run mode: triggered"?

[LorisLombardo87]

Hi @Dave_Channon ,

yes, this is how I've set the button:

please note that if a user executes ( clicks the button ) on sense itself it goes with no problems, but embedded on a web app throws the error.

Thansk,
Loris

[LorisLombardo87]

Hi @Dave_Channon any hints?

does it worth opening a support case?

Thansk,
Loris

[Dave_Channon]

Yes, please open a case! If you could DM me the ticket number too I'd appreciate it 🙂 

[jauten8]

was there any solution to this issue? 

Looks like in our embed we are running into the same thing and it ties back to the automation trigger in the app.. is requiring another sign on for it to run outside of the embedded login. 

[Ibrahim_Izz]

@jauten8 @Dave_Channon @LorisLombardo87 Hello guys

Have you find a solution to this problem yet?

[jauten8]

yes, we had to create a custom object button that called the execution token for the automation. I think they implemented or ARE going to implement a fix t o where automation buttons work in embeds, but our development team were able to create the custom execution button and it works now!

Custom object documentation: https://help.qlik.com/en-US/sense/November2025/Subsystems/Hub/Content/Sense_Hub/Visualizations/creat...

[Ibrahim_Izz]

Hello again @jauten8 

Thanks a lot, it worked, but the problem now is exposing the execution token in the front end. Have you worked that around without using a proxy server to host and hide the execution token?