Flow Vault

Securely store API keys, tokens, and passwords per flow.

Adding Secrets

1. Open the flow editor
2. Click the lock icon in the header bar
3. Enter a Key (e.g. API_KEY) and Value (e.g. sk-abc123...)
4. Click Save

Using Secrets

Reference vault secrets in any input field with double curly braces:

{{vault.API_KEY}}

This works in:

• Text inputs (Compose, URL, etc.)
• JSON fields (Headers, Body)
• Any static input value

Example

Using Vault Secrets

Store API key in vault, use in HTTP request headers

Text

Compose

template

Bearer {{vault.API_KEY}}

output

API Connector

Get

URL

https://api.example.com/data

Headers

{"Authorization": "Bearer ..."}

Status Code

Body

How It Works

• Secrets are encrypted with AES-256-GCM before storage
• Each flow has its own vault — secrets are not shared between flows
• At execution time, {{vault.KEY}} is replaced with the decrypted value
• In Execution History, vault values are masked — you'll never see the actual secret in logs

Best Practices

• Store API keys, bot tokens, client secrets in vault
• Use descriptive key names: OPENAI_KEY, AUTH0_SECRET
• Never put secrets directly in input fields — always use vault references
• Helper flows have their own vault — secrets from the parent flow are not inherited