Secretsvault - hashicorp / n8n enterprise

Questions
1

Describe the problem/error/question

We´re on self hosted enterprise edition. Trying to integrate external secrets with Hashicorp.
Set up fails due to n8n inserting __n8n_BLANK_VALUE_ before hashicorps secret id.

This seems to be a bug

{
“data”: {
“id”: “133”,
“name”: “test”,
“type”: “vault”,
“isEnabled”: true,
“secretsCount”: 0,
“state”: “error”,
“secrets”: ,
“projects”: ,
“settings”: {
“authMethod”: “appRole”,
“kvVersion”: “2”,
“url”: “https://vault-service-platform.control-plane.prod.xxxxx.cloud/v1/”,
“roleId”: “ea08674a-4a31-582a-1999-xxxxxxxxx”,
“secretId”: “**__n8n_BLANK_VALUE_**e5362baf-c777-4d57-a609-xxxxxxxxxx”,
“kvMountPath”: “”
},
“createdAt”: “2026-04-13T10:03:27.600Z”,
“updatedAt”: “2026-04-13T10:03:54.678Z”
}
}

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version: 2.15.0
  • Database (default: SQLite): postgres
  • n8n EXECUTIONS_PROCESS setting (default: own, main): main
  • Running n8n via (Docker, npm, n8n cloud, desktop app): docker
  • Operating system: ec2 aws linux ami
2

hi @Kool_Baudrillard
Honestly, the first thing I’d try is treating _n8n_BLANK_VALUE as just a masking placeholder rather than a corrupted ID.

n8n uses that to hide stored secrets in other flows, so I usually just save the Vault config once, avoid touching that field again, and test the connection right away. If it works, it’s probably just a UI masking quirk and not an actual broken value.

If it’s still failing, I’d just recreate the Vault config from scratch, enter the roleId and secretId once, and save it without reopening the fields. If that still doesn’t do the trick, I’d probably just switch to a token temporarily to get things moving. If even that fails, it’s definitely a bug where the placeholder is leaking into the config.

3

Well,

i have tried all of your recommendations and still no connection possible.

4

@Kool_Baudrillard
At this point, I’d suggest posting it in the Known Issues category as well as opening a GitHub issue in the n8n repository. Please include your version (2.15.0), deployment type, exact repro steps, and the saved config showing _n8n_BLANK_VALUE being added to secretId.

That should give the team enough detail to reproduce and investigate properly.