Automation for clients

Stage 2 · Lesson 4 of 8

Credentials

n8n in depth

n8n stores , OAuth connections and passwords as . They are encrypted, scrambled with an encryption key, inside n8n's database. Nodes then refer to a credential by its name.

This keeps secrets out of the workflow's JSON, so you can export or share a workflow without leaking keys. On a , meaning n8n running on your own , the encryption key lives in the n8n data folder. It can also be set in an , a setting passed to the server when it starts.

Lose that key and you lose every stored credential. For client work, create credentials from the client's own accounts, with the smallest scopes that work.

Common trappasting a key straight into an HTTP node header field, where it is exported with the workflow and visible to anyone who opens it.

A question to check yourself, an AI practice session and 2 cheat sheet entries come with the full roadmap. Unlock

Resources for this stage

Start with

  • CourseFree
    n8n Academy

    n8n · Beginner

    Free official courses from Essentials to APIs and AI, each with a certificate and badge

Practise

Keep handy

  • Node reference, expressions, the Code node, hosting and licence pages

Mark this stage as not done?