Forum Discussion
Adding my take (previously shared with Quickbase directly).
At this point, we (the developer community) do not feel there is parity between table webhooks and pipeline webhooks.
I would say the top 3 reasons are:
- Access: Not all users have access to Pipelines or it's often easier to create table webhooks with shared access which is not currently an option in Pipelines.
- Speed: Table webhooks run faster than you can blink even for large sets of data.
- Bulk Triggers: Today a table webhook triggered off a bulk action (grid edit or import) creates a single trigger that can either be used to create a single action like add record OR a bulk action with ImportFromCSV. In pipelines any time a bulk action (grid edit or import) triggers a pipeline it files individually which can cause issues with large updates that may trigger 1000+ instances.
Here are some feedback cases on this particular issue:
https://feedback.quickbase.com/app/#/case/359112
https://feedback.quickbase.com/app/#/case/160597
Since the retirement of Automations I've found myself relying more heavily on table webhooks when the use case is simple and the above are necessary.
Without parity it would be DISASTROUS and expensive to rework the apps where extensive table webhooks have been used... and I'm sure many partners feel the same.
In addition to the above, I agree with others who have also mentioned the often painfully slow process of building Pipelines compared to the speedy development of table webhooks as well as the difficulty searching and organizing Pipelines.
-Sharon
------------------------------
Quick Base Junkie
Sharon Faust
https://quickbasejunkie.com
------------------------------