My workflow needs to do different things depending on the data coming in, and I want to set that up properly. How does branching and conditional logic work in 3B? I’m curious how you express “if this, then that,” how multiple paths play out, and whether branches can come back together later. A walkthrough or example would be great.
Coming from Tines Stories, this is the bit where the mental model shifts! 
There’s no Condition action to place, and no paths to draw. You describe the decision in plain language and 3B builds the logic into the steps, so “if this, then that” is something you say rather than something you assemble.
So instead of planning the shape, describe the behavior. For example:
When a ticket comes in, check the severity. If it’s critical, page the on-call engineer in Slack and create a Jira issue. Anything lower, just add it to the daily digest. Either way, log it to the tracking sheet.
That last sentence is your paths coming back together, and it’s all 3B needs to handle it. Being explicit about what happens in every case, including the leftovers, is what will make the difference here
One terminology heads-up: in 3B, branches are draft versions of a workflow (like Git branches) rather than conditional paths through it.
It’s all about your prompting skills here, and being clear in what you want 3B to do. Anatomy of a good prompt covers describing this kind of thing well.