Inspect token and KV v2 metadata without reading secret values.
Explore 3 workflow actions for HashiCorp Vault, including account permissions and operation limits.
3 read actions0 write actions
WORKFLOW ACTIONS
What you can configure.
Choose an action in the workflow builder, connect an account, and map its inputs. These actions are available in the catalog; your account access and a successful test determine whether they work for your setup.
Get KV v2 metadata
Read
Read version and creation metadata for one secret without fetching its value.
Permissions and limits
Account permissions
read capability on the chosen KV v2 metadata path
Operation limits
Only a single path segment is accepted. Custom metadata, version history and secret values are excluded.
List KV v2 names
Read
List secret names in one folder of a KV v2 mount without reading values.
Permissions and limits
Account permissions
list capability on the chosen KV v2 metadata folder
Operation limits
Only one folder level is accepted per call. Names are not filtered by Vault policy; do not encode secrets in names.
Values are never requested, and at most 1000 names are accepted.
Token status
Read
Read the selected Vault token's policies and lifetime without returning its ID or accessor.
Permissions and limits
Account permissions
Token can look up itself
Operation limits
Token ID, accessor, entity metadata and raw provider data are excluded.
SETUP
Start with a controlled test.
01Connect the intended account
Use the account and permissions required for your process. Review the connection check before configuring a workflow action.
02Review inputs and access
Select a listed operation and map its required inputs. Use test records and add a human approval before writes that need review.
03Confirm the result
Inspect step outputs and confirm the result in HashiCorp Vault. A saved workflow is not a completed provider action.