Nodes
A node is one step of the job: an image or text source, a prompt, an AI model, an edit such as upscaling or background removal, or an export.
AI node editor for creative production. Build a workflow once, run it again.
Mujo's node editor connects prompts, AI models, images, video, text and tools on a single canvas. You build a creative process step by step, change only the inputs that matter, and run the same workflow again for the next product, brief or campaign.
Image, video and text nodes
Multiple AI models in one workflow
Reusable, shareable workflows
Definition
What a node editor is, and why creative teams use one.
A node editor is a visual canvas where each step of a process is a block (a node) and the connections between blocks define the order those steps run in. In creative production it replaces a chain of manual actions — write a prompt, generate, pick a result, edit it, resize it, export it — with one workflow that can be saved, shared and run again with different inputs.
Connections
Connecting nodes defines the order of the process. The output of one node becomes the input of the next, so the whole sequence is visible on the canvas.
Runs
Running the workflow executes every step in order. Change an input or a setting and run it again — the process itself stays the same.
How a node workflow works
Each node does one step. Connected, they run the whole process.
A node handles one part of the job — a source, a prompt, a model, an edit, an export. Connect the nodes once and a manual creative process becomes a workflow you can rerun, branch and scale.
Connect sources, models and tools
Bring images, video, text, documents, URLs and AI models into the same workflow.
Branch into variants
Split one input into several creative directions, different models or different output formats.
Batch and iterate
Send many assets through the same workflow using bulk inputs and iterator nodes.
Save and reuse workflows
Store a finished workflow as a template instead of rebuilding the same steps each time.
Getting started
How to build a workflow in four steps.
No code and no local setup. You add nodes on the canvas, connect them in the order the work happens, and save the result as a workflow anyone in the workspace can run.
1. Add your sources
Upload product photos, reference images, video or a written brief, or start from a prompt node.
2. Choose the models
Add generation, editing or text nodes and pick which AI model each one runs on.
3. Branch and refine
Split the workflow into concepts, formats or model comparisons, then add upscaling, background removal or resizing where needed.
4. Save it as a workflow
Store the finished graph, expose the variables your team should control, and run it again for the next brief.
Templates and presets
Start from a workflow template, not an empty canvas.
Open a ready-made workflow for a complete production task, or add a single Branch node for a job you repeat often.
Browse workflow templates
From workflow to internal tool
Build the workflow once. Expose only the controls that matter.
Publish a workflow with a fixed set of variables — model, camera, lighting, style, aspect ratio, number of images — so the rest of the team can run it without touching the graph behind it.
For buildersDesign the workflow and decide what stays fixed.
For creatorsChange the exposed variables and run it.
One workflow, many creative directions.
Branch a single brief into concepts, layouts, model choices and format variations, while the production logic behind them stays the same.
How Mujo compares
Coming from another tool? Here is what changes.
Most teams arrive at a node editor from one of three places. What they keep is the visual logic of nodes; what they gain is a hosted workspace, several AI models side by side and workflows their colleagues can actually run.
From an open-source node graph
If you already work in ComfyUI or a similar graph, the logic will be familiar: nodes, connections, branches and batch runs. The difference is that Mujo is hosted — no local install, no GPU to manage, no custom nodes or model files to maintain — and workflows live in a shared workspace with roles and usage limits.
From a chat-based image generator
A chat gives you one result per prompt and no record of how you got there. A workflow keeps the steps: the same lighting, model, format and post-processing are applied every run, and only the inputs change.
From manual production
Repetitive steps — resizing for each placement, removing backgrounds, producing format variants — run as nodes, while art direction and selection stay with your team.
Node editor for teams
Workflows the whole team can run, not only the person who built them.
Production stays inside one workspace, with control over who can build workflows, which models they can use and how much they can run.
Shared workflows
Keep production workflows available to everyone in the workspace.
Model access
Decide which AI models and tools each member can use.
Roles and permissions
Separate builders, creators, reviewers and admins.
Usage controls
Set generation limits and manage credit use across the workspace.
Activity and analytics
See which workflows, models and credits are being used.
Use cases
What teams build in the node editor, from quick fixes to production systems.
Campaign production
Concepts, variations and final assets from one brief.
Product photoshoots
Studio and lifestyle product images.
Fashion catalogue and try-on
Model and look variations at scale.
Storyboards and video shots
Frame sequences built from a written idea.
Branded layouts and reports
Presentations and documents in brand templates.
Production utilities
Background removal, resizing and format conversion.
Security and control
Your workflows run inside a controlled workspace.
Built for creative teams and enterprises that need access control, data security and consistent output at scale.
Private team workspaces
Projects, assets and workflows stay inside your workspace.
Role-based access
Assign permissions across the organisation.
Model permissions
Define which AI models and tools can be used.
Usage and activity controls
Track usage, set limits and review activity.
FAQ
Questions about the node editor, answered.
What is a node editor used for in creative production?
It is used to turn a repeated creative process into a reusable workflow. Instead of running each step by hand — prompt, generate, select, edit, resize, export — you connect those steps as nodes once and run the whole sequence again with new inputs.
Do I need to write code or install anything?
No. The node editor runs in the browser inside your Mujo workspace. There is nothing to install, no GPU to configure and no model files to download.
Which AI models can I use in one workflow?
You can use several models in the same workflow and choose which one each node runs on — for example one model for generation, another for editing or upscaling. Workspace admins decide which models are available to which members.
Can I generate a batch of images at once?
Yes. Bulk inputs and iterator nodes send a list of assets or prompts through the same workflow, so a full catalogue or a set of product photos is processed in one run.
Can my team run a workflow without editing it?
Yes. When you publish a workflow you choose which variables stay open — model, style, lighting, aspect ratio, number of images. Everyone else changes only those and runs it; the graph behind them is not touched.
How is this different from a chat-based AI image generator?
A chat returns a single result and keeps no record of the steps behind it. A workflow stores the process, so the same lighting, format and post-processing are applied on every run and results stay consistent across a campaign or a catalogue.
Can I reuse a workflow on a different project?
Yes. Workflows are saved as templates and can be duplicated, shared with the team and reused with a different product, brief or brand.
Who can see my assets and workflows?
Projects, assets and workflows stay in your team workspace. Access is set by role, and admins can review activity and set usage limits across the organisation.
Build your team's production process once in the node editor and run it whenever a new brief comes in.