September 2026 release notes for Integration Service in Automation Cloud Public Sector.

Perplexity is retiring its Sonar Chat Completions API (supported until September 27, 2026) in favor of the new Agent API. The Web Summary activity in the GenAI connector uses Perplexity as its search engine, so UiPath migrated it to the Agent API to keep your automations running. No changes are required on your side.

Because the Agent API differs from the Chat Completions API in request and response structure, the summary, citations, or model behavior may differ slightly. Re-test any workflows that parse the output of the Web Summary activity.

The Generate Text Completion activity in the OpenAI connector is deprecated. OpenAI is retiring every model that runs on the Completions API (/v1/completions) the activity uses: gpt-3.5-turbo-instruct and babbage-002 on September 28, 2026, and davinci-002 on October 23, 2026.

After October 23, 2026, the activity is no longer available for new workflows, and existing workflows that use it fail. Migrate these workflows to Generate Chat Completion. OpenAI also retires gpt-3.5-turbo on October 23, 2026, so workflows that select it in Generate Chat Completion must switch to a newer model before that date.

For details, refer to Generate Text Completion.

The Salesforce Agentforce & Flows connector is now generally available. Use it in agentic processes created in Maestro to send prompts to Salesforce Agentforce agents with Execute Salesforce Agent, run Salesforce autolaunched flows with Execute Autolaunch Flow, and close agent conversations with End Session.

For more information, see About the Salesforce Agentforce & Flows connector and About the Salesforce Agentforce & Flows activities.

Added September 17, 2026: This feature was released on September 10, 2026 but was not included in the release notes at the time.

You can now call the Integration Service API from a registered external application, so a service or script can authenticate on its own instead of relying on a signed-in user session. Register the application in Automation Cloud under Admin > External Applications, add Integration Service as a resource, grant it the scopes it needs, then request an access token using OAuth 2.0 and send it as a bearer token on your requests.

Access is confined to the scopes you grant. An external application, or a user acting through one, cannot exceed those permissions. Existing API access using user tokens is unchanged.

For details, see API access.

The Coupa connector adds a Requisition Comment Added event. Configure it against a specific requisition to start a workflow whenever a new comment is posted on it. The event fires for newly created comments only, including the comments Coupa creates automatically for lifecycle changes such as approvals and rejections.

For details, see Coupa events.

The connection form now has a Url field in place of Azure OpenAI Resource, for both the OAuth 2.0 Client credentials and API key authentication types. Enter the full base URL of your endpoint, including https:// — for example, https://your-resource-name.openai.azure.com. Previously you supplied only the resource name.

For details, see Microsoft Azure OpenAI authentication.

The Snowflake connector now supports OAuth 2.0 Client Credentials with Microsoft Entra ID authentication, which authenticates through a Microsoft Entra ID application using Snowflake External OAuth. Use it if your organization does not permit direct connections to Snowflake and requires all access to go through an Entra ID application. Existing connections are unaffected and require no changes.

For details, see Snowflake authentication.

The Database Hub connector adds a Database Sub Type selection for Databricks, letting you choose between Databricks Warehouse and Databricks Lakebase. Databricks Warehouse covers the existing SQL warehouse connections and is unchanged. Databricks Lakebase connects to a Lakebase PostgreSQL endpoint and authenticates with OAuth machine-to-machine (client credentials), so you can use Lakebase as an external source in Data Fabric.

For details, see Database Hub authentication.

The Salesforce Get Report activity is now named Get Report Metadata, which better reflects what it returns. The activity's behavior and its inputs and outputs are unchanged.