Skip to main content
The Workflows view is the local library and starting point for every definition.

​
Find work

Search uses workflow metadata and visible names. Filters and sorting let you separate active and archived work and prioritize recently opened or executed workflows. Favorites, folder names, and tags are local organization metadata; they do not change an exported workflow definition.

​
Row actions

Each workflow row exposes the actions implemented for that definition:
  • run or open the editor;
  • favorite or unfavorite;
  • move into a folder and edit tags;
  • duplicate into an independent workflow;
  • export a sanitized .sandbox-workflow.json file;
  • archive and later restore; or
  • permanently purge after confirmation.
Duplicate and import create new workflow identities. Historical executions remain attached to the workflow that originally ran.

​
Templates

Open the Templates tab beside My workflows to browse 15 premade workflows. Search by tool or outcome, or filter the gallery by AI, Monitoring, Browser, Communication, Files, and Developer. Select Use template, adjust the copy’s name, and sndbox opens the complete graph in the editor. The gallery includes starters for:
  • AI email triage, daily briefs, command analysis, and JSON summaries;
  • website health, API changes, Slack and Discord incident alerts;
  • browser screenshots and report downloads;
  • approval-gated email and downloads organization; and
  • a localhost status site built from three editable HTML, JavaScript, and CSS Code nodes connected to the Web Builder’s named inputs.
Every template creates an independent, fully editable local copy. Connections, protected values, managed browser profiles, and approved folders are deliberately left for you to choose. Review those requirements and the requested permissions before enabling or running a template. A template imported through a sandbox://templates/import deep link is also created locally and disabled. It contains no credential or protected value.

​
Next run

Scheduled workflows can show a computed next-run time. That time belongs to the runner that owns the schedule and changes when the schedule, timezone policy, enabled state, or runner availability changes.