Changelog

Workato supports Google Secret Manager, completing coverage of all three major cloud secrets managers alongside AWS Secrets Manager and Azure Key Vault.

• Runtime credential resolution: Credentials are pulled from Google Secret Manager at runtime—no secrets stored in Workato.
• Service Account authentication: Revoke Workato access to secrets at any time for enhanced security control.
• Project-level enforcement: Admins can require connections to use a secrets manager, eliminating plaintext credentials as an option.
• On-prem agent support: OPA connections are fully covered with Google Secret Manager integration.

This release enables enterprises to maintain a single source of truth for credential management across GCP environments, with rotation handled natively in Google Cloud Platform. Security teams can enforce consistent secrets management policies without exceptions for Workato.

Learn more about Google Secret Manager.

Decision Models are now generally available across all Workato subscription plans. Define decision tables once and reuse them across multiple workflows — replacing scattered conditional logic with a centralized, auditable, and scalable approach to complex business rules.

• Build and manage decision tables using an industry-standard format for conditional logic.
• Reuse models across multiple recipes for consistent outcomes in use cases like lead scoring, dynamic pricing, risk checks, and order fulfillment.
• Audit and update business logic in one place without touching individual workflows.
• Available to all customers, including Embed, as a core building block of enterprise automation.

Learn more about Decision Models.

The folder_id parameter is becoming required on three Developer API and OEM API endpoints that create assets. This supports the deprecation of the "Home Asset" folder and enables cleaner root folder structure and improved workspace organization.

POST /connections – folder_id must be specified when creating a new connection.
POST /recipes – folder_id must be specified when creating a new recipe.
POST /recipes/:recipe_id/copy – folder_id must be specified when copying a recipe.
Requests made without folder_id after May 7, 2026 will return an error response. Note that error formats vary by endpoint (HTTP 200 with error body, HTTP 422, or HTTP 400).
What you need to do:
Create a new folder in your Workato workspace (or use an existing one) and retrieve its folder_id.

Update your API calls to include the folder_id parameter before May 7, 2026.
If you have questions, contact your Customer Success Manager or reach out to Support.

Learn more about the Developer API.