QB Actions vs. Pipelines vs. Automations
Can someone define the differences between these, Pros/Cons, and when to use which one vs. the other ones. I understand that pipelines connects to other apps, but it can also work with changing things...
Forum Discussion
Great question Megan and good discussion! At the high-level, Actions, Automations and Pipelines have a lot of similarities, but they were built in different eras. Actions capability was one of our first entry points into the workflow automation space. While it was powerful and strong innovation at the time, we quickly realized that a new approach is necessary to empower our builders to continue automating their workflows. As a result, we designed and built Quick Base Automations capability, which has a similar tech stack as Actions capability, but is certainly a lot more powerful and has a better UX. As we continued our innovation journey in this space, through your and other customers' feedback we learned Automation is great but it's also limited in terms of scale as well in terms of capabilities around data transformation and integration. As a result, we delivered a completely new Platform - Quickbase Pipelines - for addressing all workflow automation and Integrations requirements you have. The reason I'm sharing this is that it's an important context to have. As you make technology decisions, it's important to know that the future of Quickbase in terms of workflow automation and integration is Pipelines and all our strategic investments are focused on improving the capability and build next-generation no-code workflow automation and integration platform. Hope this context helps!
------------------------------
Gevorg Hovsepyan
Senior Product Manager
Quick Base, Inc.
Cambridge MA
------------------------------
------------------------------
Gevorg Hovsepyan
Senior Product Manager
Quick Base, Inc.
Cambridge MA
------------------------------