Builder Overview
How Workflow Studio, Composer, Templates, and API Vault fit together in Edgaze.
Creators building and publishing workflows.
The Edgaze builder helps you turn a promised result into a product people can run and pay for. Begin with what the buyer should receive, identify the information needed to create it, then add only the transformations between those two points.
Choose the shortest path to the outcome#
Workflow Studio is for products with visible steps, branching, external requests, or repeated work. You connect blocks on a canvas, configure them in the Inspector, test the buyer path, and publish an immutable version.
Composer can turn a prompt or outcome into an editable workflow. Prompt Studio creation is retired; existing prompt products remain supported.
Templates are guided starting points. Pick an outcome, answer a few product questions, and land in Workflow Studio with a normal editable graph.
API Vault stores your model provider keys in one secure place so your workflows can run on OpenAI, Anthropic, Google, and similar providers without scattering secrets across nodes.
Composer lives inside Workflow Studio. Describe a result or change in plain language, review the proposed graph, and test it before publishing.
Which one to open first#
If one prompt can do the whole job, describe the outcome to Composer and keep the generated workflow as simple as it needs to be.
If the product needs several connected steps, branching, or post-processing, start in Workflow Studio.
If you know the result you want but not the graph, start with Templates.
Set up API Vault as soon as you want runs to use your own provider accounts reliably.
A reliable creator path#
- Write one sentence describing what the buyer receives.
- Add Output and name that result.
- Add the smallest transformation that can produce it.
- Add only the buyer inputs that transformation needs.
- Test normal, empty, and failure cases.
- Publish with a title, description, and price that describe the result rather than the implementation.
The question to keep in front of you: What does the customer get back, and why is that easier than doing it manually?
Three common shapes#
Single prompt
Customer input -> Prompt -> Result
Usually a small workflow created with Composer.
Guided workflow
Input -> Merge -> Prompt -> Model -> Output
Usually Workflow Studio or a template.
Multi-input creative workflow
Several inputs -> Merge -> Optimise -> Generate -> Output
Common for templates like AI Art Creator.
See a real workflow before you build#
This is the same graph rendering used in Workflow Studio previews and documentation. Read it from the buyer input on the left to the delivered result on the right.
AI Art Creator
If you are new here#
Read this page once, then go where your product shape points you: Workflow Studio for full control, Templates for the fastest start, or Composer to begin from an outcome. Read API Vault before you depend on your own provider keys.
Before you publish#
Strong Edgaze products are easy to understand at a glance.
Your title and description should name the outcome, not the technique. The customer should know what to enter and what they receive. If those answers are obvious, the builder work usually is too.
For pricing and earnings, see the Billing guides.
Next step#
Was this useful?
Your response helps us improve the documentation.
Builder guides to read next
Build, test, and publish your first Edgaze workflow without learning every block at once.
Build, publish, and integrate a workflow that turns a company website into a structured sales-research brief.
Start from an outcome, answer a few setup questions, and open an editable workflow in Workflow Studio.