Managing Secrets

Keep your sensitive data out of your code. Secret Store lets administrators securely store and manage API keys, client secrets, and tokens used in workflows and integrations.

---

Why use Secret Store

Previously, secrets were hardcoded in workflow JavaScript, which could expose them in the front end and database. With Secret Store:

• Secrets are stored securely in encrypted form

• Secrets are never exposed in the UI, database, or logs

Create a secret

1. Log in to your tenant as a community administrator.

2. Navigate to Settings > Secret Store.

3. Click Add new secret.

4. Enter a Name (a unique identifier used in workflows) and a Value (the API key, password, token, etc.).

5. Click Create.

Use secrets in workflows

Reference a secret inside workflow JavaScript using value substitution:

{{secrets.<secret_name>}}

For example:

const apiPassword = {{secrets.abc_api_key}};

At runtime, the system automatically replaces this with the actual secret value when executing the workflow.

How secrets are protected

• Write-only — once created, the value can never be viewed again

• Masked in the UI

• Never stored in plain text

• Not exposed in logs — even if explicitly printed, values are obfuscated

• Not directly accessible by other users

• Only the application runtime can resolve and use secrets

Note: Secrets can only be added or deleted — they cannot be edited or viewed after being added to the Secret Store.