Create Your First Workflow
Build powerful automation workflows with visual tools, AI-powered decisions, and integrated actions that execute automatically based on triggers.
Visual Builder
Drag-and-drop interface for creating complex workflows easily.
AI-Powered
Intelligent decision nodes that analyze conversations in real-time.
Flexible Tools
Send emails, SMS, webhooks, schedule appointments, and more.
Auto-Execute
Workflows run automatically on pre-call, post-call, or post-chat triggers.
Understanding Workflows
A workflow is a powerful way to automate complex tasks, especially after conversations end. It's a chain of automatic actions that handle your follow-up work: sending emails, scheduling appointments, creating tickets, updating your CRM, invoking webhooks, all happening seamlessly in the background without any manual effort.
Understanding Workflow Components
Node Types
Start Node
The beginning point of every workflow. This is where your automation starts when triggered by an event (like a call ending). It automatically receives all the information from the conversation.
Decision Node
The brain of your workflow. It analyzes what happened in the conversation and decides what to do next. You can create multiple paths like "Schedule Appointment", "Send Information", or "Create Ticket" based on what the customer needs.
You'll configure:
- โข A clear title describing what decision is being made
- โข Instructions telling the AI what to look for
- โข Different paths the workflow can take based on the decision
Tool Node (Execute Node)
The action taker. These nodes actually do things - send emails, create calendar events, send text messages, or update your systems. The AI automatically writes the content based on what was discussed in the conversation.
Connections (Edges)
- โVisual lines connecting nodes define the flow of execution
- โMust connect from output handles (right side) to input handles (left side)
- โCannot create circular loops
Step-by-Step Example: Creating a Support Issue Handler Workflow
Let's build a simple workflow that automatically handles support issues after a call ends. This workflow will check if the customer reported any issues and route them appropriately - urgent issues go directly to a technician via SMS, standard issues create a support ticket via email, and general inquiries need no action.
Start Your Workflow
First, let's set up the basics:
- Navigate to your agent in the portal
- Click on the "Workflows" tab
- Click "Create Workflow" button
- Name it: "Issue Handler"
Add an Issue Severity Decision Node
Now let's add a decision node to check if the customer reported an issue and determine its severity:
Add the node:
- Drag a Decision Node from the left panel onto the canvas
- Position it to the right of your Start node
- Click on the Decision Node to configure it
Configure the decision:
Title:
"Issue Severity"
Instructions:
"Analyze if the customer reported any technical issues or problems. Classify based on severity: - Urgent Issue: System is down, critical functionality not working, business operations affected - Standard Issue: Minor bugs, feature questions, non-critical problems that need support - No Issue: General inquiry, product information, or already resolved during the call"
Outputs (add these three):
๐ Connect it: Draw a line from the Start node's output to the Decision node's input
Add Actions for Each Issue Type
Now let's add specific actions based on the issue severity:
Path 1: Urgent Issue โ Alert Technician
- Drag a Tool Node to the upper right
- Click it and select "Send SMS" as the tool type
- Configure:
- โข Title: "Alert On-Call Technician"
- โข Phone Number: Your technician's phone number
- โข Instructions: "Send urgent alert with customer name, phone number, and brief description of the critical issue"
- Connect from Decision's "Urgent Issue" output to this node
Path 2: Standard Issue โ Create Support Ticket
- Drag a Tool Node to the middle right
- Click it and select "Send Email"
- Configure:
- โข Title: "Create Support Ticket"
- โข To: [email protected] (your helpdesk email)
- โข Instructions: "Create a support ticket email with subject line 'New Support Ticket - [Customer Name]'. Include customer details, issue description, and conversation summary"
- Connect from Decision's "Standard Issue" output to this node
Path 3: No Issue โ No Action
For the "No Issue" output, we don't need to add any tool node. This path will simply end without taking any action.
๐ก This is perfect for general inquiries that were fully resolved during the call and don't require any follow-up.
โ Your Workflow Should Look Like This
After completing the steps above, your workflow canvas should display this structure:

The workflow shows: Start โ Issue Severity (Decision) โ Three output paths (Urgent Issue, Standard Issue, No Issue)
Your Complete Workflow
Great! You've successfully built a support issue handler workflow.
This workflow will now:
- Check every call for reported issues
- Alert technicians via SMS for urgent problems
- Email support team for standard issues
- Take no action for general inquiries
Activate Your Workflow
Finally, set up when this workflow should run:
- Save your workflow
- Go back to the workflows main page (click on the "Workflows" tab in sidebar)
- Click on the "Manage Triggers" button
- Select "Post-Call" trigger and click on the "Add Workflow" button
- Add your "Issue Handler" workflow
๐ Your workflow is now live! It will run automatically after every call.
Tips for Your First Workflow
๐ฏ Start Simple
Begin with 2-3 outputs in your decision node. You can always add more paths later.
๐ Clear Instructions
Write detailed instructions for decision nodes so the AI understands exactly what to look for.
๐งช Test Everything
Test each path with realistic conversation examples before going live.
๐ Monitor & Improve
Check execution logs regularly and refine your workflow based on real results.
๐ก Remember: Workflows are powerful automation tools that improve over time. Start simple, test thoroughly, and gradually add complexity as you understand your automation needs better.