Multiple Paths (If Conditions)

Multiple Paths lets you branch a single workflow into different routes based on conditions you define. Each path runs its own set of actions — only when its condition is met.

Example: If a customer's order value is over $100 → send a "Premium Customer" message. If under $100 → send a standard thank-you message.

Click + Add Step in the workflow editor. Under Built-In Tools, select Multiple Paths (If Conditions).

The MultiPath panel opens with Path 1 ready to configure. Enter your condition in the input field (e.g., order amount > 100) and click SAVE.

You can type the condition manually or use Ask AI to generate it from a plain-English description.

Once the condition is saved, the canvas shows your path branch with an IF block and an ELSE block side by side. Click + Add or drag step here inside the IF branch to add actions that run when the condition is true. The ELSE block handles all cases where the condition is not met.

To add another condition branch, click the + button on the canvas between paths. A new Path 2 appears in the MultiPath panel. Define its condition and save — viaSocket automatically routes data to whichever path condition matches first. If no IF condition matches, the Else path executes.

Once all paths and their conditions are configured, click GO LIVE to publish the workflow. viaSocket will automatically route each run to the correct path based on the conditions you've defined.

You can place a Multiple Paths step inside another path branch to handle multi-level conditions - similar to nested if-statements in code.

Example — Order Processing:

• If order value > $100 → apply free shipping

  • If address = US → also add a discount

  • If address ≠ US → apply international fee

• If order value < $100

  • If same city → use local delivery

  • Else → use standard shipping

This lets you handle complex logic in a single workflow without duplication.

CRM Message Automation — when a customer's status changes:

• Path 1: status = "new customer" → send a personalized welcome message

• Path 2: status = "inactive" → send a re-engagement email

• Else: log the record for manual review

One workflow covers all three cases.

• Personalization — trigger different actions based on data values

• Efficiency — handle multiple scenarios inside a single workflow

• Flexibility — works with any data field from any trigger or previous step

• Simplicity — no need to build separate workflows for each condition