Integration configuration field reference

Reference information for all configuration fields across the three integration types in the automation orchestrator: LLM Provider, Ansible Automation Platform, and MCP Server.

Common fields

The following fields are shared across all integration types. The name and URL field labels vary by integration type as noted below.

Table 1. Common integration fields
Field Description Required Default
Server name / ID A unique name for this integration. Yes None
Integration type The category of external service: LLM Provider, Ansible Automation Platform, or MCP Server. Set when creating the integration and cannot be changed. Yes None
Description An optional description of the integration and its purpose. No None
URL The endpoint URL for the external service. The field label isBase URL for LLM Provider and MCP Server integrations, orAAP URL for Ansible Automation Platform integrations. Yes None
Scope Controls integration availability. WhenGlobal is enabled, the integration is available to all projects. Disable to scope the integration to specific projects. No Global
State Enables or disables the integration. Disabled integrations are not available to workflows. No Enabled

Security fields

The following fields are available under the Security expandable section on the integration details page. These fields apply to all integration types.

Table 2. Security fields
Field Description Required Default
Allow HTTP connections Permits unencrypted HTTP URLs for this integration. No Disabled
Disable TLS certificate verification Skips validation of the server's TLS certificate on connections. No Disabled
CA certificate PEM-encoded CA certificate to trust for this integration's TLS connections. No None

LLM Provider fields

The following field is specific to LLM Provider integrations.

Table 3. LLM Provider fields
Field Description Required Default
Provider Select the LLM provider from the dropdown (for example, Red Hat AI, OpenAI). Yes None

Connection credential fields

The connection credential section is separate from the integration details. The credential configured here is used to verify the connection and perform periodic health checks. Workflow credentials are configured separately in the workflow builder.

Table 4. Connection credential fields
Field Description Required Default
Health check credential The credential used to test and monitor the connection to this integration. Select from existing credentials in the dropdown. Yes None

Health status values

The following health statuses are displayed on the Configuration > Integrations list page after an integration is saved.

Table 5. Health status values
Status Description
Available The endpoint is reachable and responding normally.
Validating The system is checking the integration endpoint.
Unknown The integration health status has not been determined.
Error The endpoint cannot be reached. Verify the URL, network connectivity, and health check credential.

Integration details page

Each integration has a details page accessible by clicking the integration name on the list page. The details page includes two tabs.

  • Details — Displays the integration name, type, status, URL, connection credential, and enabled resource count.
  • Resources — Displays the discovered resources and the timestamp of the last fetch. Available for LLM Provider and MCP Server integrations.