Binding and deploying connections

Edit online

Connections link tools to the authentication method, credential model, and environment settings that are required to access external applications. Before tools can run, each one must be bound to a connection so that it can use the correct identity and configuration. When the agent is deployed, watsonx Orchestrate checks that every tool has a complete and valid live connection. This process helps maintain consistent behavior across channels and supports reliable execution in production environments.

Binding connections to tools

Tools must be bound to a connection before they can access a third‑party application. Binding links the tool’s operations to a specific connection, which supplies the authentication type, credential model (team or member), and environment settings (draft and live). A single connection can be reused by multiple tools, and tools can be unbound or rebound as integration needs evolve. Before deployment, every tool in an agent must have a configured live connection; deployment is blocked if any tool is missing a valid live binding.

Bind an existing connection

To bind a tool to a connection that exists in the Connections settings page, complete the following steps. This flow applies when you are importing a tool (for example, from an OpenAPI specification) and want to associate it with an available connection.

  1. From the menu Menu, navigate to Build.

  2. Navigate to All agents.

  3. Find and click your agent.

  4. From the agent's toolset in the Toolset section, click Add tool.

  5. Select open API.

  6. Upload the OpenAPI file for the application you want to integrate. The uploaded specification determines the authentication type and the supported security schema for the tool.

  7. Click Next. The tool import process analyzes the specification and lists all the available operations.

  8. Select the Operations that you want to include in the tool, then click Next.

  9. Review the list of relevant connections displayed.

    watsonx Orchestrate automatically identifies and suggests connections whose authentication type and security schema match the OpenAPI file.

    • Connections that match the required security schema appear as eligible.

    • Pending connection or pending configuration indicates that configuration or credentials are incomplete and cannot be selected.

    • If none of the existing connections are suitable, you can select Add a new item to create a new connection directly from this window without exiting the tool setup flow.

  10. Select an existing connection from the list to bind it to the tool.

    Only fully configured and valid connections can be selected. Using an incomplete connection causes the tool execution to fail.

  11. Click Done

    The tool is added to the toolset, and the bound connection is shown in the tool’s Connection section. You can preview the tool to verify that it uses the connection’s draft environment in preview chat.

After the connection is bound, the tool follows the connection’s environment behavior and you can verify how it is applied during testing and deployment:

  • The tool uses the draft connection when tested in preview chat.

  • After deployment, the tool uses the live connection configuration

  • In the tool’s Edit details view, the Connectors tab shows the bound connection and displays draft and live status. It also provides Edit and Delete options so you can update or unbind the connection when needed.

  • Deployment fails if any tool in the agent does not have a valid live connection.

Prerequisites when deploying agents with live connections.

Before you can deploy an agent, every tool in the agent must be bound to a connection that has a fully configured live environment. The Live environment defines the connection configuration that the agent uses in production channels such as in‑portal chat, Slack, Microsoft Teams, and embedded chat. If any tool is missing a valid live connection, the deployment cannot proceed.

watsonx Orchestrate performs a connection validation check during deployment. This check confirms the following conditions:

  • Each tool is bound to a connection

  • The bound connection has a complete live configuration

  • Live credentials (team or member) are present and valid

  • Authentication succeeds for the live connection

  • No environment is in a pending or error state

If a live configuration is incomplete such as missing URLs, incorrect metadata, missing credentials, or authentication errors the deployment workflow stops and displays an error message. You must fix the connection configuration before you try again. For more information about deploying agent with live connection see, Deploying agents.