Workflows Overview

Workflows are Convotic's visual automation engine. Each Workflow is a directed graph of nodes that executes when a trigger fires. Workflows let you automate conversations, route messages, update CRM records, and orchestrate actions across all your connected Blocks -- without writing code.

Key capabilities

Capability	Description
Visual flow builder	Drag-and-drop canvas for building automation logic.
20+ node types	Messaging, logic, data manipulation, and advanced nodes.
Durable execution	Workflows are executed with at-least-once delivery. If a node fails, it retries automatically. Long-running flows (e.g., wait for reply) survive restarts.
Cross-platform	A single Workflow can span multiple Blocks (e.g., receive an Instagram DM, look up a Shopify order, reply via LINE).

How Workflows work

Every Workflow follows the same pattern:

Trigger → Node → Node → ... → End

1. Trigger -- an event that starts the Workflow (e.g., a new message, a keyword match, a follow event). See Triggers.
2. Nodes -- individual steps that execute in sequence or branch based on conditions. See Nodes.
3. Actions -- the side effects produced by nodes (send a message, tag a contact, call an API).

Example flow

[Keyword: "order"] → [Ask for order ID] → [Wait for reply]
    → [Shopify lookup] → [Condition: order found?]
        → Yes: [Send order status]
        → No: [Send "order not found" message]

Platform support

Workflows can be triggered by events from any connected messaging Block:

Platform	Supported triggers
Instagram	new_message, keyword, story_reply, comment_keyword, new_conversation
LINE	new_message, keyword, follow, unfollow, postback, new_conversation
Messenger	new_message, keyword, comment_keyword, new_conversation, postback
WhatsApp	new_message, keyword, new_conversation
Telegram	new_message, keyword, postback, new_conversation

Workflow lifecycle

Status	Description
Draft	The Workflow is being edited and will not execute.
Published	The Workflow is live and will execute when its trigger fires.
Paused	The Workflow is temporarily disabled. Existing in-progress executions will complete.
Archived	The Workflow is no longer in use and is hidden from the main list.

Execution model

• Each Workflow execution is independent and isolated.
• Nodes execute sequentially unless a Condition or Split node branches the flow.
• The Wait for Reply node pauses execution until the user responds, with a configurable timeout.
• All executions are logged and visible in the Workflow Logs panel for debugging.

tip

Use the Test button in the Workflow builder to simulate a trigger and step through your flow before publishing.