Changelog
Keep up with the latest updates we’ve made in Workato.
Batch publish and new API for Workato PubSub
First, the new batch publish action allows you to send a batch of up to 100 events to a PubSub topic within one action. It's a valuable addition the Workato PubSub connector to go alongside the existing batch trigger.
Second, the PubSub API was moved to a totally new microservice resulting in increased throughput and up to a 50% latency decrease. The new API is now available on a new domain, event-streams.workato.com. Note that the old API version is still in operation and that both versions share the same auth tokens, data format, and endpoints to make it simple to migrate to the new API.
Custom webhook responses for custom connectors
With custom webhook responses, Workato Connector SDK developers can now build webhook triggers with custom responses to ensure triggers conform to their destination application.
This allows developers to create real-time triggers to applications like Microsoft, Facebook, and Adobe that require targets to respond in a specific format, making the Workato Connector SDK even more flexible.
This feature is available today for any dynamic webhook triggers created with the Workato Connector SDK.
Community Connectors: What’s new in October
We've released 15 new or updated connectors, including Trustcruit, streamlining recruitment feedback loops, and HeyMarket, enabling batch imports from Salesforce. We've also fine-tuned the SmartRecruiters connector, adding new actions related to job and candidate properties, enhanced the universal GraphQL connector, and more. Read our full update here.
Private communities now ready for EU data center
Our Embedded Private Community feature is now available in all of Workato's data centers, including US, EU, JP, SG, and AU data centers. With Private Community, users can choose the apps and recipes customers see as they browse for community recipes.
Streamline asset management with new filtering options
Discover assets more efficiently with our enhanced filters. Previously, you could only filter assets by type and status. Now, you can also filter by apps, recipe trigger, and editors.
Enhanced file operations in the FileStorage UI
With the latest UI updates, managing your files is now easier than ever. Users can:
- Download and Upload multiple files directly from the UI
- Create, organize and search files and directories
- Move, rename and delete files, and delete directories
- Quickly preview files for easy checking
On-prem Agent (OPA) 22.0 Release
- Security: updated Java runtime to version 17.0.9+9.
- MySQL: updated JDBC driver to version 8.2.0.
- Monitoring: fixed initialization error when starting agent with monitoring feature enabled.
- Hardening: fixed rare reconnection bug when using a proxy.
- Hardening: fixed memory consumption for long-running agents.
- Configuration: reduced default graceful shutdown timeout to 30 seconds.
See the OPA release notes for this and previous updates to OPA.
TableStorage Download as CSV
We are excited to announce that data tables in Workato TableStorage can now be downloaded as a CSV! This allows users to extract data stored in Workato TableStorage as CSVs and easily import to popular apps such as Microsoft Excel and Google Sheets with protection against formula injection.
Better Observability when Working Webhooks
Native webhook triggers configured for JSON payloads will now return a 400 bad request status code if the payload wasn't valid JSON. Additionally, to ensure consistency, starting from 6th November 2023, we will also start validating webhook triggers within the same workspace using the event name and webhook URL. If they have different configurations, we will prevent the recipe from starting.
These updates allow senders to see when events are not accepted so they can intervene and investigate immediately.
Recipe Lifecycle Management Enhancement: Option to Disregard Submit Button Command Recipe when Building Package
If a project includes a bot that is calling a recipe using a "Submit button command", we now allow building and deploying packages without the recipe in the folder. Previously, users would experience an error preventing them from building or deploying packages based on the missing recipe. This error can now optionally be disregarded. This aligns behavior to how packages can be built and deployed that reference Recipe Functions from different projects.