Skip to main content

​
Secrets and safe execution

Your custom logic runs in a protected environment. GenieForge and your app work with project data through that environment; you should not paste database connection strings or API keys into chat. When a capability must call an external API, sign a webhook, or hold a credential: store the secret first under Environment Variables, then brief Build to use the named variable (never the raw value).

​
Where it lives

  • App Settings → Connections → Environment Variables for named secrets (values stay hidden).
  • App Settings → Connections → Outbound network for which hosts tools may call.

​
How to verify

  1. Confirm the name exists under App Settings → Connections → Environment Variables (values stay hidden).
  2. Run the flow or automation that should use it.
  3. Confirm success in Executions without the secret appearing in chat.
  4. For external calls, confirm App Settings → Connections → Outbound network allows the host.

​
Limits and notes

  • Prefer Environment Variables or the product’s secure prompts over pasting keys into chat.
  • Export/import moves recipe metadata; re-enter secret values in the destination.
  • For regulated or sensitive apps, ask support@genieforge.ai how networking should be set up before you rely on external calls.
  • To inspect production data without mutating it, use Builder read-only mode.