Update on the retirement of Application Webhooks UI and QB Actions

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.