#Build & Run

Use the visual editor to build a workflow from nodes. Start with a blank canvas, add a trigger or action, connect nodes together, then save and execute the workflow.

#Add Nodes

Use the node palette at the bottom of the canvas to add a node. The editor prompts you to choose a node when the workflow is empty.

Common node categories include:

• triggers
• actions
• data transforms
• database steps
• file operations
• notifications
• utilities

Choose the node type that matches the next step in your process.

#Connect Nodes

After adding more than one node, connect the output of one node to the input of another. Connections define the path data follows through the workflow.

Keep the first version simple. A small workflow with a clear trigger, one action, and one output is easier to test than a large workflow with many branches.

#Configure a Node

Select a node to edit its configuration. Configuration fields depend on the node type. A trigger might ask when the workflow should start. An HTTP node might ask for a URL and method. A specialist node might ask which specialist should respond and what prompt it should receive.

#Choose an Execution Mode

The toolbar includes an execution mode selector.

• Dataflow passes data from node to node and is the best starting point for most workflows.
• State Machine is useful when workflow state matters across steps.
• Hybrid combines both styles.

#Save and Run

Use Save to persist your workflow. Use Execute to run it. Watch the canvas for node status changes and inspect the run output when available.

#Import and Export

Use the toolbar import and export actions to move workflow definitions between files or environments. Import is useful when you already have a workflow JSON file. Export is useful for sharing or backing up a workflow.

#Attach to Channels and Specialists

Workflows become more useful when connected to work surfaces:

• Attach a workflow to a channel when chat activity should trigger it.
• Attach a workflow to a specialist when the specialist should use it as part of its role.
• Link workflows to projects when the automation belongs to a specific initiative.

#Tips

• Start with one trigger and one action.
• Save before experimenting with major edits.
• Use clear workflow and node names.
• Test with small inputs before using production data.
• Keep specialist prompts explicit about the expected output.

#Next Steps

• Visual Workflow Editor. Return to the editor overview.
• Run History. Inspect workflow execution records.