Run it in the browser,
or on your own machines.
Build and run in the browser with nothing to install. Export compatible workflows to supported Linux or macOS runners: on a schedule, when files land or from a webhook.
One workflow, two places to run it.
Confirm that the workflow’s steps, connections and operator inputs are supported headlessly. Headless execution is included with Pro and Enterprise.
How a headless deployment works.
The runner, nf, is a background service on your machine under launchd or systemd. It starts at login and restarts after a crash.
- 01
Send it from the browser
Export the App or Automation as a file, or send it straight to a paired runner.
- 02
Install the runner
One command with an install code downloads nf and signs the machine in.
- 03
Choose a trigger
Run it from the command line, on a schedule, from a watched folder or from a webhook.
- 04
Read the record
Every run leaves a record on the machine: what ran, what it produced and how it ended.
# install and sign in with your install code curl -fsSL https://nodefox.ai/nf/install.sh | sh -s -- --code NF-… # deploy what you exported, run it as a service nf deploy order-check.nfx nf service install # weekdays at 07:00, Chicago time nf dispatch order-check --schedule "0 7 * * 1-5" --tz America/Chicago # what ran and how it ended nf runs
Start runs the way your work arrives.
Each deployed workflow has one trigger, with its own policy for errors and for questions nobody is there to answer.
Command line
Run on demand, from your own scripts, or from an agent through the runner’s MCP server.
Schedule
Cron with a time zone; a firing missed while the machine was off is skipped, not replayed.
Watched folder
Each file that lands in the folder starts a run with that file as its input.
Webhook
A bearer-token endpoint on the machine’s loopback; put your reverse proxy in front to expose it.
A machine, access and keys.
A host machine
A reverse proxy with TLS
Access to your systems
Model provider keys
- Windows and Intel Mac runners
- Offline or air-gapped runs
- MCP tools and OAuth connections inside headless workflows
- Remote or mobile approvals for headless runs
- A runtime or control plane hosted for you
Does a headless run need the internet?
What happens if the machine restarts or the runner crashes?
Who answers a question a headless run asks?
What happens when a step fails?
Plan where your workflow will run.
Bring the workflow and the machine you have in mind. We’ll cover triggers, access and what each run should record.