Variables can't be passed through trigger URL

[Liang0info]

Describe the bug I want to execute Automa workflow with variables through an URL. And I attempted to use {{variables.variableA}} to access the variable but failed. chrome-extension://infppggnoaenmfagbfknfkancpbljcca/execute.html#/uZhm-lJyEbObBs3URyWJ_?variableA=value&variableB=10

To Reproduce Steps to reproduce the behavior:

1. Create a workflow which will access some variables.
2. Execute it with variables through an URL.
3. The variables can't be accessed.

Expected behavior The variables should be passed.

Desktop (please complete the following information):

• OS: Windows
• Browser: Google Chrome 125.0.6422.7 (Stable)
• Extension Version: v1.28.27

[BenJamesAndo]

I was having a similar issue. It doesn't seem to be properly functional. I've mentioned the bug and a limited workaround at https://github.com/AutomaApp/automa/issues/1607#issuecomment-2174926746

[Banalian]

I also encounter this. With debut mode I can see that there's no variables setup, the workaround suggested doesn't work for me this I need to use letters as the arguments.

[eriksonssilva]

I have found out that if you encapsulate the string between double quotes, it will work! So instead of chrome-extension://infppggnoaenmfagbfknfkancpbljcca/execute.html#/workflowId?variableA=value you would do chrome-extension://infppggnoaenmfagbfknfkancpbljcca/execute.html#/workflowId?"value"=variableA. Not sure why it's like that, but at least it's a workaround!

[BenJamesAndo]

@eriksonssilva that's awesome that you figured it out! Works great for me now as well. Thanks for sharing your findings.

[Banalian]

Awesome indeed! Thanks a lot for this, it's gonna be a huge improvement for my stuff!

[SimpleTangLong]

@eriksonssilva I'm so shocked, how did you find out？