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)
12 Replies
That returns: Exception: Job not found
I see, but I think that under the hood, will be http request anyway... I just think, I'm not sure
I use that approach within my scripts inside the app
Do you use the wmill module or just call the api endpoint?
just call the api endpoint
like the examples in the tab details & trigger
Just tested here on a new TS script and a Python script using the
wmill.run_script_by_path_sync. It worked. Are they in the same workspace?
Ah, you used wmill.run_script_sync which expects a hash, you should call run_script_by_path_sync instead.Does that only work with scripts? Is there an option for flows?
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.
Just tried here with a flow and it didn't work too
Thank you for trying--it may not be implemented yet.
So to answer, script and flows live in different namespaces so the same method cannot be used
we could add it to the client but under the hood it's just an http request
we will add it
Thanks Ruben!