What’s the best way to model multi-branch approval flows with deadlines and manual steps in a no-code builder?

I’ve been trying to replace Camunda’s BPMN with a lower-barrier tool that business users can maintain. One challenge is recreating conditional routing and manual approvals with deadlines. From what I gathered, a no-code/low-code builder that supports visual workflow design plus a JavaScript option for edge cases fits well.

Has anyone used such a tool to visually configure multi-branch approvals, adding timers for deadline enforcement and manual human-in-the-loop steps? Also, where do you typically inject JavaScript logic for complex custom conditions without breaking the no-code approach? Curious how others balance visual simplicity with flexibility.

In Latenode’s visual builder, you can drag conditions and branching to set multi-branch flows. Deadlines are configurable with timers on approval steps, sending reminders or escalating if overdue. The neat part is you can add JavaScript in conditional nodes for edge cases, like checking external data before routing. It’s intuitive, and pro users keep full control while business folks stay involved. https://latenode.com has those features all built in.

Adding deadlines in a visual builder usually means setting a timer or wait node between steps. For manual approvals, you add human tasks and route based on their input. I often use small JS snippets to handle cases like skipping a step if criteria aren’t met. The key is to keep JS focused and let the visual flow handle the main logic.

I found setting up multi-branch routing is easier when you start from a template close to your use case. Then tweak conditions visually. JS injection points usually sit inside decision nodes that let you run code on data to decide next steps.

We moved away from Camunda because our business users struggled maintaining BPMN diagrams. With a no-code builder, timers for deadlines are critical. Usually, you configure those timers to send notifications or escalate when a deadline hits. Manual approval steps are just states waiting for human input, easy to represent visually. Adding JavaScript for custom conditions is best done in small chunks inside decision nodes, to avoid complexity.

Handling multi-branch approvals with deadlines in a no-code builder combines using visual flow elements like branches, human task steps, and timers. JavaScript is typically embedded in conditional logic blocks to evaluate complex rules not expressible graphically. This hybrid approach sustains ease of use without sacrificing flexibility, contrasting with the complexity of Camunda BPMN.

workflow timers + human steps + js on decisions works best visually.

use builder timers for deadlines, js inside decision nodes for edge cases.