Reference

Quick-access reference tables for keyboard shortcuts, condition templates, API endpoints, troubleshooting, and terminology.

Keyboard Shortcuts

Node Status Colors

Edge Colors

Loop Edge Labels

During execution, the label updates to show progress:
– loop:3 ↺ 1/3 — first iteration
– loop:3 ↺ 2/3 — second iteration
– loop:3 ✓ 3/3 — all iterations complete

The counter resets to the clean loop:N label when the workflow is reset.

Condition Templates

NORA ships with a Condition Library of ready-made templates you can drop onto the canvas. See Node Types — Condition Node for full details on each.

Basic Logic

Output Comparisons

Time / Date

Advanced

AI Nodes

Condition Logic Types

Layout Algorithms

Available via the Layout dropdown in Edit Mode:

API Endpoints

All endpoints run on http://localhost:4000 (default port).

Workflow Config

Command Execution

AI Services

Custom Script Agent Sessions

The Custom Script Agent maintains persistent sessions for multi-turn interactions:

Background Execution

Scheduling

Execution History

Gmail

Process Management

Tool Library

Media & Files

System

Troubleshooting

Import Errors

Save Errors

Workflow Execution Issues

AI Node Issues

Tool Library Issues

Connection Issues

System & Startup Issues

Tip (Windows Startup): The startup shortcut is located at:
%APPDATA%\Microsoft\Windows\Start Menu\Programs\Startup\NORA.lnk
You can manually verify it exists and points to the correct NORA executable.

Scheduler Features

File Locations

~ = your home directory (e.g., C:\Users\{YourName} on Windows)

Glossary

Developer Tools

NORA includes tools to help you generate workflow configs without writing code by hand.

Workflow Config Converter (Convert UI)

A browser-based tool with three workflow generation utilities.

Location: Documents\NORA\tools\text_workflow\convert-ui.html

Tab 1: Checklist Converter (No AI Required)

Converts a structured checklist into workflow config code using a built-in parser.

Checklist format:

1 Download Sales Report
  a Connect to FTP server
  b Download latest CSV
  c Save to E:\Data\sales
2 Process Data
  a python process_data.py
  b Validate output
3 Send Notification
  a Email team with results

Rules:
– Main steps: Number + space + title (e.g., 1 Step Name)
– Sub-items: Two spaces + letter + space + description (e.g., a Details here)
– Commands are auto-detected (python, node, npm, etc.)
– Paths use double backslashes for Windows (e.g., E:\\Data)

Tab 2: Directory Generator (No AI Required)

Scans a folder and auto-creates workflow nodes for all scripts found.

1. Select a project folder
2. Configure depth, grid layout, spacing
3. Click “Generate Config”

Output includes nodes for .py, .js, .bat, .ps1 files with proper commands and working directories.

Tab 3: AI Chat (Optional, requires proxy)

Conversational AI workflow generation in the browser. For this feature only, you need the AI Proxy Server running.

AI Proxy Server

A local proxy that enables browser-based AI features (Convert UI’s AI Chat tab) to call AI providers without CORS issues.

Location: Documents\NORA\tools\text_workflow\ai-proxy-server.js

Note: The Checklist Converter and Directory Generator do NOT require this. Only needed for the browser-based AI Chat tab.

Start the server:

cd Documents\NORA\tools\text_workflow
node ai-proxy-server.js

Default port: http://127.0.0.1:8787

AI Chat CLI (Recommended for AI Generation)

A standalone terminal chatbot that generates workflow configs through conversation. This is the most powerful AI workflow generator — it uses a comprehensive schema prompt for accurate results.

Location: Documents\NORA\tools\text_workflow\ai-chat-cli.js

Run:

cd Documents\NORA\tools\text_workflow
node ai-chat-cli.js --provider gemini

Options:
| Flag | Description |
|——|————-|
| -p, --provider | AI provider: claude, openai, or gemini |
| -o, --output-dir | Directory to save generated files |
| --auto-save | Auto-save generated configs without prompting |
| --log-history | Save conversation history to JSON |
| -m, --max-tokens | Default max tokens for responses |

Example session:

You: Create a workflow that monitors E:/logs for new files and sends a Slack notification
AI: [generates complete workflow config code]
Save to file? (y/n): y
Filename: log-monitor-workflow.js

Getting an API key:
– Google Gemini (free tier): https://aistudio.google.com/app/apikey
– OpenAI: https://platform.openai.com/api-keys
– Anthropic: https://console.anthropic.com/

VS Code + GitHub Copilot

If you use VS Code, you can leverage GitHub Copilot (or Claude) to help with NORA workflows:

Use cases:
– Generate configs: Describe your workflow in natural language
– Debug scripts: Paste error output, get fixes
– Explain nodes: Ask “What does this aiAutonomousAgent config do?”
– Refactor: Ask “Split this workflow into smaller, reusable parts”

Tip: Open ai-chat-cli.js in VS Code so Copilot learns the workflow schema from its massive system prompt. Then Copilot will understand NORA’s node structure when you ask it to generate configs.

Example prompt to try:

Create a NORA workflow config that:
1. Runs a Python script at E:/scripts/daily-report.py
2. Checks if the script succeeded or failed
3. On success, reads the output file and sends it via Gmail
4. On failure, sends an error notification

Best Practices for AI-Generated Workflows

1. Be specific — Include file paths, expected outputs, and tool names
2. Start simple — Generate 3-5 nodes first, add complexity incrementally
3. Test individually — Run each node in isolation before running the full workflow
4. Add documentation — Include notepad nodes to explain your workflow
5. Review paths — AI-generated paths may need adjustment for your system
6. Use the schema — When asking AI for help, reference that NORA uses a specific node schema (aiAgent, aiAutonomousAgent, condition, script, etc.)