Manage workflows
Everything you do with workflows in the nullplatform UI lives under Platform Settings → Workflows: the list of your workflows, the editor, every run, and the variables and secrets they read.
Who can manage workflows
You need the Ops or Admin role. With it on the organization, you see and edit every workflow. With it on an account, namespace, or application, you see and edit the workflows owned there, so a team can run its own automations without access to the rest of the organization.
Without write access to a workflow you can still open it, but the editor is read-only. See Workflow permissions for the full rules, including who can change variables and secrets.
Find your workflows
The Workflows menu has three pages: Workflows (the list), Executions, and Variables and secrets.
Each row shows where the workflow lives (its owner and folder), which aliases publish it and on what version, how its last run ended, and when its next cron tick fires. Search matches the name, the ID, or the folder, and the Published filter keeps only the workflows that are (or aren't) published. Sort by Folder to keep each suite together.
Click a row to open the workflow in the editor. Its actions menu has the rest: View executions, Rename, Move to folder, and Delete. Deleting a published workflow unpublishes its aliases first, so nothing triggers it again, and then deletes it with its revisions.
Create a workflow
The fastest way to create a workflow is to describe it to your coding assistant, as in Your first workflow: the skill builds, validates, and publishes it for you. To start by hand, click New workflow in the list.
The Create workflow dialog has two ways in:
- Start from scratch creates an empty workflow with a manual trigger and opens it in the editor.
- Import YAML takes a
.yaml,.yml, or.jsondefinition, shows a preview of its name, folder, steps, and triggers, and creates it as is. Use it to bring a suite from the open source catalog or from another organization.
The Folder is a path like /governance/checklists; leave it empty for the root. The Owner decides who can see and edit the workflow: leave it empty for the whole organization, or pick an account, namespace, or application. If your role is only on a namespace, pick that namespace, since creating at the organization level would be denied. For the same reason, you can't create or move a workflow into a folder that holds variables or secrets: see Folders that hold variables or secrets.
Work in the editor
The editor opens full screen over the list. Its header switches between three views of the same workflow: Canvas to build visually, Code to edit the YAML, and Observe to follow a run on the graph. Next to them are Revisions, Save (Ctrl+S), Run, and the version chip.
The panel on the right follows what you select. With no step selected, it shows the workflow itself: its Overview, the Input/Output contract the Run dialog asks for, its Triggers with their live status, and the Variables it can read. Select a step and the panel shows its Configuration, its Input/Output mapping, and its latest Runs. Cron triggers get a schedule builder that previews the next runs, and any step can turn on per-item iteration or Continue on fail without leaving the canvas.
A few things make editing safer:
- The chip shows what's live. It reads, for example,
live v3orDraft v4, and opens the versions panel where you publish. See Runs and versions. - Problems show up before you run. Saving or validating lists the engine's warnings, such as a secret that isn't defined or a step key the engine ignores, with a link to the step.
- Unsaved work isn't lost. If the tab closes, the editor recovers your changes from the browser the next time you open the workflow. If someone else saved in the meantime, the editor saves nothing and lets you copy your YAML or reload their version.
- Shared workflows warn you. When other workflows call this one as a sub-workflow without pinning a version, saving tells you which ones, because they pick up your changes right away.
💡 Tip: Press
⌘Kto add a node, or right-click the canvas, a node, or a connection for its actions. On a published webhook trigger, Copy webhook URL gives you the URL to hand to the external system.
Review executions
Executions lists every run of the workflows you can see, newest first.
Filter by status, workflow, alias, or start date. Once you pick a workflow, you can also filter by the inputs it declares, with an exact value: for example, every run of a scanner that got a given nrn. Click a run to open it in the editor's Observe view, where you can follow it step by step, cancel it, or run it again. See Runs and versions.
Next steps
- Runs and versions: publish from the version chip, compare revisions, and act on a run
- Secrets and variables: the values your workflows read, and the page that manages them
- Workflow permissions: who can see, edit, and run workflows, on the organization or one namespace
- Tutorials: complete suites to import and tune