I was hoping that there would be

I was hoping that there would be something more direct. Abstracting an API call behind another API call seems redundant.

Here's what I was trying: wmill.run_script_sync("f/stantt/ups_tracking", {"Tracking Number":"1Z036W6E6730439313"}, verbose = True)

That returns: Exception: Job not found

antonioalves•9/14/23, 6:00 PM

I see, but I think that under the hood, will be http request anyway... I just think, I'm not sure

antonioalves•9/14/23, 6:01 PM

I use that approach within my scripts inside the app

Do you use the wmill module or just call the api endpoint?

antonioalves•9/14/23, 6:03 PM

just call the api endpoint

antonioalves•9/14/23, 6:03 PM

like the examples in the tab details & trigger

Tiago Serafim•9/14/23, 6:17 PM

Just tested here on a new TS script and a Python script using the . It worked. Are they in the same workspace?

Tiago Serafim•9/14/23, 6:18 PM

Ah, you used which expects a hash, you should call instead.

Does that only work with scripts? Is there an option for flows?

Tiago Serafim•9/14/23, 6:37 PM

Not sure, I'd guess that internally they're treated the same.

It doesn't seem to be working to trigger a flow, unless I'm missing something on my end.

Tiago Serafim•9/14/23, 6:42 PM

Just tried here with a flow and it didn't work too

Thank you for trying--it may not be implemented yet.

rubenf•9/14/23, 10:54 PM

So to answer, script and flows live in different namespaces so the same method cannot be used

rubenf•9/14/23, 10:54 PM

we could add it to the client but under the hood it's just an http request

rubenf•9/14/23, 10:54 PM

we will add it

Thanks Ruben!