Every Node Type in MegaNova's Workflow Editor Explained

The workflow canvas looks simple at first glance.

Drag. Connect. Run.

But the power of MegaNova Studio's workflow editor comes from understanding what each node actually does — and more importantly, knowing which one to reach for when.

The node panel on the left is organized into four categories: Nova Agent, Channels, Flow, and Output. Each category handles a different part of the workflow. Together, they cover everything from triggering a process to delivering its output across every major platform.

Here is every node, explained plainly.

Flow

Logic and routing. These nodes control when the workflow runs and how data moves through it.

Trigger

The entry point for any workflow. Defines what activates the process. Configure it with one of five event types:

• New Message — fires whenever a message arrives
• Keyword Match — fires when the message contains a specific word or phrase
• Scheduled — fires on a time-based schedule
• Webhook — fires from an external HTTP call
• Escalation Request — fires when a conversation is escalated

One workflow, one Trigger. Everything downstream depends on what enters here.

Condition

Evaluates the output of a previous step and routes the workflow in two directions: True or False.

Configure a condition type:

• Keyword Match — does the input contain a specific word?
• Sentiment — is the tone positive or negative?
• Intent Detection — what is the user trying to do?
• Custom Expression — define your own comparison with equals, contains, greater than, or less than

Use this when the workflow needs to behave differently based on what was said or detected.

Router

Multi-path branching for more than two outcomes. Where the Condition node handles binary decisions, the Router handles three, four, or more.

Configure each route with a name. Set the routing mode:

• All Routes — sends data to every matching route simultaneously
• First Match — sends data only to the first route that matches
• Random — sends data to a randomly selected route

Output handles generate dynamically based on the number of routes you configure.

Nova Agent

The AI brain components. These nodes supply intelligence, context, knowledge, and behavior to the workflow.

Character

Links a workflow to a specific character defined in your space. The character's personality, behavior rules, and system prompt become the foundation for the AI response. You can enable Custom Instruction to add workflow-specific context without modifying the original character.

Inputs: Context, Skills, Memory. Outputs: Persona, System.

Agent

A self-contained intelligence node. Unlike the Character node — which is a building block that connects to other nodes — the Agent node is an entire pipeline compressed into a single block: character, lorebook, memory, skills, and tools all configured in one place.

Use it when you want autonomous behavior without building out a full multi-node graph. Supports automatic model routing and tool use.

Memory

Manages conversation history and context. Choose the memory type:

• Short-term — within-session recall
• Long-term — persistent storage across sessions
• Episodic — structured event-based recall

Set the maximum number of entries to control how much history flows forward. Connect its output to the Character or Agent node's Memory input.

Skills

A behavior modifier, not a content generator. The Skills node injects a professional capability into the system prompt — it changes how the character responds rather than what it responds with. Define the skill name, techniques, and guardrails (prohibited topics, required behaviors). Token cost is estimated automatically.

Connect its output to the Character node's Skills input.

Storage

Free-form text storage. Write directly into the node or upload files and let MegaNova extract the text automatically. Tracks token count so you know how much context budget you are consuming.

Use it for injecting fixed context — instructions, templates, reference material — into any part of the workflow.

Lorebook

Links to a lorebook defined in your space and injects its content as context when triggered. Configure the token budget to control how much lorebook content enters the prompt.

Use it when a workflow needs character lore, world-building details, or factual reference material to be conditionally available.

Image

Selects a static image from your space and passes it downstream as an image handle. Use it to provide a reference image to the Image Gen or Video Gen node.

Audio

Selects an audio file from your space and passes it as an audio handle. Useful for providing a voice reference to the Voice node, or ambient audio to the Video Gen node.

Agent (Connector Mode)

The same Agent node can also operate as a connector: when a channel node fires, the Agent processes the incoming message and routes the response back out through the appropriate output. Configure tools, enabled channels, and memory limits in the properties panel.

Output

Delivery nodes. These are where the workflow's result becomes visible or gets handed off.

Chat

Delivers a live streaming response to the user in the chat interface. Configure streaming behavior and typing indicators. No outputs of its own — its job is delivery.

Inputs: Response, Persona.

Widget

Packages the workflow output into an embeddable chat widget. Choose the widget style — bubble, inline, or fullscreen — and receive an embed ID for placement on any external site. Use this when the workflow is the backend for a deployed user-facing product.

Voice (TTS)

Converts any text input into spoken audio. Supports three TTS providers:

• Edge TTS
• OpenAI TTS
• ElevenLabs

Accepts a voice reference audio for cloning. Configure speed, pitch, and voice ID. Output is an audio handle that connects downstream to the Video Gen node or standalone audio delivery.

Image Gen

Generates an image from a text prompt using AI image generation models:

• FLUX.1
• Seedream
• DALL-E 3
• Stable Diffusion

Configure size, accept a style reference, and optionally pass a reference image for guided generation. Tracks execution status in real time — generating, completed, or failed.

Video Gen

Generates a video from a text prompt, audio input, and optional reference image. Supported models:

• LiveAvatar
• Runway Gen-3
• Pika Labs
• Kling AI

Configure resolution (supports 9:16 vertical for social formats), duration, and frame rate. The natural downstream destination for the Image and Audio asset nodes when building character video pipelines.

Channels

Communication destinations. These nodes deliver workflow output to external platforms — or receive input from them.

Each channel node has the same basic structure: configure the target destination, check the connection status, and connect it into the workflow. When the workflow reaches a channel node, it delivers the output to that platform automatically.

Freshdesk

Creates a support ticket in Freshdesk when triggered. Designed for escalation flows — when a Condition or Agent node determines a conversation needs human follow-up, this node routes it into your helpdesk. Configure ticket priority from low to urgent.

Microsoft Teams

Sends a message to a Microsoft Teams channel. Configure the channel name. Outputs message ID and delivery confirmation for downstream handling.

Email

Sends an email notification. Accepts a recipient address as a dynamic input so the destination can change based on earlier workflow logic. Configure the subject line template.

Slack

Posts a message to a Slack channel. Configure the target channel. Outputs message ID and status.

Other Messaging Platforms

A single Channel node type covers every other messaging platform: Telegram, WhatsApp, Discord, Google Chat, Signal, LINE, Feishu, Mattermost, Matrix, Twitch, Zalo, Nostr, Nextcloud Talk, iMessage, and WebChat. Select the platform from a dropdown in the properties panel. All operate identically — configure the channel name, verify connection status, and connect to the workflow.

How to Think About the Four Categories

When you sit down to build a workflow, the question is never "which node do I use." The question is "what does this step need to do."

Flow — something needs to start the process, or make a decision: Trigger, Condition, Router.

Nova Agent — something needs to think, remember, or supply knowledge: Character, Agent, Memory, Skills, Storage, Lorebook, Image, Audio.

Output — something needs to deliver the result to a user: Chat, Widget, Voice, Image Gen, Video Gen.

Channels — something needs to reach an external platform: Freshdesk, Slack, Teams, Email, or any of the other messaging integrations.

Map those four questions to your workflow before you open the canvas.

The node you need will be obvious before you look for it.

Final Thought

In practice, most workflows use five or six nodes.

You do not need all of them for every build. You need the right ones — connected in the right order, configured with the right prompts and logic.

Learn what each category is for. The individual nodes will make sense on their own.

Start simple. Add complexity only when the simpler version cannot do the job.

The canvas rewards clarity far more than it rewards size.

Open the Workflow Editor in MegaNova Studio →

Stay Connected

💻 Website: Meganova Studio

🎮 Discord: Join our Discord

👽 Reddit: r/MegaNovaAI

🐦 Twitter: @meganovaai