Kick off automations from forms as well as pipeline statuses
under review
G
Geoff Brandt
Agreed. Thanks Geoff for re-opening.
Starting with a form naturally and intuitively filters a "path" through the prospect/client journey vs the blanket nature of having stages be the only trigger. (Interestingly, this is essentially what is achieved is you use multiple (form specific) entry stages - Inquiry1, Inquiry2 etc. as a workaround.
The only other option presently is doing gymnastics with form field answers which can be a hack if such form fields have no use other than to force an automation. I guess if there were a way to make fields invisible with default answers it would be a quick fix, but not a very elegant long term solution.
Geoff Mina
under review
Re-opening
Geoff Mina
closed
Decision node makes this request possible with a single pipeline status and worfklow.
Geoff Mina
Hi Elle Baldry - the philosophy here is that the meeting or form submission create an opportunity (automatically) in the Pipeline and then that kicks off the workflow.
Are you seeing use cases where you would have a submission and not want to create an opportunity, but still automate a bunch of things after a meeting gets booked?
E
Elle Baldry
Geoff Mina: I was thinking more for having the additional option for the form or meeting to kick off the workflow.
Some uses mean that the workflow would vary based on which agreement they need based on the services being provided.
At the moment if they go into a particular pipeline status (proposal for instance) there's no way of sending that specific agreement automatically as the workflows for all opportunities in that proposal status would kick off.
I think in every use you would still want it to log the opportunity though. The workaround is to have different pipeline status' but then that makes the interface look messy when you are breaking it down into different services being provided rather than high level.
Geoff Mina
Elle Baldry: you could check the form name or some field value in the submission to branch your workflow using a decision node.