Introducing Shadow Flow, a innovative feature designed to manage complex, multi-step workflows by enabling parallel supporting workflows that operate alongside the primary workflow. Whether managing internal steps, coordinating parallel approvals, or collaborating with external stakeholders, Shadow Flow provides a seamless way to execute parallel processes, selectively controlling visibility into certain aspects of the flow, without disrupting the main workflow.
Watch our video overview or dive into the detailed breakdown below to learn more.
What Shadow Flow does
Shadow Flow allows businesses to launch dependent workflows in parallel to the primary flow, offering the flexibility to either keep certain processes hidden or selectively visible to roles based on the context. Using the Flow Template Builder under the "Control" section, users can drag and drop Shadow Flow to define where parallel processes should occur without interrupting the workflow.
Setting up Shadow Flow
Adding Shadow Flow to your workflow is straightforward:
- Access the Flow Template Builder: Navigate to the Flow Template Builder.
- Locate Shadow Flow: Under the "Control" section on the left-hand interface, drag and drop the Shadow Flow element.
- Position Shadow Flow: Place it where internal processes need to occur within the workflow.
- Configure Shadow Flow: Define the tasks, logic, and actions required for the internal flow.
- Save and implement: Test the workflow to ensure seamless integration before deploying.
Key benefits
- Efficiency: Parallel workflows reduce bottlenecks, ensuring faster task completion.
- Coordination: Internal teams can collaborate on backend tasks without disrupting client-facing workflows.
- Focus: Clients remain engaged with their tasks while internal operations are handled discreetly.
- Clarity: Complex workflows are simplified with clear separation between internal and client-facing processes.
How Shadow Flow works
- Internal-only processes: Shadow Flow is visible only to internal teams and does not affect the client’s view.
- “Wait” Step: Clients see a placeholder “Wait” Step while internal tasks are completed.
- Dependent actions: Once the Shadow Flow is complete, the next step in the main flow is triggered automatically.
- Parallel processing: Multiple Shadow Flows can run simultaneously, enhancing operational efficiency.
Use cases for Shadow Flow
- Onboarding simplified: Internal tasks like compliance reviews or backend setup run parallel to client onboarding steps. This ensures readiness for subsequent actions without exposing backend operations.
- Document review: Internal departments can independently review documents before proceeding to client-facing steps.
- Product deployment: Backend configurations and checks are completed without interrupting the client workflow, ensuring a smooth deployment experience.
Important notes
- Shadow Flow can only be created within the Flow Template Builder.
- It is unavailable in instant flows, runtime workspaces, or live workspaces.
- Data from the main flow is accessible to Shadow Flow through Dynamic Data References (DDR).
- Shadow Flow cannot be nested within another Shadow Flow.
- Saving a flow as a template does not save Shadow Flow configurations.
Shadow Flow revolutionizes workflow management by enabling businesses to handle backend operations with precision and efficiency. Internal teams can focus on their tasks, while clients enjoy a seamless, distraction-free experience.
