External vault

Node catalog Actions

On this page

Read, browse and write secrets from an external vault.

Usage and specifics

Select an authorized external vault, path and key. read retrieves the secret; write changes the remote value. Restrict access and avoid copying the value into parameters or logs.

Technical type : external_secret. Runtime : nodulz.

Credentials and prerequisites

This node defines no dedicated external credential. Remote sources or execution targets may still need their own access credentials.

See the credentials guide if a remote source or execution target requires access.

Parameters

Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.

Parameter	Type	Default	Values / limits
`operation`	`enum`	`"read"`	`list`, `read`, `write`
`path`	`string`	`""`	-; max 2048
`key`	`string`	`""`	-; max 256
`value`	`string`	`""`	-; max 1048576
`vaultId`	`string`	`""`	-

Configuration help

vaultId Vault connection: Vault configured in instance administration and accessible to the workflow owner.
operation Operation: Read a value, browse secrets or explicitly write to the vault. Writing must be enabled on the connection.

Initial configuration

Initial catalog configuration example, to adapt before running. Keep secrets in credentials.

json

{
  "operation": "read",
  "path": "",
  "key": "",
  "value": "",
  "vaultId": ""
}

Verification

Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.