Draft and deploy
Overview
Section titled “Overview”Each script, flow, or app can be saved in three ways: locally in browser storage, as a backend draft, or as deployed. Once deployed, these items become visible and actionable by users with appropriate permissions.
Local edits
Section titled “Local edits”Changes to scripts, flows, or apps are initially saved locally in your browser until validated as either a draft or deployed version. Local edits can only be run and tested from the editor using the Test button.
Local edits can be saved as a draft for staging purposes. A draft remains visible and editable by workspace members, with only one draft per runnable. The draft inherits permissions from its parent item or path location. Like local edits, drafts can only be tested through the editor’s Test button.
Deployed version
Section titled “Deployed version”The deployed version represents the authoritative state of a runnable. Once deployed, it gains visibility to workspace members with proper permissions and obtains its own auto-generated UI, webhooks, and can be called from flows and apps (for scripts and flows). Importantly, local edits and drafts can be developed in parallel without affecting the deployed version’s behavior.
Deployment history
Section titled “Deployment history”Scripts and flows support deployment messages on each release. View versions and their messages in the History menu. Fork previous versions using the Deploy dropdown’s Fork button, and retrieve past versions through History with “Restore as fork” or “Redeploy with that version” options.
Diff viewer
Section titled “Diff viewer”Compare changes between current work and the latest deployed version or draft for any script, flow, or app. Changes can be reversed to previous versions using the diff toggle to examine code changes inline.
Special case: deployed script versions
Section titled “Special case: deployed script versions”Apps and flows maintain one deployed version per path, with new deployments overwriting previous ones. Scripts differ — each deployment creates an immutable hash never overwritten. The script path redirects to the latest hash, but all historical hashes persist permanently, guaranteeing consistent behavior when referencing by hash.
Special case: public apps
Section titled “Special case: public apps”Orvanta apps can be published publicly, allowing standalone access via secret URL to anyone with the link.