Integrations and environment

Connect an external service

Open Integrations in a project to browse the catalog enabled by your Amazi administrator. A connection belongs to the whole project rather than one chat or application. Full access or ownership is required to connect, replace, or reveal protected values. Browsing the catalog remains available without the built-in integrations feature; opening managed integration details and connecting require that feature in the project owner's plan. This restriction does not prohibit the agent from developing application code. Actual use of an external service still requires its own access and working connection.

Use All or a group tab to filter the catalog. Each group has an icon beside its name, shown in the color configured for that group.

The integration header shows its logo, name and connected status. Its groups appear below the name, separated by commas; integrations without a group show Other integrations. Use the back arrow to return to the catalog. For a connected service, Disconnect is in the header; Update connection stays beside the credential form. Disconnecting requires confirmation and does not automatically change your application's code.

Enter credentials only in the integration form. Amazi stores them outside chat and gives the agent variable names, connection status, and usage instructions without returning stored secret values. If an active task needs a disconnected integration, it can pause and show the same secure form; after an authorized member connects it, Amazi reconciles the development runtime and continues the task.

After you connect or skip an integration, the action appears in the chat's work summary. Saving or skipping a secure request for environment variables is recorded there too. The history shows names and outcomes, without credential values.

To name a service in a request, type @ in project chat and select it from the integration list. Connected services appear first and are tagged. A mention inserts the service name into your draft; connecting it remains a separate action. See Agent and chat.

Expand the integration panel in chat, enter the values you have and select Connect below the fields, or select Skip to continue without connecting. Empty values can be completed later in the integration settings. Opening another action panel collapses this one and preserves your entered values.

Integration and environment requests share one title and description followed by all requested inputs. An empty field shows the environment variable name as its placeholder.

Environment-variable requests show all variables together, without steps or a progress counter. Enter the values and choose Save to submit the whole form, or Skip to leave every requested variable unchanged. Saving an empty field sets that variable to an empty value. Collapsing the panel preserves your draft. Save, Connect and Skip stay visible at the bottom of the open section as you scroll.

For Yandex Metrica, the credential is an OAuth access token, separate from Client ID and Client secret. Follow the integration's token-issuance link while signed in to the account with counter access. Replace an existing token through Update connection, then ask Amazi to check the available counters.

Review Environment

Environment combines:

• custom project values;
• variables supplied by integrations;
• managed platform values.

Members with project view access can inspect names and sources. Only roles with environment-management access can reveal or change protected values. Integration values are edited at their owning connection instead of being duplicated as manual variables. In Environment, use the eye button beside a fixed value to reveal it. The managed database owner's current DATABASE_URL uses the same control when its value is available. Values start masked and remain read-only after revealing them. Empty or unavailable fixed values appear as empty fields, without placeholder dots.

Amazi can assign an already connected integration variable to its consuming applications without reading or changing the credential. Ask it to update the variable's application assignments; this does not require manually copying the token or editing the integration values.

Every custom, integration, Gateway, and Voice variable has an explicit application selection. Only the selected applications receive it in development and in the next production release. Vite exposes to browser code only names beginning with VITE_; Amazi does not rename variables. Runtime-owned secrets are separate: eligible server applications receive storage credentials, and only the managed database owner receives DATABASE_URL.

Each custom variable and integration credential has one value shared by Preview and published applications. Existing projects keep their previous production values as the shared values, including empty values. Previously separate development values are no longer used. Application selections stay the same.

When value changes take effect

Changing a value reconciles the retained development runtime. An active production release keeps the environment snapshot from its build, so publish a project update when production must use the new value. This reconciliation avoids stale process state without rewriting environment files that belong to the project. Amazi AI Gateway is configured on a separate project surface.

Available integrations