N4N · CONNECT
Connect once.
n4n Connect links the accounts you already work in — Google, Slack, Notion, GitHub — to your n4n agents. You grant the access on the provider's own consent screen, n4n holds the resulting credential under encryption, and your agent can then do the few specific things you allowed. Nothing more, and only when asked.
HOW IT WORKS
Four steps, then it is yours.
A connection is just a credential you lent us, scoped to a handful of actions and revocable the moment you change your mind.
Connect an account
Pick a service and sign in on its own consent screen. n4n never sees your password — only the access the provider issues afterwards.
Your agent gets tools
Each connection turns into a small set of named actions — list events, create an event, send an email — that an agent can call on your behalf.
Credentials stay sealed
Tokens are encrypted before they touch the database and decrypted only in memory, for the moment a request runs.
You can end it
Disconnect deletes the stored credential outright. You can also revoke n4n from the provider at any time, without asking us.
GOOGLE ACCOUNTS
What we ask Google for.
Connecting a Google account lets an n4n agent work with your calendar, send a message you dictated, and keep its own working files. Here is every permission we request, and — just as important — what each one does not permit.
requested scopes · google account
userinfo.email · userinfo.profile · openid
Allows · Show which Google account a connection belongs to, so you can tell two connections apart.
Does not · Nothing else — it identifies the account, and reads no content.
auth/calendar
Allows · List your upcoming events, and create an event when you ask for one.
Does not · Nothing happens on its own — no background sync, no scanning your history.
auth/gmail.send
Allows · Send a message you asked to send, from your address.
Does not · Read, search, list or delete your mail. Sending is the entire permission.
auth/drive.file
Allows · Create a file, and reopen files that were created through n4n.
Does not · See the rest of your Drive. This grant is per-file, not account-wide.
We do not read your Google data in the background, use it for advertising, sell or transfer it, or train models on it. n4n's use and transfer of information received from Google APIs adheres to theGoogle API Services User Data Policy, including the Limited Use requirements. The full detail is in ourprivacy policy.
TAKING IT BACK
Two ways out, both immediate.
Disconnect the account in then4n Connect dashboardand the stored credential is deleted, not just disabled. Or cut it off at the source from yourGoogle account permissionspage — you never need our cooperation to end access.