The Multiple Paths feature in viaSocket allows you to split your workflow into different paths, with each path performing specific actions based on the conditions you set. You can define these conditions using operators like "less than" or "greater than," giving you full control over how your data moves through the workflow and ensuring that different actions are triggered depending on the criteria you’ve defined.

For example: If event A occurs in your trigger app, act X. But if event B happens, act Y instead.

How to get started with Multiple Paths

Step 1: Once logged into viaSocket, navigate to the workflow editor.

Step 2: In the workflow editor, search for and select your trigger app. Connect your account, configure the trigger step, and test it to ensure it's working properly.

Step 3: Next, add an action to your workflow, and select the “Multiple Paths” feature from the built-in tools to create different routes based on your conditions.

Step 4: Create path branches and define specific conditions for each branch. Based on these conditions, the data will follow the appropriate path, ensuring the right actions are taken for each scenario.

Step 5: Test your paths.

Step 6: Now, add actions to each path, just as you would in any workflow, ensuring they match the conditions for each branch.

Step 7: Once you've finished adding your paths and actions, be sure to test the workflow and publish it to start running.

Example of Using Multiple Paths

If you send personalized messages whenever their status changes in your CRM. Then in that scenario, you can use multiple paths like this : 

When a customer's status updates in your CRM, you can set up two paths:

In Path A, if the status is exactly "new customer," send a personalized welcome message. In Path B, if the status is "inactive," send a re-engagement message to encourage them to return.

Importance of using Multiple Paths in your Workflow

1. Personalization: Set different actions for different conditions.

2. Efficiency: Automate tasks for various situations in one workflow.

3. Flexibility: Handle multiple scenarios based on the trigger.

4. Simplicity: Combine actions into one workflow instead of creating many