Actions vs pipelines Best Practice
I have not actually used QB Actions. But in looking, for simple tasks, this seems like it may be a good way to go. If I make an action, it won't interfere with all my pipelines running, and also allow...
Forum Discussion
If you are officially ask QuickBase about this they will probably say that their long-term vision is to have a single path for these automated functions and of course that is Pipelines. But my personal opinion is that an Action is just a Webhook with a pretty face on it. Nothing more. That is why they run wonderfully instantly. I think there is zero chance that they would ever declare end of life on webhooks, so it seems unlikely they would ever declare end of life on Actions. But that is just my semi informed opinion and of course I don't live inside the braintrust of QuickBase.
One disadvantage of Actions is that they can be a little obscure to find particularly when you are debugging because you have to check each separate table to see if there is an Action being triggered. Also there may be a limit of 10 Actions per table. With Automations at least you could go to one place and see all the Automations for that App.
------------------------------
Mark Shnier (Your Quickbase Coach)
mark.shnier@gmail.com
------------------------------
One disadvantage of Actions is that they can be a little obscure to find particularly when you are debugging because you have to check each separate table to see if there is an Action being triggered. Also there may be a limit of 10 Actions per table. With Automations at least you could go to one place and see all the Automations for that App.
------------------------------
Mark Shnier (Your Quickbase Coach)
mark.shnier@gmail.com
------------------------------
- Actions are just so damn fast ! I absolutely love them.
I only wish there were more than 10 actions per table honestly
------------------------------
Prashant Maheshwari
------------------------------
