Question 1

What are workflows and how do they work?

Accepted Answer

Workflows are visual automation flows that extend your AI chatbot's capabilities. You can create multi-step processes using drag-and-drop nodes like forms, API calls, webhooks, and conditional logic. When a user's message matches a workflow trigger, the workflow executes automatically, handling complex tasks like booking appointments, processing orders, or collecting information.

Question 2

Do I need coding skills to build workflows?

Accepted Answer

No coding required. Workflows use a visual drag-and-drop builder where you connect nodes to create automation flows. You can configure API endpoints, form fields, webhooks, and conditional routing through simple forms—no programming knowledge needed.

Question 3

How do workflows get triggered?

Accepted Answer

Workflows are triggered automatically when the AI understands that a user's intent matches the workflow's purpose. The system analyzes the workflow's description and purpose to determine intent, so even if someone phrases their request differently, the workflow will activate if the intent aligns with what the workflow is designed to do. You can also set up multiple workflows per widget with different priorities.

Question 4

Can I test workflows before going live?

Accepted Answer

Yes, you can test workflows directly in the builder. The test feature lets you simulate conversations and see how the workflow executes step-by-step, so you can verify everything works correctly before deploying to your live widget.

Question 5

What can I do with workflow nodes?

Accepted Answer

Workflows support multiple node types: Forms (collect user information), API Calls (connect to external services), Webhooks (send data to other systems), Messages (send automated responses), Ask Question (interactive prompts), Calendar Booking (schedule appointments), and RAG Search (query your knowledge base). You can chain these together to create complex automation flows.

Question 6

Can workflows connect to my existing APIs?

Accepted Answer

Yes, the API Call node lets you connect to any REST API endpoint. You can configure HTTP methods (GET, POST, PUT, DELETE), headers, request bodies, and authentication. The workflow can use data from previous steps or user input in API requests, and the response can be used in subsequent workflow steps.

Question 7

How do conditional branches work?

Accepted Answer

You can create conditional branches using edge conditions. For example, if an API call succeeds, route to one node; if it fails, route to another. Conditions can check variable values, node status, or user responses. This lets you build workflows that handle different scenarios automatically.

Question 8

Can workflows collect information from users?

Accepted Answer

Yes, workflows can collect information through Form nodes (structured data collection) or Ask Question nodes (conversational prompts). Collected data is stored as variables that can be used throughout the workflow—for example, to populate API requests or send to webhooks.

Question 9

Do workflows work with calendar booking?

Accepted Answer

Yes, workflows include a Calendar Booking node that integrates with Cal.com. You can embed a calendar interface in the chat, show available time slots, and let users book appointments directly. The booking data is captured as workflow variables for use in subsequent steps.

Question 10

Can I have multiple workflows per widget?

Accepted Answer

Yes, you can create multiple workflows for a single widget. Each workflow can have different triggers, priorities, and categories. The system will automatically select the most appropriate workflow based on user intent and your configured priority settings.

Question 11

How does workflow state work?

Accepted Answer

Workflows maintain state across multiple conversation turns. If a workflow needs user input (like filling a form), it pauses and waits for the user's response. The state persists between messages, so users can complete multi-step workflows naturally through conversation.

Question 12

What happens if a workflow step fails?

Accepted Answer

You can configure error handling in your workflows. If a node fails (like an API call), you can route to an error handling node that sends a message to the user or tries an alternative action. Failed steps are logged so you can debug and improve your workflows.

Question 13

Can workflows send data to external systems?

Accepted Answer

Yes, workflows can send data to external systems through Webhook nodes. You can configure webhook endpoints to receive workflow data, including user information, collected variables, and workflow execution results. This is useful for integrating with CRMs, databases, or other business tools.

Question 14

How do I design effective workflows?

Accepted Answer

Start simple: identify a common customer request that requires multiple steps. Map out the flow on paper, then build it node by node. Test thoroughly, handle error cases, and keep workflows focused on one task. Use clear variable names and add helpful messages at each step to guide users.

Question 15

What's the difference between workflows and the chatbot?

Accepted Answer

The chatbot handles general questions using your knowledge base. Workflows handle specific actions that require multiple steps, external API calls, or structured data collection. They work together—the chatbot can answer questions, while workflows execute tasks like booking appointments or processing orders.

Question 16

How many workflows can I create?

Accepted Answer

You can create multiple workflows per widget. There's no hard limit, but we recommend keeping workflows focused and well-organized. Use categories and priorities to manage multiple workflows effectively.

Automate support
with drag & drop logic

Ready to Automate Your Support?

Frequently Asked Questions

GETTING STARTED

WORKFLOW CAPABILITIES

ADVANCED FEATURES

BEST PRACTICES

Automate support with drag & drop logic