Changelog

When using the Teams Workbot, you can now handle user button clicks in messages within the same recipe, without invoking a separate command and recipe. This allows for modeling a whole conversation in one recipe.

This feature is available to both Standard and Enterprise Workbot users.

We're sunsetting Microsoft Teams tabs functionality in Workbot for Microsoft Teams. Microsoft's new Teams client doesn't support Adaptive Cards in tabs, rendering Workbot tabs inaccessible. No comparable replacement functionality is currently planned by Microsoft. Check Microsoft's new Teams client release schedule to keep updated on when the new client will be rolled out (currently planned for March 31).

We advise users to transition onboarding content to custom help messages or develop web-based tabs. Our planned schedule for this transition is as follows:

Jan, 31st - All users who have created a Workbot with active tabs and admins of their accounts will receive an email with the notice.

Feb, 5th - The tab trigger and action will be deprecated and will no longer be available in new recipes. Existing recipes will continue to work (in ‘classic’ client)

March, 31st - We will share further sunset schedule based on customer usage and Microsoft's release schedule.

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.

Workbot for MS Teams now supports Tabs. Create multiple personalized views for your bots.

Configure access and permissions for Slack workbots with a single click.