How to Connect Your Apps to Nod by n8n
Yes — connecting your own apps and accounts is the whole point of Nod. You authorize each app once, and from then on Nod can read and act inside it: triaging your email, prepping your calendar, turning Slack requests into tasks. Anything that has no integration at all, it can still handle through its own browser, using logins you save. This page covers what you can connect, how authorization works, and how you stay in control of that access. If you haven't installed Nod yet, start with Install on Mac or Install on Windows.
What you can connect
Nod is designed for a single player: it connects one person's own accounts and works on that person's business and household errands. n8n's own examples of connected apps in action include:
- Email and calendar — every morning Nod reads your mail threads and calendar and writes a one-page brief for each call.
- Slack and Linear — client requests sitting in email and Slack get turned into Linear tasks, deduplicated.
- Vendor portals and dashboards — logging in monthly to download invoices for your accountant, or pulling last week's numbers out of a dashboard that has no export button.
App connections run through a connection service: by default, connections are handled by an n8n-hosted connection service together with Composio. There is no fixed "integration list" to check your app against, because the second route covers everything else — see the browser section below.
The range of work those connections unlock is wider than messaging and mail. From n8n's own list of typical tasks: watching a price or a page and checking every few hours, reporting only when something changes; finding a hotel that fits your trip and booking it once you say go; pulling last week's numbers out of a dashboard with no export function and writing them into your weekly report; downloading month-end bank and tax documents and filing them by name; even booking a team offsite by comparing three venues and reserving the best once you nod. If a job lives in one of your accounts, connecting that account is what hands it to Nod.
One distinction worth knowing: Telegram and WhatsApp are not apps Nod works in; they are chat channels you can talk to Nod from, with the same conversation continuing across the app, Telegram, and WhatsApp.
How authorization works
You add a connection inside Nod and authorize your own account for that app. Nod only ever touches accounts you have connected yourself — there is no shared workspace and no second user; each install has exactly one owner.
For websites, the credential story is different and stricter. Logins and bank cards you save are stored encrypted in Nod's Vault on your own machine, and they are filled into pages through private forms that the AI model itself cannot read. Your password is never pasted into the chat, never shown to the model, and the same applies to card details when Nod pays for something on a site. This is also how Nod can work on websites that have no official integration at all: it opens its own browser, logs in with the saved credentials, and does the job like a person would. For the model side of setup, see Connect a model.
What Nod does once an app is connected
Connected apps are what let Nod prepare work instead of just answering questions. It reads your mail and calendar ahead of your calls, and it also works proactively: Nod reads the apps you've connected and suggests tasks it could take off your plate. n8n's example: it spots a client question you missed, drafts a reply from your own pricing sheet, and sends it only after you approve.
Everything it does is logged. Every login, card use, and action inside an app is recorded in Usage, together with what each task cost — so you can audit afterwards exactly where Nod went and what it did. For more on what connected Nod can take over, see Use cases.
Connected apps also feed Nod's memory and its routines. Tell it once that "Anna handles invoices now" and it remembers, with every memory visible, editable, and deletable, and labelled with the message it came from. It learns your writing style from the mail you send, so drafts in your inbox sound like you. And recurring jobs built on your connections — the morning brief, the price check — can be put on a schedule, while several tasks run in parallel in the background instead of queuing up behind each other.
It asks before it acts
Connecting an app does not give Nod a blank cheque. Before actions like sending, paying, posting, or deleting — anything you didn't explicitly ask for — Nod runs an independent check on whether the action is covered by your request and your rules. If it isn't covered, it asks you first. When Nod chases an unpaid invoice for you, for example, the first friendly reminder goes out, but it checks with you before sending a second, firmer chase.
The same boundary applies in the other direction: web pages and emails cannot give Nod instructions. Content it reads while working is treated as data, not commands, which is n8n's defence against prompt injection through a malicious page or message.
Privacy notes worth knowing
Your database, files, memory, and saved logins live on the computer (or server) running Nod. Two defaults deserve a look, though. First, as noted above, app connections route through n8n's hosted connection service and Composio by default — that is how the authorization is brokered. Second, new users share basic usage data with n8n by default; you can turn this off under Settings → Privacy & data (Share usage data). Conversation traces are only sent if you separately opt in.
Disconnecting an app
Connections are per-account authorizations, managed where you added them. Disconnecting an app in Nod cuts off its access going forward; you can also revoke Nod's access from the connected service's own account settings, wherever that service lists third-party access. Saved website logins are a separate thing: they sit in the Vault on your own machine, so removing them there ends Nod's ability to log in to that site. Either way, nothing about a connection survives you revoking it — Nod has no back door into an account you have disconnected.
New to Nod entirely? What is Nod explains the basics, the Tutorial walks through a first task end to end, and the Nod hub links every guide in this series.