The HTTP Webhook connector now supports header-based authentication, letting you require the vendor to include a shared secret in a designated HTTP header on every webhook delivery. Requests that don't carry the configured header value are rejected with HTTP 401, preventing unauthorized callers from triggering your workflows.

For setup instructions, see HTTP Webhook authentication.

The Database Hub connector is now generally available. This release includes the following updates:

When you use the Repository field in connector activities, you can now select the repository from a dropdown which lists repos from all the organizations you have access to.

The Slack connector HTTP Request activity always used the OAuth user token, causing an invalid_auth error on connections with bot scopes only. The activity now falls back to the bot token when no user token is present, consistent with the curated Slack activities.

The Google Vertex connector now supports Gemini 3.1 Flash-Lite. The discontinued Gemini 2.0 flash model is no longer available. Gemini 3.1.x models require you to set the Region to global when adding a connection.

Snowflake is enforcing multi-factor authentication (MFA) for all users and removing password access for service accounts as part of Phase 3 of their strong authentication rollout, rolling out between August and October 2026.

Ahead of this enforcement, the Custom (password-based) authentication method will be removed from the Snowflake connector starting with July 20, 2026.

What you need to do: Existing connections using Custom authentication will continue working until Snowflake applies enforcement to your account. Recreate all connections that use Custom authentication with one of the following supported methods:

For setup instructions, see Snowflake authentication.

The MCP connector is now available in Preview. It is a universal connector that connects to any remote MCP (Model Context Protocol) server and dynamically invokes the tools that server exposes — from your RPA, API Workflow, and Maestro automations.

You create the connection once, authenticating with OAuth 2.0 (Authorization code, Authorization code with PKCE, or Client Credentials) or a Personal Access Token, and Integration Service handles connection, credential management, and governance centrally.

For more information, refer to About the MCP connector.