Changelog

The enhanced recipe API allows resetting one or more recipes either manually on an ad-hoc basis or through automations. Resetting a trigger makes it forget the data that it has picked up in the past so it will pick up the same historical data again. This is a great way to do a full data refresh for data replication, master data management, or reverse ETL type of use case.  Click to learn more about reset API.

We introduce file streaming support for connector SDK. With this, custom connector builders can:

• create triggers to download data sequentially in small chunks
• create actions that can upload data sequentially in small chunks. 

This allows the transfer of large files between apps or file systems without worrying about hitting the size limit. By removing the previous file limits of 100-200MB, connectors can now stream large files upwards of 10GB, enabling you to automate more.

Webhooks are a great way of responding to real-time triggers in other systems – through the use of our webhook-based connectors or by creating your own through the Custom Connector SDK. For many automations, a single or small set of updates will use a webhook to trigger your recipe.  This creates events that are sent to our webhook gateway that then creates a job.

Introducing Webhook Gateway Limits

However, some triggers may invoke thousands of webhooks – such as some bulk updates – that happened in the source system.  To ensure ongoing reliability and performance of the platform, we introduced Webhook Gateway Limits for cases where a large number or size of webhook events are created.  These new rate limits will be based on the number of events or memory you can send in a specific time interval.  

With this SAML SSO enhancement, you will now be able to manage the roles of your collaborators from your identity provider that you used to configure SAML SSO. This allows you to govern roles you already use without having to duplicate in Workato, allowing for a more efficient way of managing role changes across different workspaces.

What this means:

• Admins no longer need to manage collaborator roles manually on the Workato platform
• Users are able to provision / de-provision environment-specific access to your collaborators from their identity provider via custom / system roles.
• Workato roles are automatically synced and updated from user profile data on your organization’s identity provider each time a user signs into Workato via SAML SSO

Users can now handle user input of Slack Modal Dialogs in the same recipe.

How it works
The Workbot recipe job will suspend until the user provides input and closes the modal. The job continues to the next action when it receives the input; it does not run a separate command as a distinct recipe trigger.

What this means for users
This enables users to specify multiple steps of Workbot-user interaction in one recipe, streamlining logic, reducing the number of recipes, and avoiding artificial and unnecessary bot commands.

A new version of the on-prem agent has been released with updates in security, new on-prem agent monitoring, added support for Cliend ID and Secret encryption, and more. Click here for the full version notes.