In the last two weeks we threw wide the gates and Pipelines went live to all our of customers and we continued launching new channels that Pipelines can integrate with. Bringing together the power of low-code app development with the speed of our new low-code integration and automation capabilities, in one POWERFUL platform. Builders can now orchestrate workflows across their entire ecosystem of software tools in all new ways with Quick Base Pipelines. Using our visual interface, you can design your processes and connect to our library of third-party integration channels.
Note: On Wednesday, April 15, 2020 we concluded our phased roll out of the Pipelines technology for Quick Base customers. If your account has not been activated please submit a support case.With so many features and so many channels available to you it can be a bit daunting to know where to start. That is why this month's Community Tip Jar is focused on tips and tricks for Pipelines. Have you already learned a new way you can use Pipelines you want to share? Perhaps you have a technique you are using to help you build Pipelines that has kept your integrations organized?
Right now the most popular Pipelines channel being built is Quick Base to Quick Base Pipelines and a great tip for getting started is making sure you have your User Tokens ready. Your User Tokens will help set which apps your Pipeline has the permissions to use when you are building your Pipelines so as you are planning to build your Pipelines it is helpful to think about which apps your Pipelines are going to use and create User Tokens that have access to all the apps being used. Then it is really helpful as well to name your User Tokens to match up to your Pipelines so at a glance you can remember which token is being used where in case you need to come back and change its permissions to match your changing needs.
When you are in the thick of building a new Pipeline it can be easy to focus on all the steps and getting the data lined up just right. One helpful tip as you start building more Pipelines is to make sure you name your Pipelines to help you remember which ones are live versus test Pipelines and to help you remember their purpose. It is easy to remember when you have one or two but as you build more a consistent naming convention can help you find and edit Pipelines fast. One suggestion is to use a consistent pattern like :"Process name: Clear verb describing at a high level what action the pipeline takes" so for example: "Factory Machine Management: Push Inspection Reminder from QB to Slack". Now instead of seeing Pipeline 3 in your list and wondering what it does at a glance you know what your Pipeline is set up to do when it needs to be updated or changed.
Looking for some additional resources to help you learn more about Pipelines? Below you can find webinars, release notes, and community how-to articles.
Getting Started with Pipelines WebinarPipelines Release NotesNow to Use The Bucket Channel To Schedule an Archive to BoxBuild Better Trend Reports with PipelinesGenerate Template Records with Pipelines