Creation of new QB Actions and Webhooks will be locked as of  June 30, 2024

The one big missing feature of Pipelines is the ability for developers collaborate.  Will that be addressed prior to June? Actions and Webhooks are maintainable by all Admins in an App.  Not so Pipelines.

I agree with Mark and would add that the in-table Webhooks run MUCH faster than using a Pipeline which leads to a much nicer user experience. In most situations, the Webhook has already run by the time the single-record is re-displayed. This often means an embedded report shows updated data without having to do an extra refresh. It would be really nice to keep the in-table Webhooks feature.

The main use case of webhooks is the consolidated triggers that help to handle bulk operations better. In Pipeline, I don't see any option to have one single trigger when bulk insert of update happens. 

I sometimes call the pipeline after creating a bulk upsert log through a webhook. I'd like to know if there's any pipeline alternative that exists.

Webhooks are faster and easier to setup than Pipelines 

When writing a Webhook, the process looks like this. Open the Webhook, write the Webhook, test the Webhook. Takes no time and little effort.

With Pipelines users have to log on to a service account in incognito mode. Then go through an arduous process of waiting for drop down lists to load and dragging little images around on a screen, etc etc... it's too many layers of abstraction for anyone who knows how to write a Webhook. 

Until the Pipelines process is as fast or faster than the Webhooks process, there is little to no value in using Pipelines.

Webhooks still have great value and it is a mistake to remove them from the rich feature set Quickbase has to offer.

Will there be a migration tool provided like Automations migration to Pipelines?

I’m not so concerned about Quickbase Actions, I think I have two, but we use a lot of webhooks. To get rid of webhooks would be a HUGE downgrade, as webhooks are immediate and good for completing simple, instant actions. Pipelines can still take a while to trigger and cannot do immediate actions. This will cause workflows to pause, and users to have to keep reloading a page to see if an action has occurred. Lately we have even increased our usage of webhooks for adding templated items such as tasks on a project, invoicing headers and line items, and change logs/audit logs. With pipelines a user won’t be able to add a project and immediately see the tasks when the page reloads. They’ll have to sit and wait for pipelines. This will also cause issue with Quickbase released apps in the exchange, such as Ryan Pflederer’s App Library, which uses webhooks to manage schema changes.

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.

Thanks for all the comments so far, everyone. I want to ensure Qrew members see that we're reading these comments, and there's a plan to address the concerns being raised soon. 

Ideally it makes sense. In practice pipelines don't have drag & drop. They have click...wait...drag....wait....drop...uh oh, didn't drop correctly....drag again...wait...

There are still so many functional problems with pipelines if anyone over there thinks they are ready to replace webhooks and actions then I'd love to show you how they actually function in a large app.

I'm willing to make a list of issues if it will do any good...

Hi Everyone, if you are attempting to Add a comment here and unable to, it's likely due to a security setting in how your account was first configured. We'll be addressing this in our site maintenance on April 1st. In the meantime, if you have concerns over the announcement in this blog, you can share them in this discussion: 

https://community.quickbase.com/discussion/bringing-attention-to-the-end-of-life-for-webhooks#bma069ed71-4ccd-4f47-882f-018e5c871027