Workflow Studio
Build, test, and publish your first Edgaze workflow without learning every block at once.
Creators building and publishing workflows.
Publish a workflow whose input, transformation, and buyer result are obvious before anyone runs it.
Workflow Studio is the visual editor for products that buyers can run. A workflow can be one model block or a connected process with inputs, tools, logic, and a final output. This page gets one working end to end; the Block reference is authoritative for individual block settings.
The shortest useful workflow#
Start with three blocks:
- Ask for Input asks the buyer for a topic or source text.
- Generate Text turns that input into the requested result.
- Result publishes the value buyers should receive.
Connect them from left to right. A connection carries the upstream block's output into the downstream block. Keep the first version small enough that every connection has an obvious purpose.
Build it#
Open Workflow Studio, create a workflow, and add the three blocks.
You can start without an account. A guest workflow is saved only in the current browser and is limited to one local draft. Sign in to save it to your account, run it, or publish it. After sign-in, Studio transfers the local draft to your account and returns to the action you selected.
In Ask for Input, add one question or a group of related questions. Use clear labels and mark only essential answers as required.
In Generate Text, write instructions that reference the connected answers. Choose a model based on quality, latency, and provider setup. The current default comes from the catalog: gpt-6-sol. The model picker is the source of truth for currently callable alternatives.
In Result, choose the value from Generate Text and give it a plain name such as article or summary. Only Result blocks become the buyer's final result.
Use the Studio without losing context#
The left library is for finding blocks. Use the category menu above the block grid to narrow the list, and search to filter blocks by name. Templates are not in the library: choose Browse templates when you start a workflow, or open Templates.
Select a block to configure it in the Inspector. The Inspector is tied to that exact block, so switching between two blocks of the same type does not carry unfinished field values across. Saving, Saved, and Error show whether the current draft reached storage.
Connections describe data flow, not execution decoration. Start at an output port and finish at a compatible input port. If a connection is rejected, use the message beside the attempted connection to fix the type, occupied input, direction, or cycle.
On a narrow screen, the Inspector becomes a bottom sheet so the graph remains visible. Hidden Studio layers are removed from keyboard and screen-reader navigation while a modal editor is open.
Repeat a transformation without cluttering the main graph#
Use Repeat when the same steps should run an exact number of times. Each repetition receives the incoming value and the original submitted inputs.
Select the Repeat block and choose Edit repeated steps (or Add repeated steps on a new block) to work with the same library, canvas, connections, and Inspector inside Repeat. Saving returns you to the main graph.
See Repeat for result selection, limits, cost, and failure behavior.
Test the buyer path#
Select Run, enter realistic input, and run the workflow. Check all of these before publishing:
- The form asks only for information the workflow actually uses.
- Every block completes in the expected order.
- The Result block contains the complete buyer result.
- Errors explain what the creator or buyer needs to change.
- No provider key, token, or internal configuration appears in output or logs.
Builder test runs run the model each step is set to, on Edgaze's keys, and draw on your weekly Workflow Studio usage allowance (see Pricing Limits). The ring next to Run shows how much of this week is left; it turns amber from 80% used, and the Run panel adds a short note. Each run gets an execution budget from its estimate before it starts. A run that needs more stops with "Stopped: execution budget reached" and keeps what it finished; run it again for a fresh budget.
When this week's allowance is used up, Studio asks before anything starts: turn on Use wallet funds to keep testing from your wallet (compute price, no margin, confirmed once a week), top up, or wait for the Monday reset. With Edgaze Plus and keys saved in API Vault, turn on Use my API keys in the Run panel to run the steps whose provider has your key on that key; those steps use only their compute from the allowance. The row shows which steps move and which stay on Edgaze. Steps have no per-step key setting.
For Repeat workflows, test with a small count first. Confirm that each repetition produces the result you expect, then test the largest count you promise buyers.
Choose provider credentials#
Publishing offers three listing-level modes:
- Edgaze hosted: Edgaze supplies provider credentials and applicable hosted compute is included in the displayed run price. Buyers with Edgaze Plus can opt in to their own keys for the steps whose provider they have a key for; you earn the same margin either way, and the publish preview shows both prices.
- Creator-connected: the creator's encrypted Vault keys run the listing. The creator needs active Plus and every required provider key. Provider usage bills the creator directly.
- Buyer brings keys: each runner needs active Plus and the required Vault keys. Provider usage bills the buyer directly.
The publish screen derives required providers from the graph. A non-hosted listing never silently falls back to Edgaze credentials. If a required creator key is removed, the listing becomes unavailable until it is repaired.
Read API Vault and BYOK billing before choosing a non-hosted mode.
Price and publish#
Free workflows have no creator margin. For a paid workflow, set a per-run creator margin between $0.05 and $50.00. The buyer sees one displayed price containing the creator margin plus applicable hosted compute. Creators receive 80% of their margin, not 80% of the full displayed price.
Before publishing, confirm:
- The title and description say what the buyer gets.
- Required setup and providers are disclosed.
- The thumbnail and demos represent normal results.
- The input envelope covers the promised use case.
- The failure and cancellation expectations are accurate.
Publishing creates an immutable workflow version. Later edits create a new version when the executable graph or pinned execution contract changes.
Remix rules#
A creator may allow an original workflow to be remixed as one sealed Remixed Workflow block. A valid remix has one sealed parent and a meaningful change around it. A remix cannot itself be remixed, so composition depth is one. The publish screen rejects a remix of a remix before it becomes a listing.
Read Remix and composed workflows and the Remixed Workflow block for exact inputs and failure behavior.
Where to go next#
Was this useful?
Your response helps us improve the documentation.
Related builder documentation
How Workflow Studio, Composer, Templates, and API Vault fit together in Edgaze.
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.