← All topics

Secrets

Store API keys and credentials, keep them to yourself or share them with everyone on the account, then bind them in the wizard.

Why it works this way

Packs and connectors need credentials. Secrets live in one place so you are not pasting keys into chat, and you can reuse them on the next deploy.

Before you start

Steps

  1. Name the secret and set the value. You can reveal it while typing; Nested does not echo it after save.
  2. List your own secrets plus ones marked available to everyone. You can change only the ones you own.
  3. In the deploy wizard, bind a secret to the env the pack declared.

Example

Create “search-api” as Only me, then bind it when deploying a research pack that asks for SEARCH_API_KEY.

Open in Nested