Skip to main content

Digitorn Studio

Studio is the visual editor for Digitorn apps: on the web at https://digitorn.ai/studio, or inside the desktop app through its Build your own button. The canvas compiles to the same app.yaml (plus package files) the daemon runs, whichever way you opened it.

A conversational “build with AI” track is not shipping yet. Use the canvas and YAML today.

Who can edit​

  • Anyone can open Studio and browse examples without signing in.
  • Editing an app requires signing in.
  • On Digitorn cloud, editing and deploying requires a paid plan (or an admin account). A free account sees an upgrade prompt instead.
  • Running your own daemon (self-hosted), editing is open to any signed-in user by default. An admin can turn on the same paid-plan requirement cloud uses, by setting builder.require_paid: true in the daemon's own config file; this is an operator setting, not something you touch from Studio itself.

Install for Test vs Publish​

ActionVisibilityTriggersWho sees it
Install for TestdebugNot armedOwner only
PublishproductionArmed (webhook/cron/…)Catalogue on this daemon

Always Install for Test first. Live Test / run-step / studio test-trigger work against the debug install without exposing public hooks.

Studio Listen for test webhook URLs are ephemeral (in-memory, one-shot). They are not production channel webhooks.

Background apps​

  1. Start from Scheduled job or Background webhook (or blank flow).
  2. Keep a real channel trigger on the canvas (cron / webhook / …).
  3. Install for Test, then use Fire test / Listen / Live Test.
  4. Publish only when you intend to arm triggers.

Flow debug toolbar​

On flow.* nodes (after Install for Test):

  • Run step: execute one node (pins seed prior outputs).
  • Run until here / Run from here: partial walks (studio-only).
  • Pin / Inspect: fixture data under _studio/pins/ (not part of production YAML).

Approval nodes cannot be run from the toolbar (they would block the HTTP call).