Blog Post

The Qrew Blog
4 MIN READ

Update on the retirement of Application Webhooks UI and QB Actions

BrianCafferelli's avatar
BrianCafferelli
Quickbase Staff
2 years ago

Top of FormQB

NOTE: Since we originally published this article, we have updated the date when Application Webhooks UI and QB Actions will reach End of Support. The new date is June 30, 2025 – when both creating and editing actions and webhooks will be locked. Note that locking create and edit does not apply to Webhooks APIs or the Webhooks channel in Pipelines.  

 

Quickbase makes it easy to reduce repetitive tasks and orchestrate workflows, uniting disconnected data onto one platform. With Pipelines, business users can manage both automations and integrations in one place. And we have been hard at work enhancing our Pipelines capability based on your feedback. Now, as we continue to look toward the future, we must also evaluate the role of older and less flexible features like the Application Webhooks UI and Quickbase Actions. These two features will reach End of Support on June 30, 2025, and existing actions and UI-based webhooks will become read-only at that time.

 

What this change means for you

After June 30, 2025, the Application Webhooks UI and QB Actions will no longer be supported. At that time, there are some changes we are making to those features:

  • Any actions you’ve already created will continue to run. However, at that time they will become read-only, so you will not be able to edit them or create new ones.
  • Any webhooks you’ve already created will continue to run. However, at that time the ability to create or edit Application Webhooks through the UI will be disabled.
  • You will still be able to enable and disable existing actions and webhooks after this point.

We strongly recommend that you migrate any remaining actions and webhooks to use pipelines instead, which enable more powerful and flexible workflows.

If you are an app builder, you already have access to create pipelines. If you do not see the Pipelines link below, please contact your account administrator to get access.

 

 

The Pipelines Advantage

We have been continuously adding new capabilities and tools that make it easy for you to transition your workflow automations to our newer and more powerful Pipelines technology. Not only will this ensure that you don’t experience any disruption to your business or your processes, but it also opens the door to new workflow ideas that can connect across multiple systems.

  • Pipelines supports all QB Actions and Webhooks features – Pipelines supports all the features you’ve been leveraging within QB Actions and Webhooks, including the ability to query the previous value of a field.
  • Pipelines enables more sophisticated logic than Quickbase Actions and Webhooks – Pipelines supports more powerful business logic than QB Actions and Webhooks, including branching and looping, as well as parsing text.
  • Pipelines gives you the ability to scale workflow across systems – In addition to orchestrating workflow within your Quickbase ecosystem, Pipelines includes drag-and-drop integration with over 40 products including Outlook, Slack, and Sharepoint.

 

Recent Pipelines Improvements

We are making major improvements to Pipelines, which make it easier to build, enable more powerful pipelines, and make them easier to govern and manage.

 

 

Easier to build:

More powerful and reliable pipelines:

  • New integration channels for Fastfield and Snowflake
  • Improved Outlook channel enables replying to email thread
  • Improved Quickbase channel enables exporting records to CSV
  • Pipelines trigger up to 5x faster
  • Increased limit on outbound webhooks from 20/second to 50/second

 

Improved governance:

 

Focus areas for improving Pipelines

We’ve gotten feedback from many of you on Pipelines about what’s going well and where we have opportunity to improve. Thank you for taking the time to share your thoughts with us. Getting this perspective is essential to help us evolve our product and make sure we are serving the community well. Looking forward, we are exploring a number of Pipelines enhancements:

  • Support for official service accounts
  • New bulk trigger step
  • Initial trigger time improvements
  • Connection Central improvements

We plan to keep existing actions and webhooks running for the foreseeable future. If this changes, we will make sure to provide a reasonable amount of notice first.

Learn more

Updated 11 months ago
Version 4.0

27 Comments

  • DwightMunson1's avatar
    DwightMunson1
    Qrew Assistant Captain

    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.

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

  • 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.

  • DineshV's avatar
    DineshV
    Qrew Trainee

    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.

  • 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 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.