Hi,
Is there a way I can set the input parameters to my Xano collection at the time of invoking the collection? For instance, I have a Xano collection (POST) that I’m using for event logging. The current approach I’m using is to set up a variable (object) and bind the collection inputs to this variable. This means each time I want to use this collection, I need to have a step in my workflow where I have to first set this variable and then ‘fetch’ the collection.
I’m wondering if each time I create an action in the workflow to log an event, I add the Xano endpoint as s step, but then set the input variables right there in this workflow itself (and that are specific to this workflow only). So in another workflow, when I invoke the same Fetch collection step, I again set the input variables for whatever I want to pass in that scenario.
In other words, can the collection inputs be similar to how a Workflow with parameters is set up or the way the REST API plugin works? It appears that I can seem to do it like this using the REST API plugin, i.e. to define input parameters in the action step where I’m calling the REST API – but I can’t seem to find a way to do this if the collection is a Xano collection.
Thanks.
Sean
Hi ,
not answering for your question, cause don’t know the answer.
But I’m also using Xano. So what you described is exactly the reason why I changed all of my API calls from Xano plugin to REST API calls. They are flexible enough for difficult logic and nested workflow calls. I just wanted to say that you are not alone in this 
1 Like
Dang! That sucks. I actually love the Xano plugin. It simplifies a bunch of little configurations that I’d otherwise have to set up each time so I’d hate to move away from it just for this.
I wish Weweb would add the option to “override” the collection bindings at the time of Fetching a collection in a workflow. This way, we could set up a collection and pre-bind it to a variable. But then in specific cases, we could override the binding to have a different set of input/bindings for a particular workflow.
I’m not 100% this is what you mean with your question?
2 Likes
Thanks so much @nealzie. I just learned something new today. This is awesome and exactly what I was looking for. I was actually looking for these options in the “Fetch collection” action. I didn’t even notice that there’s a separate “Request” action that does exactly this – i.e. I can choose the Xano endpoint I want, and then dynamically modify the input parameters only for a specific workflow. Sheesh, do I feel silly now.
Fetch collection action options
Request action options
I ran into exactly the same problem recently. Then I built an entire workaround with variables and whatnot. Then today I had to do it again elsewhere and managed to create this workflow 
Somehow I stumbled upon your post literally 5 mins after finding it out myself, haha. So glad it helped you out!
3 Likes
