Update on the retirement of Application Webhooks UI and QB Actions

Completely agree with all the comments. Getting rid of Webhooks would set Quickbase back, not move them forward. 

Like Jim said, webhooks are SO much easier to create, especially for quick, simple needs.

As all others mentioned, their 'instantaneous' nature is what sets them apart from Pipelines. Based on the nature of Pipelines, I don't foresee them ever catching up and functioning in the manner of of Webhooks. For my use cases, this is the most striking difference, and most necessary need for webhooks.

Not mentioned yet is simple organization. It is quite often that I need a very very simple automated feature. 'If a new record is created, create a record over here.' Or perhaps 'when a record is saved, copy this formula field to this scalar field.' While Pipelines could obviously handle these, having an extra 100+ Pipelines to accomplish this, is a organizational mess.

I don't use it yet, but for more advanced development, as other mentioned (integrating from Workato etc), this crushes that functionality.

I cannot come up with a single positive to removing Webhooks, so I would be curious to hear from QB Development team, what advantages they see to removing Webhooks as an option? Perhaps if we had more context we would be able to better understand.