Nesting: workflows within a task

Nesting empowers you to embed workflows within other workflows through the Subflow task type. By calling upon existing workflow definitions stored in the database, Nesting bypasses their inherent time constraints and external dependencies. However, it's important to note that all dependencies of the individual tasks within the nested workflow remain fully active.

The introduction of Nesting unlocks significant advantages. It facilitates the transfer of output properties between workflows, tasks, and even other nested workflows. This creates a more dynamic and adaptable automation ecosystem.

Nesting also promotes exceptional reusability of workflow definitions. Instead of creating multiple, similar workflows, you can now adapt existing ones to diverse scenarios by nesting them within different parent workflows. This not only streamlines automation design but also simplifies the overall automation architecture. By allowing for workflows within workflows, Nesting reduces the number of directly connected workflows, enabling you to create more manageable and comprehensible macro-blocks of automation logic.

Increased efficiency

By automating data transfer between workflows and tasks, you can save significant time and reduce the potential for manual errors.

Enhanced adaptability

You can easily repurpose and combine existing workflows to respond quickly to changing business needs and scenarios.

Reduced development overhead

Minimize the creation of redundant workflows, freeing up your resources and accelerating the design of better automation solutions.

Simplified automation management

A more hierarchical and modular structure with fewer top-level workflows leads to easier maintenance, monitoring, and troubleshooting.

For more information, see Subflow tasks.