Using the AI Editor Assistant
Let AI help you build workflows. Learn how to use the AI assistant in the editor for suggestions, debugging, and automated workflow creation.
Using the AI Editor Assistant
The AI Editor Assistant helps you build workflows faster by understanding your goals and making changes for you. It's like pair programming with an AI that knows FlowDot inside and out.
What the Assistant Can Do
- Suggest improvements to your workflow
- Add and configure nodes based on descriptions
- Debug issues and explain errors
- Generate complex workflows from prompts
- Explain how existing workflows work
Step 1: Accessing the Assistant
- Open any workflow in the Editor
- Click the AI Assistant icon (top right, looks like a chat bubble)
- The assistant panel opens on the right
Choosing Your Model
The assistant uses your tier preferences:
| Tier | Best For |
|---|---|
| Simple | Quick questions, basic changes |
| Capable | Most assistance tasks |
| Complex | Advanced workflows, complex changes |
Select your tier before asking for help. Complex models (like Claude Opus) are best for workflow building.
Step 2: Asking for Advice (No Changes)
Start by getting suggestions without making changes:
You: Without invoking changes, tell me how you can improve this workflow.
The assistant will:
- Analyze your current workflow
- Review all node types available
- Suggest improvements
- Explain reasoning
Example Response:
Looking at your Goat Simulator, I can suggest:
- Enhanced Personality: Add memory to make the goat remember past conversations
- Decision Branching: Let users choose topics with a router node
- Goat Sounds: Add TTS for actual "Baa!" audio output
- Personality Modes: Switch between happy, grumpy, and sleepy goat
Step 3: Scoped Requests
Be specific to get better results:
Too Broad (Might Overwhelm)
You: Make this the best goat simulator ever.
Better (Scoped Request)
You: Update only the system prompt to make the goat more entertaining and punny.
Even Better (Very Specific)
You: Change the system prompt to: "You are Gerald, a chaotic but lovable goat who loves wordplay and always mentions hay."
Step 4: Applying Changes
When you're ready to let the assistant make changes:
The Apply Actions Button
After the assistant suggests changes, you'll see:
- Description of proposed changes
- An Apply Actions button
- Review what it wants to do
- Click Apply Actions
- Changes are made to your workflow
Undo/Redo History
Every assistant action is undoable:
- Look for the Undo button in the assistant panel
- Click to revert the last change
- Click Redo to reapply
Important: The undo history is session-based. When you close the assistant panel, history is cleared. Save your workflow if you want to keep changes!
Step 5: Common Assistant Tasks
Adding Nodes
You: Add a text-to-speech node that reads the goat's response aloud.
The assistant:
- Finds the TTS node
- Adds it to the canvas
- Connects it appropriately
- Configures default settings
Debugging Issues
You: This workflow gives an error when I run it. What's wrong?
The assistant:
- Analyzes the workflow structure
- Identifies missing connections
- Spots configuration errors
- Suggests fixes
Explaining Workflows
You: Explain how this workflow works step by step.
The assistant:
- Traces the data flow
- Explains each node's purpose
- Describes the overall logic
Generating Workflows
You: Create a workflow that takes a URL, scrapes the content, summarizes it, and saves to a text file.
The assistant:
- Plans the workflow structure
- Adds all necessary nodes
- Configures connections
- Sets up parameters
Step 6: Best Practices
Start with Conversation
Bad: "Build me an email workflow."
Good: "I want to automatically summarize my emails. What approach would you suggest?"
The conversation helps the assistant understand your goals.
Be the Creative Director
Your human creativity + AI's technical knowledge:
You: I want something that feels like chatting with a wise old wizard.
Assistant: [Suggests approaches]
You: I like option 2, but make it more mysterious.
Assistant: [Refines]
You: Perfect, apply that change.
Review Before Applying
Always read what the assistant proposes:
- Does it match your intent?
- Are there unintended side effects?
- Is the approach reasonable?
Use Different Models for Different Tasks
| Task | Recommended Tier |
|---|---|
| Quick questions | Simple |
| Debugging | Capable |
| Building new workflows | Complex |
| System prompt writing | Complex |
| Explaining code | Simple/Capable |
Step 7: Advanced Techniques
Mixing Models
Use expensive models to design, cheap models to run:
1. Use Complex (Opus) to write the perfect system prompt
2. Save the workflow
3. The workflow itself uses FlowDot (free) to execute
Iterative Building
You: Add a weather lookup.
[Apply]
You: Now connect it to an LLM that interprets the weather.
[Apply]
You: Add a decision node that changes output based on weather type.
[Apply]
Build complex workflows step by step.
Getting Unstuck
When the assistant misunderstands:
You: That's not quite what I meant. I want [clearer description].
Or start fresh:
You: Let's start over. Here's exactly what I need: [detailed requirements]
Troubleshooting
"The assistant made weird changes"
- Click Undo immediately
- Be more specific in your next request
- Try a more capable model
"The assistant doesn't understand my workflow"
- Use descriptive node names
- Add descriptions to complex nodes
- Simplify or clean up messy workflows
"Apply Actions button doesn't appear"
- The model may not support tool use
- Try a more capable model
- Ask more explicitly: "Please add a node for..."
Summary
The AI Editor Assistant accelerates workflow building:
- Ask for advice before making changes
- Scope your requests for better results
- Review changes before applying
- Use undo liberally
- Mix models - design with Complex, run with Simple
You're still the creative director. The assistant is your capable co-pilot.
Next, learn about the Agent's memory system!