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
My two cents in addition to everything Mark has already mentioned:
Automations:
Pros: Much faster than pipelines. Stable, user friendly. Much easier for a table import.
Huge Pro: Action can be 'if modified OR added'. Pipeline you need to build 2 pipelines.
Cons: Cannot handle complex automations (often times where I would need 2 or 3 automations, Pipelines can do it in one).
Pipelines:
Pros: Much more flexibility, more capabilities for complex automations. Can connect to external apps. Great potential.
Cons: Buggy and frustrating. I've had to rebuild a number of pipelines because of bugs. You can't rearrange order of steps properly, it will have weird lagging out problems and not save your work, etc. Also, runs very very slow, as compared to automations.
------------------------------
Mike Tamoush
------------------------------
Automations:
Pros: Much faster than pipelines. Stable, user friendly. Much easier for a table import.
Huge Pro: Action can be 'if modified OR added'. Pipeline you need to build 2 pipelines.
Cons: Cannot handle complex automations (often times where I would need 2 or 3 automations, Pipelines can do it in one).
Pipelines:
Pros: Much more flexibility, more capabilities for complex automations. Can connect to external apps. Great potential.
Cons: Buggy and frustrating. I've had to rebuild a number of pipelines because of bugs. You can't rearrange order of steps properly, it will have weird lagging out problems and not save your work, etc. Also, runs very very slow, as compared to automations.
------------------------------
Mike Tamoush
------------------------------