docs

Workflow Assistant

The Workflow Assistant is an AI-powered chat panel that lives inside your workflow editor. Instead of dragging and configuring nodes manually, you can describe what you want in plain English and the assistant builds it for you.

Open it by clicking the floating button on the right edge of the editor.

What It Can Do

The assistant has direct access to your workflow canvas. It can:

  • Add nodes — create any node type and place it on the canvas
  • Connect nodes — wire outputs to inputs with proper handle mapping
  • Configure nodes — set properties like asset symbols, LLM prompts, conditions, and more
  • Delete and reorganize — remove nodes, rename them, reposition them on the canvas
  • Execute workflows — trigger a run and monitor the results
  • Debug failures — pull execution logs, analyze errors, and suggest fixes

Every action the assistant takes appears as a live update on your canvas — you see nodes being added and connected in real time.

Building with Natural Language

Just describe what you want. The assistant understands trading concepts and workflow logic. Watch it build a sentiment trading bot from a single prompt:

The assistant creates all nodes first, then wires them together, then configures properties — just like you would manually, but in seconds.

Actions

When the assistant modifies your workflow, each change appears as an action pill in the chat showing exactly what happened:

ActionDescription
Add NodeCreates a new node on the canvas
Connect NodesWires an output to an input
Update ConfigChanges a node's properties
Set PropertyUpdates a single field (e.g., symbol, prompt)
Delete NodeRemoves a node and its connections
Rename NodeChanges the display label
ExecuteTriggers a workflow run

Each action shows a status indicator — spinning while executing, checkmark on success.

Debugging

When a workflow fails, the assistant can diagnose the issue:

  1. It retrieves the execution logs and per-node inputs/outputs
  2. Analyzes where the failure occurred
  3. Explains the root cause in plain language
  4. Suggests or applies a fix directly
Workflow Assistant
4 nodes · 3 connections
Why did the last run fail?
The execution failed at the Exchange Order node. The error was "Insufficient funds" — your Alpaca paper trading account doesn't have enough buying power for the order size. Try reducing the amount from 1.0 BTC to 0.01 BTC, or switch to a funded account.
Updated Exchange Order: amount = 0.01
Ask Nick any questions or give it any task

Auto-Iterate

Enable Auto-Iterate to let the assistant automatically fix and retry failed workflows:

  1. You click Run (or the assistant triggers execution)
  2. If the workflow fails, the assistant analyzes the error
  3. It modifies the workflow to fix the issue
  4. Reruns automatically
  5. Repeats up to 5 times or until the workflow succeeds

Enable auto-iterate from the toggle in the chat input area. Your preference is saved across sessions.

Voice Input

Click the microphone icon to speak instead of type. The assistant uses your browser's speech recognition to convert voice to text.

  • Automatic silence detection — stops recording after 2 seconds of quiet
  • Real-time visualization — audio level indicator shows recording is active
  • Works in Chrome, Edge, and Safari

Attachments

You can attach files to your messages:

  • Images — share screenshots of charts, error messages, or UI issues (up to 20MB)
  • Documents — attach PDFs, text files, or spreadsheets for the assistant to reference (up to 20MB)

Useful for sharing chart screenshots for analysis, or pasting error logs from external systems.

Models

The assistant supports multiple LLM providers through a unified interface. Switch models from the dropdown in the chat input area.

ProviderModels
AnthropicClaude Sonnet 4.6 (default), Claude Opus 4.6, Claude Haiku 4.5
OpenAIGPT-5.2, GPT-5, GPT-4o, GPT-4o Mini
GoogleGemini 2.5 Flash, Gemini 3 Pro
xAIGrok 4, Grok 3
DeepSeekDeepSeek Chat, DeepSeek Reasoner
PerplexitySonar Pro, Sonar Reasoning (with web search)

Some models support extended thinking — you'll see a collapsible "Thought process" block showing the assistant's reasoning before its response.

How It Understands Your Workflow

The assistant receives full context about your current workflow:

  • All nodes — types, positions, labels, configurations
  • All connections — which outputs connect to which inputs
  • Node schemas — what each node type accepts and produces
  • Execution history — recent run results, errors, and per-node outputs
  • Variables — workflow and global variables you've defined

This context means the assistant can reference specific nodes by name, understand data flow between them, and make targeted fixes.

Next Steps

  • Workflows — learn the visual editor fundamentals
  • Executions — understand how workflows run and how to debug them
  • Nodes — explore all available node types the assistant can use
  • Credentials — set up the API keys your workflows need