• Custom n8n node
  • Security
  • AI-agent tool

Passbolt

Fetch secrets from Passbolt at run time instead of hard-coding passwords in workflows.

How it works in practice

Signing in to a portal without a password in sight

How we apply it

It is the first step of our portal robots, such as the bank statement download across several banks, so no password ever sits inside a workflow.

This node signs in to a Passbolt password manager with the user's GPG key and returns a stored secret together with its metadata: name, username, URL and description. Both Passbolt v4 resources (plaintext metadata) and v5 resources (encrypted metadata) are supported, with automatic metadata decryption.

We built it for the portals that RPA and browser automations have to log in to. Credentials live in one audited vault, workflows pull them only when they run, and rotating a password means editing one Passbolt entry instead of dozens of workflows. The node has a credential test button in n8n and is usable as an AI agent tool.

In practice it is the first step before a Playwright or Robot Framework flow signs in to a bank, utility or supplier portal. It runs in 8 of our production workflows.

Limits: there is a single operation, Authenticate. The output contains the plaintext secret, so downstream nodes and execution-data retention need to be set accordingly.

For your technical team: it installs from npm as

n8n-nodes-kt-passbolt

What it means for you

  • Passwords live in one place, not scattered across automations

  • Changing a password is one edit, not dozens

  • Access is controlled and can be audited

Want Passbolt in your n8n?

Tell us what the workflow has to do and what it connects to. We will say whether this node covers it as it stands, what we would add, and when a different approach is the better one.