A personal desktop agent and a shared business workflow solve different problems. n8n Labs' Nod is a research-preview app that runs on one person's computer, while workflow automation is built to run a repeatable process for the business.
That distinction matters before an owner hands an agent access to Gmail, Calendar, Drive, Slack or a logged-in website.
What Nod is
n8n describes Nod as a separate personal-agent app from n8n Labs. It is not the n8n workflow product, and it does not require an n8n account. Nod runs jobs in a local sandbox with its own browser. It can use an API key, a ChatGPT plan or a local model, and the project says it is free and Apache 2.0 licensed.
The useful mental model is a supervised assistant on one laptop. It can take a plain-language request, use approved tools and work across sites that do not have an integration. It is not automatically a shared operations system with a central owner, service account and durable run history.
What a shared workflow does differently
A workflow starts from a defined trigger, reads known inputs and follows steps the business can review. It can run on a server, use a business-owned credential, write to a system of record and alert an owner when a step fails.
That makes a workflow a better fit for work such as:
- copying a web lead into the CRM and assigning an owner;
- checking an invoice status before sending an approved reminder;
- turning a maintenance request into a work order with an exception queue;
- sending a scheduled report from a known set of systems.
An agent can still help with the messy part, such as reading an email or choosing which approved path fits. Keep the write, payment, deletion and customer-facing steps deterministic or behind a person who can review them.
We'll separate the work that belongs on one laptop from the steps that need a shared workflow and approval path.
Five checks before Nod handles business work
1. Who owns the machine? Nod has one owner per installation and stops when the laptop sleeps. That can work for personal research. It is a poor fit for a process that must run when the owner is away. Decide where the job runs and who can recover it.
2. What can the agent reach? List the browser sessions, files and connected services it can use. Nod says saved logins and cards are encrypted on the machine and entered through forms the model cannot read. That reduces exposure to the model, but it does not decide which tasks the logged-in browser may perform.
3. What happens before an action? Nod's permission check is itself a model. The app asks when the user's words do not cover an action. Write down the actions that always need a person, such as sending an external message, changing a customer record, using a card or releasing money. Do not treat a permission prompt as a complete approval design.
4. How much can a run cost? The project documents a per-task check-in set to $5 by default and a monthly spending limit, with an estimated monthly cost for schedules. Check the limit before enabling recurring work. Early testers also found that some tasks cost more than expected, according to n8n's launch post.
5. What survives a failure? Nod is a local research preview, not a promise of a durable business queue. Test what happens when the laptop sleeps, the browser session expires, a site changes, or a task stops halfway. For a business process, record the input, action, result and person who owns the exception.
When Nod is a reasonable starting point
Nod may be useful for one owner testing a repetitive personal task, researching whether a browser-based job is worth formalizing, or handling work where a person remains present and can inspect each result. Start with read-only research and low-risk drafts. Use a separate browser profile and accounts with the narrowest access that lets the test work.
Do not start with payroll, payment release, account recovery, regulated records or a bulk customer message. Those jobs need an explicit owner, a defined approval step and a recovery path before an agent touches them.
When to build the workflow instead
Choose a shared workflow when the business needs the same process to run without one person's laptop, a central source of truth, predictable permissions, retries, alerts or a handoff when something fails. Workflow automation covers the repeatable path. AI agent systems fit the parts that need interpretation, tool selection or a conversation.
We usually combine them: a model extracts the request or proposes a next step, then rules and approvals control what changes in the business systems. Our AI agent permissions guide covers the approval boundary, and our free automation audit gives you a way to bring one real task for review.
Before you choose a tool, write down the task's owner, inputs, allowed actions, approval points, spending limit, failure alert and recovery step. If those answers belong to one person and one laptop, you are testing a personal assistant. If the business needs them to outlive that laptop, build the workflow around them.
Source note
The product details in this guide come from n8n's Nod announcement and the Nod documentation, checked November 12, 2026. Nod is a research preview, so verify current behavior before relying on a feature or limit.
