<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>N8n · Danilo Falcão da Silva</title><link>https://falcao.org/tags/n8n/</link><description>Field notes on Linux, containers, infrastructure &amp; AI by Danilo Falcão da Silva, a Senior DevOps Engineer with 20+ years in production. Belo Horizonte, Brazil.</description><generator>Hugo</generator><language>en-us</language><managingEditor>danilo@falcao.org (Danilo Falcão da Silva)</managingEditor><webMaster>danilo@falcao.org (Danilo Falcão da Silva)</webMaster><copyright>© 2026 Danilo Falcão da Silva</copyright><image><url>https://falcao.org/avatar.jpeg</url><title>Danilo Falcão da Silva</title><link>https://falcao.org/</link></image><lastBuildDate>Sun, 15 Nov 2026 08:52:00 -0300</lastBuildDate><atom:link href="https://falcao.org/tags/n8n/index.xml" rel="self" type="application/rss+xml"/><item><title>n8n Is Back: Nod, Your Personal Agent, Is Here</title><link>https://falcao.org/posts/nod-n8n-personal-agent-worth-your-attention/</link><pubDate>Sun, 15 Nov 2026 08:52:00 -0300</pubDate><dc:creator>Danilo Falcão da Silva</dc:creator><guid isPermaLink="true">https://falcao.org/posts/nod-n8n-personal-agent-worth-your-attention/</guid><category>nod</category><category>n8n</category><category>ai</category><category>ai-agent</category><category>open-source</category><category>self-hosting</category><category>linux</category><category>productivity</category><description>Nod is very good. n8n's standalone personal agent brings browser work, connected apps, memory, and explicit permissions to the everyday jobs that should not require another afternoon of tabs. Here's why I'm enthusiastic about it.</description><content:encoded><![CDATA[<p>Nod is very good. Let me put that at the beginning, before the architecture and the qualifications make this sound like a procurement document.</p>
<p><a href="https://nod.n8n.io/">n8n Labs&rsquo; new personal agent</a> is aimed at something I care about a lot: getting the annoying work out of the way. Invoices. Follow-ups. Finding the information scattered across three apps. That website you only visit once a month, which somehow manages to consume a different piece of your afternoon every time.</p>
<p>I like powerful models. I like coding agents. But not everything I want from AI involves a repository. Sometimes I would just like a piece of software to deal with the administrative nonsense so I can get back to the work I actually wanted to do.</p>
<p>That is what makes Nod so appealing. My verdict is enthusiastic; the specific capabilities below are documented product behavior, not a claim that I have independently tested every integration or reproduced n8n&rsquo;s evaluations.</p>
<h2 id="not-another-workflow-you-have-to-build-first">Not another workflow you have to build first</h2>
<p>First, the naming deserves a quick clarification: <strong>Nod is a standalone application from n8n Labs, not a node inside n8n, and not the n8n AI Assistant.</strong> You do not need an n8n account or an existing instance to use it.</p>
<p>The <a href="https://blog.n8n.io/meet-nod/">launch post</a> makes a useful distinction. n8n is often where a team runs shared processes. Nod is for the jobs that belong to one person, connected to that person&rsquo;s accounts.</p>
<p>That separation makes sense to me. A recurring business process deserves an explicit workflow, clear ownership, and predictable execution. But there is also a large category of work that does not justify becoming an automation project before it can stop being your problem.</p>
<p>Collect these invoices. Prepare me for tomorrow&rsquo;s calls. Find the unanswered question in that thread. Check whether this price changed.</p>
<p>I know how to write scripts. That does not mean every minor inconvenience should earn a repository.</p>
<p>Nod gives this work a different entry point: tell it the outcome you want, and let it work through the steps. If you already use n8n, you can connect your instance so Nod can work with your workflows too. You are not being asked to abandon one approach to benefit from the other.</p>
<h2 id="the-browser-is-where-this-gets-interesting">The browser is where this gets interesting</h2>
<p>Nod has its own computer environment and browser. It can work through connected apps such as Gmail, Calendar, Drive, Slack, and Notion, but it is not limited to the services with a convenient integration.</p>
<p>That matters because the real world did not agree to become a well-documented API.</p>
<p>There is always a supplier portal. A dashboard without a useful export. A cancellation flow designed by someone whose performance review apparently depends on how many times you reconsider leaving.</p>
<p>The examples n8n describes are refreshingly ordinary: download invoices from supplier portals, collect numbers from a dashboard, monitor prices, compare hotels, or work through a subscription cancellation. Those are advertised use cases, not errands I am claiming to have benchmarked. But they are exactly the right target.</p>
<p><strong>The interesting deliverable is the finished job, not a beautifully formatted explanation of how I could finish it myself.</strong></p>
<p>A chat assistant that explains where to click can be useful. An agent designed to do the clicking, collect the result, and come back when it needs a decision is addressing a different problem. Nod is going after that problem directly, and I love that.</p>
<h2 id="memory-that-earns-its-place">Memory that earns its place</h2>
<p>A personal assistant becomes much less personal if every conversation starts with onboarding.</p>
<p>Nod&rsquo;s documented memory system keeps preferences and context across conversations. It also saves procedures: how it completed a task, so it can reuse that knowledge and adjust it when a website changes. You can inspect, edit, or delete what it remembers.</p>
<p>That last part is important. I do not want personalization to mean there is an invisible collection of assumptions somewhere that I can only correct by arguing with a chat window.</p>
<p>The distinction between remembering facts and remembering how to do something is especially useful. Knowing which supplier I use helps. Knowing how to get the invoice out of that supplier&rsquo;s portal helps more next month.</p>
<p>Nod also supports scheduled jobs and several tasks running in the background, with conversations available through the app and channels such as Telegram and WhatsApp. That fits the role: a personal agent should be reachable where I am, rather than requiring me to keep another window under permanent supervision.</p>
<p>For me, this is a much stronger product idea than treating every request as an isolated prompt. The recurring work should get easier to delegate, not require the same explanation forever.</p>
<h2 id="the-permission-model-deserves-actual-credit">The permission model deserves actual credit</h2>
<p>I spend enough time around agents to appreciate a product that treats permission as part of the design rather than a warning at the bottom of the page.</p>
<p>Nod separates planning the work from checking whether an action is allowed. Its <a href="https://nod.n8n.io/docs/trust/">Trust layer</a> checks proposed actions against your request and instructions. When those do not cover the action, it asks. Payments require explicit approval.</p>
<p>This is not the same as asking you to approve every harmless step. Reading and drafting can proceed; an action such as sending an email can run when your request already authorizes it. The useful question is whether you actually asked for that action, not whether the agent can find a button to perform it.</p>
<p>Saved credentials have a separate path through Vault. According to the documentation, the model can see account names and status, but saved passwords and card details are filled privately rather than handed to it as text. Usage records let you review actions, sign-ins, and model use afterwards.</p>
<p>Those are good decisions. An assistant needs access to be useful, but access should not mean putting every secret into its conversation and hoping for the best.</p>
<p>The authorization check is itself model-based and can make mistakes. I would not call Nod immune to prompt injection or give a research preview unrestricted access to critical accounts. That does not diminish the design: it means there are concrete controls to evaluate instead of a vague promise that the agent will behave.</p>
<h2 id="open-source-provider-choice-and-a-real-linux-option">Open source, provider choice, and a real Linux option</h2>
<p>Nod is released under <strong>Apache 2.0</strong>. You can inspect the <a href="https://github.com/n8n-io/nod">source</a>, run it on your own machine or server, and choose the model provider.</p>
<p>I like that combination a lot. The personal assistant and the model do not have to be a single inseparable purchase. Supported options include API providers, ChatGPT plan sign-in, and local models. Local models still need the capabilities the agent depends on; a smaller model is not automatically a sensible choice for permission checks just because it fits in memory.</p>
<p>As of November 15, the <a href="https://nod.n8n.io/docs/get-started/install-desktop/">installation documentation</a> includes macOS, Windows, and a <strong>Linux x64 Flatpak preview</strong>. On Linux, a local assistant needs hardware virtualization, access to <code>/dev/kvm</code>, and a desktop secret store. It is a preview, not a claim of identical polish on every platform, but Linux is an actual installation path rather than a suggestion to buy another computer.</p>
<p>There is also an important distinction between local storage and entirely local processing. Nod keeps its database, files, memory, and saved logins on the machine running it. Your chosen model service still receives task data, connected services receive their requests, and default managed app connections use n8n and Composio. Usage analytics can be disabled in settings. Read the <a href="https://nod.n8n.io/docs/trust/privacy/">privacy documentation</a> rather than translating “runs locally” into “nothing leaves.”</p>
<p>For recurring work, I particularly like the server option. A laptop that is asleep cannot run your schedules. An always-on machine can keep the assistant available without making your desktop session its uptime strategy.</p>
<h2 id="useful-software-should-show-what-it-costs">Useful software should show what it costs</h2>
<p>Nod itself is free; model usage is not necessarily free. Refreshingly, the product gives that distinction somewhere to live other than your provider&rsquo;s billing page.</p>
<p>The <a href="https://nod.n8n.io/docs/use/spending/">Usage view</a> records work and model calls. For priced API usage, it provides cost estimates and monthly limits. Tasks can check in when spending passes a configurable threshold. Subscription usage is handled differently, and estimates are not a replacement for the provider&rsquo;s bill.</p>
<p>This belongs in a personal agent. A scheduled check that quietly consumes money is still consuming money, even if nobody has a chat window open.</p>
<p>I do not need every task to cost almost nothing. I need to know whether the result was worth what it cost, and I need a way to stop an unproductive task from becoming an expensive hobby.</p>
<h2 id="yes-i-recommend-trying-it">Yes, I recommend trying it</h2>
<p>Nod is a research preview. I would start with a bounded job, connect only the accounts it needs, and review the result. That is how I would introduce any software that can act on my behalf, not a polite way of retreating from the recommendation.</p>
<p><strong>I am very positive about Nod.</strong> The combination is excellent: connected apps, a browser for the gaps, memory you can inspect, recurring work, provider choice, and permissions that are part of the product rather than an afterthought.</p>
<p>What I like most is where that capability is pointed. Not at generating more things for me to read. At reducing the things I still have to do.</p>
<p>Give it one of those jobs you keep postponing because it is too small to become a project and too annoying to want to start.</p>
<p>That is a very good place for an agent to earn its keep.</p>
]]></content:encoded></item></channel></rss>