What this adds
The StretchCRM visual automation canvas (Automation V2) now includes the power nodes that define a HubSpot-class workflow tool, plus real actions that change your records:
| Capability | What it does |
|---|---|
| Branch by value (Switch) | Send a record down a different path based on a field value — for example route deals by region or contacts by lifecycle stage, with a default path for anything unmatched. |
| A/B split | Split enrolled records into weighted buckets (e.g. 50/50) to test two paths. The split is deterministic, so a record always lands in the same bucket even if the workflow re-runs. |
| Goal + early exit | Define an exit condition (the "goal"). When a record meets it, it leaves the workflow immediately and the rest of the steps are skipped. |
| Re-enrollment | Optionally let a record enter the same workflow again after its previous run finishes. |
| Real actions | Assign owner (explicit or via your round-robin/load-balanced assignment rules), Move deal stage (logged to stage history), and Create deal now actually run — they are no longer placeholders. |
How to build it
- Open StretchCRM → Automations and open or create a V2 (canvas) workflow.
- Drag a Switch (by value) node onto the canvas. Pick the field to branch on and add one case per value, each pointing at the next node. Set a default route for unmatched records.
- To test two treatments, drag a Split (A/B) node and give each branch a weight.
- Open the Goal & re-enrollment panel to set an exit condition and (optionally) allow re-enrollment.
- Add action nodes — Assign owner, Move deal stage, or Create deal — wherever you want the workflow to act.
- Simulate to preview the path a sample record takes, then enroll records.
Availability
Rolling out. Advanced automation is released behind a feature flag and is enabled per account. If you do not yet see the Switch/Split nodes or the Goal panel, they have not been turned on for your workspace yet. The underlying engine is complete and tested; ask your StretchSuite contact to enable it.
Tips
- A Split is for testing paths; a Switch is for deterministic routing by data. Use Switch when the outcome should depend on the record, and Split when you want a controlled experiment.
- Actions only fire when the advanced capability is enabled for your account — with it off, an action node is inert and changes nothing.
Was this helpful?
Help us improve this article
Use these controls to share whether this answer solved the issue. Feedback helps prioritize updates to StretchSuite Support.