SecurityComing soon
Secrets / Vault Input
Will bring named secrets — a database password, an API token — into a flow as rows, so later nodes can use them without the secret being written in the flow.
When to use it
Use it when a step needs a credential that should be kept, rotated and audited in one place rather than typed into node settings.
In a pipeline
Secrets / Vault InputREST API
Settings
| Setting | Type | Required | Default or hint |
|---|---|---|---|
| Secrets | select | Yes | e.g. prod/db_password |
Example
A password from the vault
- Secrets=prod/db_password
| Secret | Value |
|---|---|
| prod/db_password | •••••••• |
Worth knowing
- Coming soon: FlowDoo has no store of named secrets yet — only the credentials inside saved connections — so how secrets are named and stored is still to be decided.
- Secret values will never appear in previews, run logs or exports.