Workflow

A workflow is a series of triggers, actions, and conditions designed to achieve a specific goal or outcome. Depicted as a flowchart or diagram, it illustrates how various triggers and actions interconnect.

DevRev’s workflow engine automates tedious tasks, providing precise control and efficiency. Leveraging AI through AgentOS, it creates adaptive, real-time workflows that handle complex tasks with minimal human intervention. AI agents interpret and execute tasks based on fuzzy inputs, enhancing productivity and efficiency. This shift from rigid workflows to adaptive automation aims to improve organizational processes and outcomes.

The workflow engine is a highly flexible solution enabling users to build personalized workflows tailored to their organization’s needs. Catering to both high-code and no-code users, it simplifies the creation of complex automations.

With our pre-built library of workflow nodes for common tasks, users can quickly implement powerful functions without writing custom code.

This combination of flexibility and a robust pre-built library ensures that you can easily design workflows that perfectly fit your organizational requirements.

🎥 Video: Workflow

Key features

AI-powered automation: Utilize out-of-the-box AI-based nodes and AI generation capabilities for intelligent automation that enhances productivity.
No middleware: Our workflow engine is natively built into the CRM system, eliminating the need for third-party tools and additional training.
Scalable performance: Handle thousands to millions of executions per day effortlessly with our scalable workflow engine.
Automations on one schema: Our Airdrop feature automatically transforms data from different sources. It enables you to create workflows natively in DevRev without the need to create fetch nodes or manually transform data.

Components

Workflow canvas: The field where you connect and visualize different steps in your workflow.
Steps: The building blocks of your workflow, shown on the canvas.
Variable selector: Used to insert variables into your steps during configuration. The variable selector is available through the Insert variable button. Entering double open curly braces ({{) in the text field is a shortcut to a compact list of available variables.
Toolbar: Located at the bottom of your screen, it provides tools to add new steps, align steps, zoom in/out, and more.

Workflow steps

Workflow steps are categorized into the following types:

Trigger: The event that initiates a particular process.
Action: Tasks that modify one or more objects in the system.
Control: Conditional (if-then) blocks to determine which actions to take based on an operand (variable) and an operator.
Delay: Wait to take an action.

AI nodes

We provide several native AI nodes out of the box to enhance your workflows.

Spam checker

The spam checker takes the ID of a ticket or object and determines whether the ticket or conversation is spam. You can use this output in your workflows as needed. For example, if the ticket is found to be spam, you can automatically add a comment to the ticket.

Suggest part

Often, your integrations create tickets or issues associated with a default part. The suggest part takes the ID of a ticket or issue and suggests a relevant part. You can use this to route your tickets or issues to the most appropriate part of the product. For example, when a ticket is created, you can find a relevant part and update the ticket with the suggested part.

Sentiment evaluator

The sentiment evaluator takes the ID of a ticket and assesses the customer's sentiment based on their comments. Sentiment values can be Delighted, Happy, Frustrated, Neutral, Unhappy, or Unknown. It also provides justification for the sentiment values. These values are only generated if there is a customer conversation on the ticket. For example, you can listen to a ticket update event, evaluate the sentiment, and send a comment to the account.

Prompt

Write your own LLM prompt to generate content that can be used in . For example, you can request a summary of a ticket based on the title and description.

Creating a workflow

Go to Settings and select Workflows. A canvas appears.
Enter a name for your workflow.
Select the steps you want to include by selecting them from the button toolbar.
Set your triggers. You can have multiple triggers within a single workflow.
To configure your workflow, utilize the data reference pane to select values from previous nodes.
Connect steps with multiple paths as needed, allowing for the management of complex workflows on one canvas.
To add conditional logic, use a control step.

Select a value for the LHS; select the appropriate operator; and enter or select a value for the RHS, which can be a literal value or one from a previous node.
Click Deploy.
If you need to modify the workflow after is has been deployed, click Pause, edit the workflow, then click Deploy to reactivate it.

Workflow example: Ticket auto-response

flowchart TD
%%{
  init: {
    'theme': 'base',
    'themeVariables': {
        'fontFamily': 'Segoe UI',
        'lineColor': '#000',
        'primaryTextColor': 'white',
        'primaryColor': '#2a33ff',
        'primaryBorderColor': '#62D65D',
        'secondaryColor': '#5D0E1C',
        'tertiaryColor': '#e6e6e6',
        'clusterBorder': 'white'
    }
  }
}%%
classDef attrs text-align:left
tc -->|Control| Control -->|If true| Delay -->|Action| AskAI -->|Action| AddC --> e(((End)))
Control --> |If false| e
Delay ~~~ e
tc(((Ticket
created)))
subgraph Control[If-else]
    attr[**Attribute:**&nbsp;<tt>Ticket&nbsp;Created/Output&nbsp;>&nbsp;Applies&nbsp;to&nbsp;part&nbsp;>&nbsp;Display&nbsp;ID</tt>
    **Operator:** Equals
    **Operand:** CAPL-18
    ]:::attrs
end
subgraph Delay
    dly[**Duration:** 2 minutes]
end
subgraph AskAI[Ask AI]
    pr["**Prompt:** “Summarize the ticket based on 
    {{<tt>Ticket Created > Output > Description</tt>}}, 
    {{<tt>Ticket Created > Output > Title</tt>}}, 
    {{<tt>Ticket Created > Output > Applies to Part > Name</tt>}}, and
    {{<tt>Ticket&nbsp;Created&nbsp;>&nbsp;Output&nbsp;>&nbsp;Reported&nbsp;By&nbsp;>&nbsp;Rev&nbsp;Org&nbsp;>&nbsp;Display&nbsp;Name</tt>}}.”"]:::attrs
end
subgraph AddC[Add comment]
    comm["**Object:**&nbsp;<tt>Ticket&nbsp;Created&nbsp;>&nbsp;Output&nbsp;>&nbsp;ID</tt>
    **Visibility:** External
    **Body:** “We have received your request for help with the following:
    {{<tt>Ask AI > Output > Output string</tt>}}. 
    A support agent will review the request and respond within your organization's SLA.”"]:::attrs
end