Integration Service release notes

The Nvidia NIM connector is now generally available.

OAuth 2.0 Client Credentials is now available as an authentication method for the Salesforce connector. This server-to-server flow requires no user interaction and is suited for unattended automations that run as a dedicated system user.

For setup instructions, refer to Salesforce authentication.

The chat:write bot scope is now mandatory for all Slack connections, including OAuth 2.0 and Bring Your Own App authentication. This scope is required to complete the connection setup process.

If you use Bring Your Own App authentication, ensure your Slack app includes chat:write as a bot scope before connecting. For more information, refer to Authentication for Slack.

The List Email Attachments activity is now available in API workflows and agentic processes. It retrieves the list of attachments for a specified email message, returning metadata such as attachment name, content type, size, and whether the attachment is inline.

Integration Service can now reference credentials stored in any external credential management system supported by Orchestrator. This addresses security and compliance requirements for organizations with centralized credential management policies, and prevents connection breaks during credential rotations.

The feature works through Orchestrator credential assets. When creating a connection, select Use credential asset from the menu next to any secret-type field to reference a credential asset. Integration Service resolves the credential at runtime through Orchestrator and automatically refreshes it if the cached value becomes invalid.

For setup instructions, see Use credential assets for connections.

Integration Service now supports private connections to on-premises systems via Relay. Relay lets Integration Service connections securely reach on-premises HTTP and HTTPS endpoints inside your network — without a VPN, without opening inbound firewall ports, and without changing your network topology.

When creating a connection, you can now select the connection type:

A lightweight Relay client runs inside your network and establishes an outbound-only TLS tunnel to Automation Cloud or Test Cloud. An administrator must configure Relay before you can use private connections.

For Relay setup, refer to Relay in the Automation Cloud admin guide. For connection creation details, refer to Connecting to on-premises systems.

Relay does not work with the Amazon Web Service Connector.