How to set up and use Paths action
Run different sets of actions based on conditions. Follow these steps:
*This is an advanced feature. Reach out to our team and we'll help you set it up!
Example:
For the purpose of this help article, we'll go through an example. We will be creating a workflow that takes in a question about a product, and routes the question to different Cassidy Assistants depending on which product the question was asking about.
For this example, we have 4 different products: ClientConnect, CaseSight, DocuSprint, and LegalSprinter. For each product, we have created a corresponding product knowledge Assistant:
We'll start this workflow with a manual trigger with a text input (in this case "Product Question"). *Variables are inputs from the trigger, or outputs from previous steps.
Then, we'll have a "Categorize Text" action that categorizes the Product Question by the product type. For this example, the categories will correspond to the 4 product types we mentioned above (ClientConnect, CaseSight, DocuSprint, and LegalSprinter):
Add a Paths action: While editing a workflow, click the plus button between existing blocks. This will open a modal where you can select from Cassidy's pre-configured actions. Choose the Paths action to add it to your workflow.
Rename the action (if needed): If you want to make the action more descriptive or easier to reference as a variable later, enter a new name.
Rename the paths (Optional): If you want to make the paths more descriptive, you can enter a new name for each path. This can help clarify the purpose of each path.
Create a condition for the first path: Define the conditions that must be met for the first path to run. For example, we will set a condition that will make it so the "ClientConnect question" path will execute if the categorize text action categorizes the text as "ClientConnect". To create a condition:
Click on the "Add Condition" button
Fill out the first input with the field you would like to evaluate. This can be a variable from a previous step or the trigger.
Make your selection for the operation condition (e.g., Equals, contains, etc.).
Fill out the next input with the value it should be evaluated on.
Add more conditions (Optional): You may add more conditions by clicking on the "And"/"Or" buttons. By adding a conditional with the "And" operator, this will make it so both conditions must be true for the path to run. By adding a conditional with the "Or" operator, this will make it so the path runs if either conditions are true.
Add more paths (Optional): You may add as many paths as needed to suit your workflow's requirements. For each new path, you should specify the conditions that need to be met for the path to run. To add a new path, click on the plus sign next to the path tabs. For our example, we have 4 different products, so we will make 4 different paths:
Configure the last path's conditions (Optional) : By default, the "Run if no other paths are run" toggle is switched on for the last path. This path will run if the conditions of all other paths are not met, serving as a catch-all. If this toggle is switched off, you can customize the conditions for this branch. Note that if you turn this toggle off, it's possible that none of the paths will run if the conditions for each branch are not met. For our example, we will turn the toggle off and set a condition where this path should only execute if the categorize text action categorizes the text as "LegalSprinter":
Add actions within the Path: Click the plus button inside each Path to add actions within the Path. You can define a different set of actions for each path. For our example, we will add an action to route the product question to the specialized Cassidy Assistant:
Customize output for each path (Optional): Return to the Path's settings and toggle on "Customize Output". Click the "Customize Output" button at the bottom of each path's tab to configure what the output of the path should be. This allows you to define specific outputs for each branch based on the conditions met.
* If you are referencing the output of the path in subsequent workflow steps, the best practice here would be to use "customize output" so that each path has a uniform output
Use the Path's output: If you want to use the output of the Path, you can add an action after the Path and reference the Path's output. Only one Path can ever be run at once, so the value of the path output will be output of whichever Path ran. For example, in our case, we can add a Send Email action to send the answer to the product question generated by our workflow. You can reference the Path output as a single variable.
Run the workflow: You can run the workflow.
Here's a sample of the type of output you can expect:
