Skip to main content
Phinite uses three deployment environments — DEV, UAT, and PROD — for Agent Builds, Env. variables, and channel/trigger webhook URLs. Assign builds to an environment so runtime uses the correct secrets and endpoints.
Environment variable values are not embedded in the Agent Graph canvas. Configure them on the workspace Env. variables page and reference keys by name in tools and integrations.

​
Environment purposes

​
Env. variables

  1. Open workspace Env. variables (/{org}/workspace/{id}/environment).
  2. Click New Environment or edit an existing variable row.
  3. Enter the Variable Name and values for DEV, UAT, and PROD as needed.
  4. Save each row — sensitive values display masked in the table.
Environment variables table

Env. variables — DEV, UAT, and PROD columns per variable

Permissions: workspace.sidebar.environment. Full field reference: Env. variables.

​
Assign a build to an environment

  1. Create an Agent Build (Builds overview).
  2. When deploying:
    • Deploy to Channel — pick Development, UAT, or Production and assign the build (Deploy to channel).
    • Deploy as API / Cron — assign build on the trigger connection (Deploy a trigger).
    • A2A — TEST builds use registry-scoped URLs; LIVE uses production routing (Endpoints & lifecycle).
  3. Test in DEV first — send a channel message or call the trigger webhook.
  4. Promote assignment and webhook URLs to UAT, then PROD.
Keep variable names consistent across DEV → PROD. Only the values should change (API keys, base URLs, feature flags).

​
Access and monitoring

  • Restrict who can publish to PROD via User roles.
  • Track errors and session volume per environment in Observability.
  • Separate credentials per environment — never reuse production secrets in DEV.