September 2026 release notes for Integration Service in Automation Cloud.

Added September 21, 2026: This change was released on September 18, 2026 but was not included in the release notes at the time.

Integration Service usage is no longer metered or billed. Connector activities, HTTP requests, and triggers are included under both the Unified Pricing and Flex licensing plans, in API workflows, Agents, Maestro Orchestrate, Maestro Automate, and RPA workflows.

The Integration Activity is no longer used as a consumption unit. Executing an activity no longer draws down Platform Units or API calls, and there is no allocation to exceed.

You can still review your Integration Service usage under Admin > Your Organization > Licenses > Consumables. These figures are informational only.

API workflow pricing transitions to a per workflow execution charge instead of charging for Integration Activities. For details, refer to API workflows licensing.

For more information, see Integration Service licensing overview.

The Epic FHIR connector is now available in preview. It reads clinical, administrative, and financial data from your organization's own Epic instance through Epic's Fast Healthcare Interoperability Resources (FHIR) R4 APIs, so your automations can work with that data in UiPath.

For more information, see About the Epic FHIR connector.

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.

Connector Builder adds a Global Scripts tab, where you can write JavaScript that runs for every API request your custom connector makes. Use a pre-request script to modify outgoing requests — injecting headers, building the vendor URL from configuration values, or stopping a request without calling the provider — and a post-request script to transform responses before they reach your workflow.

Scripts run in a sandboxed JavaScript environment with no network access and no package imports.

For details, see Global Scripts.

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. Configuring a connection is more straightforward as a result, particularly for Private (Relay) connections.

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.

Searching for a connector now matches its tags and description in addition to its name, so searching SQL returns Database Hub. This applies to the connector catalog, the connector picker when you add a connection, and the connector dropdown in the trigger form.