Build the process once. Let your agent run it.
Some briefs need several connected generations. Studio lets you save that process on a visual canvas, then let an agent start it with new inputs through the API. People and agents work with the same saved workflow.
A repeatable prompt-to-image-to-video process, with each run tracked in one place.
Saved workflows are useful for teams that want consistent production steps across many briefs. A creator can adjust the visual workflow while a developer or agent calls it through the API. This makes the process inspectable: the team can see how a result was produced, which node failed, and what each run consumed, instead of rebuilding a chain of requests from scratch.
- 01
Save the production workflow
Connect supported prompt, reference, generation, and output nodes in Studio. Save the workflow in the organization that owns the API key so your agent can discover it.
- 02
Inspect the input nodes
The agent reads the saved workflow through the Studio API and identifies which node IDs accept overrides. New briefs are submitted as inputs keyed by those IDs.
- 03
Start a run with a retry key
POST to /api/v1/studio/workflows/{id}/run with an Idempotency-Key. Reuse the same key and input payload when retrying the same submission. A new key intentionally starts a new billable run.
- 04
Read results and usage
Poll /api/v1/studio/runs/{runId} for persisted status, node results, and net credits used. Cancelling a run stops future steps after already submitted jobs settle; completed work remains charged.
Find our saved product-film workflow in Vydra Studio. Inspect its input nodes, use the approved product brief, and start one run with a stable idempotency key. Return the completed node outputs and credits used.
Adapt this instruction to your agent, account, and approval preferences.
Go from idea to implementation.
Can I run a workflow from both the UI and an agent?
Yes. Studio stores organization-owned workflows that can be run through the interface or the API, subject to the API key’s permissions.
How do retries avoid duplicate Studio runs?
Use the same Idempotency-Key and inputs for the same submission. Creating a new key starts a new run. This applies to Studio runs and should not be assumed for ordinary job POST requests.