Keep up with the latest updates we’ve made in Workato.
Wait for a user to act on Slack
Our Workbot for Slack connector now allows you to wait for a user to act on Slack before continuing your recipe. This means you no longer have to build multiple recipes, saving time and effort.
Delete messages on Microsoft Teams
We've introduced a new delete message action to our Workbot for Microsoft Teams connector. Use it to make your users' Microsoft Teams experience more dynamic.
Create magic with OpenAI and automations
Always looking for innovative ways to use ChatGPT in our work, we're thrilled to introduce OpenAI as one of our connectors!
This means you can now power all kinds of workflows with OpenAI’s AI models. We’re starting off with 5 new actions that you can use right away—and we’ll be adding more soon—including the ability to use the same model that powers the conversational ChatGPT.
Sounds exciting? Go ahead and start exploring the new OpenAI actions. We can't wait to see what you'll create with them. And don’t forget to stay tuned for more updates!
Safely retrieve secrets and API tokens, with HashiCorp Vault
We’re excited to share that Workato now supports HashiCorp Vault secrets engine, a security feature many of our customers have been asking for.
HashiCorp Vault is an external secrets manager that lets you store and retrieve passwords and API tokens in a secure way. And trust us, this comes in super handy when you create or update a connection on Workato.
Publish and consume PubSub topics with APIs
We've just introduced APIs for PubSub. This means you can have 3rd party applications directly publish to and consume events from a PubSub topic, making it easier than ever to keep everything in sync.
What’s new with connectors: April edition
Gmail and Google Calendar
Google has service accounts for apps to access Google APIs programmatically via OAuth 2.0. Use service accounts to make sure connections run even when permissions for individual users change.
Enjoy the option of storing empty files in your file storage solutions, now that file contents are optional for these connectors.
We had to fix a couple of issues to improve the experience with authentication, input and output schema. And in more exciting news, there's a new set of endpoints that lets you read and manage your Workday Drive documents in your recipes.
Now you can get more specific with your JSON filters when using the search records action, by using symbols like “=”, “>” or “<”.
Manage your Sharepoint files and folders in your recipes, with new actions that allow you to copy file, move file and rename file or folder.
SendGrid deprecated some endpoints like create/update recipient, search recipient and add recipient to list, so we’ve removed these actions to avoid any “403 forbidden” errors.
Beefed up with 5 new actions, you can now update deals, update persons, get deal-related products, create notes and create activities.
Support for the Evernote connector has been removed, since our customers have moved on to other note taking apps, and its usage has been low.
Workday’s multi-instance custom objects now supported
Our Workday connector now supports creating, updating, and retrieving not only single-instance custom objects but multi-instance ones too! This means you can attach more than one instance to a parent object, which is handy when you need to add, say, an employee's multiple COVID-19 vaccination records.
Oh, and we've made these actions much more user-friendly too.
SAP connector is now SAP certified
Our SAP certification demonstrates that our connector is reliable, secure and efficient for our customers.
This gives organizations and their IT teams confidence that our integration does not pose risks of errors, data inconsistencies, nor security breaches.
Longer timeouts for API requests
You can now increase timeout durations—from the default 30 seconds, up to 240 seconds for the endpoints that need it. Just note that this works only for endpoints created on the API platform.
Better quality of service and stability with API throttling
API requests that exceed the workspace’s concurrency limit will no longer be rejected. Instead, when API requests spike, API throttling will come into play. This will delay the requests a little, depending on their size.