I am referring to the point raised here a while ago about specifying more granular conditions WHEN a webhook will be triggered.
We are looking to trigger the webhook only if e.g., the “Action” Field/Column is changed to “Do Action 1”. Currently the webhook is triggered whatever value we set in the “Action” Field/Column. It would be great to specify to what value a column needs to be changed to trigger the webhook.
We have a column Action where we can trigger various actions. The problem now is that every action triggers every webhook, which leads to unnecessary resource consumption, - on the side of Baserow but also on the receiving end of the webhook - Make.com or N8N. We would like to avoid this and keep the resource consumption to a minimum.
There is just one argument - an input field or dropdown field - missing in the above criteria so that we could specify in which cases the webhook will be triggered. We would appreciate it if this could be addressed.
Hi @artoflogic, I’ve discussed this request with the team, and there’s actually a workaround. If you create a view with filters that match your conditions and then use the Rows enter view trigger, you should get the setup you need.
For example, in the view filtering options, you can specify that Name equals X. When this condition is met and the filter is applied, a webhook will be triggered.
Please note, this is an Advanced/Enterprise feature.
This won’t work for us as we don’t work like this. We have 10 or sometimes 20 views in a table, and our filter criteria are always changing. It is impossible to program a webhook, which is triggered only by a specifc view. What we want is to trigger the Webhook regardless, which view we have chosen.
Today one of our automations hung up and ended in an eternal circle. Then what happened is that all webhooks for that database table were triggered.
We had 2000 executions triggered, multiplied by ca. 6 webhooks, triggering 12,000 automations in Make.com. In Make.com we have filters installed and if the action is not what the scenario was designed for, the execution will stop. I just received an invoice for processing all these 12,000 triggered webhooks only for Make.com having to process 12’000 invalid actions. Its very very costly your missing column filter.
I am really not looking for a workaround. I am looking for a proper solution.
Is it not possible to specify what column value needs to be set in order to trigger the webhook? This is the proper solution we are looking for. If you could check this.
The use case for Baserow is mainly to work in tandem with Automation providers such as Make.com and N8N in my understanding. Triggering webhooks should be done only when precise criteria are met.
