Flexible Workflow Control

When building powerful workflows in Alteryx, control over execution flow is key. While tools like the Block Until Done and Control Container offer sequential and conditional control, the Detour and Detour End tools allow you to skip, redirect, or bypass specific paths of a workflow, based on conditions—without deleting or redesigning your entire logic.

In this article, we’ll break down how the Detour and Detour End tools work, explore common use cases, compare them with alternative tools, and share best practices to get the most out of them. And of course, we’re pairing this workflow flexibility with a snack that reflects the concept: choose-your-own-flavor jelly beans—a sweet metaphor for picking the right workflow path.

What Are the Detour and Detour End Tools?

Alteryx’s Detour and Detour End tools are part of the Interface category, meaning they’re most commonly used when building analytic apps or macros. Their primary function is to provide a mechanism to conditionally control the path of execution.

✅ Detour Tool:

• Think of it as a “decision fork” in your workflow.

• It has one input and two output anchors (True and False).

• Depending on a condition—usually derived from a Radio Button, Drop Down, or Check Box Interface tool—Alteryx will choose which path to follow.

✅ Detour End Tool:

• The merge point where the two diverged paths from the Detour tool come back together.

• Ensures that only one path (the one chosen) is executed, and the workflow continues from there.

These tools do not require scripting or manual deletion to test multiple logical paths. Just like those jelly beans, you pick your flavor and follow that path!

Detour vs. Other Conditional Tools

Alteryx provides several ways to manage workflow logic:

While Detour is unique to interface tools, it’s ideal for apps where users select options like:

• "Do you want to apply this transformation?"

• "Include customer segmentation in this report?"

🔧 How to Use the Detour and Detour End Tools in Practice

Here’s a simple step-by-step guide:

1. Add Interface Elements

Let’s say you’re building an app with a checkbox asking: “Would you like to remove null values?”

• Drag in a Check Box tool.

• Label it appropriately.

2. Configure the Detour Tool

• Drag in the Detour tool and connect it to your data source.

• Connect both outputs to different paths:

  • True → Data Cleansing or Filter tool to remove nulls.

  • False → Directly to the next step (no cleansing).

3. Add the Detour End Tool

• Both paths should connect to the Detour End.

• This ensures the workflow rejoins cleanly before continuing.

4. Configure the Interface Designer

• Ensure the interface tool (checkbox) is configured to update the Detour's behavior using Action tools.

• Save as an analytic app.

That’s it! You’ve now added dynamic behavior to your workflow with minimal setup.

Practical Use Cases for Detour Tools

🎯 1. Optional Data Processing

Use the Detour to include or exclude steps like filtering, formatting, or joining additional data based on user input.

📊 2. Generating Different Reports

Users can select between “Summary Report” or “Full Detail Report.” Each option triggers a different path of tools, converging later.

🔁 3. Branching Logic in Macros

Macros often contain multiple calculation paths. Use Detour to switch between algorithms, aggregations, or output formats.

🚩 Common Pitfalls and Best Practices

✅ Do:

• Use Detour only in apps or macros, not standard workflows.

• Always close every Detour with a Detour End.

• Label branches clearly for readability.

• Test each path independently to ensure proper data flow.

❌ Avoid:

• Trying to use Detour without an interface input.

• Connecting both paths to the same downstream tools (can cause unexpected behavior).

• Nesting too many Detours—use containers instead when possible.

💡 Tips to Get the Most Out of Detour

1. Use Annotations: Make your intention clear to collaborators or future-you.

2. Combine with Interface Designer: You can use conditional groups to build powerful, interactive experiences.

3. Keep It Clean: Even if only one path is used during execution, both paths must be logically valid and not throw errors if unused.

🔄 Example: Real-World Workflow

Imagine an HR analytics app where users can:

• Choose to anonymize employee data (yes/no).

• Choose the report type (summary/detail).

Flow:

• Detour 1 → If anonymization is selected, scrub PII.

• Detour 2 → Choose reporting logic.

• Detour End → Merge into final output.

This keeps the app user-friendly, dynamic, and modular, allowing quick adjustments without redesigning the whole workflow.

🥨 Snack Pairing: Choose-Your-Own-Flavor Jelly Beans

Just like Detour tools, jelly beans offer multiple paths and flavors—but you choose just one. Whether it's watermelon, buttered popcorn, or the dreaded mystery bean, the metaphor stands: make a decision, and stick with that flavor of logic!

🔍 Final Thoughts: When to Reach for Detour Tools

Use Detour and Detour End when your app or macro requires interactive decision logic, like:

• Optional calculations

• Variable outputs

• Feature toggles

They're lightweight, intuitive, and seamlessly integrate into the Alteryx Interface Designer ecosystem. While not intended for static workflows, they're indispensable in building powerful, flexible analytic applications.

Happy snacking and analyzing!