OK so we use a lot of automations, as Quick Base is a CRM / ERP for us. So we have automations that fire when certain conditions are met, and now that they are going away, I'm having trouble getting a pipeline to do exactly the same task. Specifically, I can't seem to filter the pipeline down the way I can an automation. is there something I'm missing here? Surely there is a way to filter...
Example: When an opportunity's status is changed to WON, and it also has a $ value in a certain field, and it's territory is X, then perform Z action. I can't seem to get a pipeline to replicate this and I'm not really finding what I need in any of the documentation. Any help out there?
------------------------------
Thanks,
Chris Newsome
------------------------------
Question
Pipeline conversion from an automation... not sure how to get the same results
+10This topic has been closed for replies.
+17Hi Chris,
One thing I've found helpful if you haven't used it yet is to try the Migration option on an existing Automation. That will convert it into a Pipeline and you can actually go back in and see what the Pipeline version of an Automation looks like as a one to one comparison. Then you can see how the filters are nested and where the options appear. That can be helpful when you are first transitioning to get to see some of your business logic right in Pipelines.
Typically what you are looking for is in the trigger there is a section to add a query and the fields you are interested in for subsequent steps. For example in the image below you can add in that you care about location name in your subsequent steps and then further down you can Query on that to say you only want location names that start with "Cambridge". It can get more complicated as you add more conditions and select either and or or, but that is how to get started.
If you are looking for branching out what happens based on these values in your Pipeline that can also be covered by adding conditions, this help doc goes more in depth on how you can instead add logic into a Pipeline to say if certain values then run this action, if not then do another action entirely.
------------------------------
Evan Martinez
------------------------------
One thing I've found helpful if you haven't used it yet is to try the Migration option on an existing Automation. That will convert it into a Pipeline and you can actually go back in and see what the Pipeline version of an Automation looks like as a one to one comparison. Then you can see how the filters are nested and where the options appear. That can be helpful when you are first transitioning to get to see some of your business logic right in Pipelines.
Typically what you are looking for is in the trigger there is a section to add a query and the fields you are interested in for subsequent steps. For example in the image below you can add in that you care about location name in your subsequent steps and then further down you can Query on that to say you only want location names that start with "Cambridge". It can get more complicated as you add more conditions and select either and or or, but that is how to get started.
If you are looking for branching out what happens based on these values in your Pipeline that can also be covered by adding conditions, this help doc goes more in depth on how you can instead add logic into a Pipeline to say if certain values then run this action, if not then do another action entirely.
------------------------------
Evan Martinez
------------------------------
Sign up
Already have an account? Login
Login to the community
Login with Quickbase US – quickbase.com Login with Quickbase EU – quickbase.eu
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.