Skip to main content

Digitorn Studio

Studio (https://digitorn.ai/studio) is the visual editor for Digitorn apps. The canvas compiles to the same app.yaml (plus package files) the daemon runs.

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

Who can edit​

  • Guests may open Studio and browse examples.
  • Signing in is required to edit.
  • On Digitorn cloud, paid plan (or admin) is required to edit and deploy. Free users see an upgrade prompt.
  • Self-hosted daemons leave builder.require_paid: false by default.
  • When builder.require_paid: true, the daemon also gates mutating /api/builder/* calls. Allowed when the JWT has features.plan_tier (or top-level plan_tier) other than free, or role admin, or perms * / studio:edit / builder:edit. Cloud example config sets this true; self-host keeps false.

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 → 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).