We started to migrate everything to Pipelines. You can filter Pipelines using your own custom tags or by Channel. e.g. Webhooks. This should also help dodge table limits.
For us, this includes the "simple" tasks which may only have one step and may have historically been an Automation/Action/Webhook. This approach keeps things consistent and I imagine helps future proof the app since
Automations are being deprecated. Speed, error and access control reporting seem to be improving as QB further develops Pipelines as well.
I don't have any official info from QB, this is just our internal best practice.
------------------------------
Brian
------------------------------
Original Message:
Sent: 11-11-2022 14:33
From: Mike Tamoush
Subject: 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 allows me to clean up my Pipelines and only have necessary complicated ones.
Is there a reason to use or not use Actions vs Pipelines? What is the best practice?
------------------------------
Mike Tamoush
------------------------------