Slack has introduced important updates to its Workflow Builder, introducing new options that make it simpler than ever for customers to create time-saving automations.
The updates embody plug-and-play workflow templates, enhanced developer instruments, and extra workflow steps from well-liked third-party apps like PagerDuty, Asana, and Bitbucket. These enhancements are designed to make no-code automation extra accessible to customers throughout numerous industries, enabling groups to streamline routine duties and concentrate on extra strategic actions.
Key Updates to Slack’s Workflow Builder
- Plug-and-Play Workflow Templates: Slack has launched 50 new plug-and-play workflow templates that permit customers to construct and customise no-code automations shortly and simply. These templates simplify the method of making workflows by offering pre-built constructions that customers can modify to suit their particular wants. Examples of those templates embody:
- Onboarding New Hires: Routinely add new crew members to related conferences, share essential recordsdata, and ship a welcome message once they be part of a Slack channel.
- Managing Recurring Conferences: Acquire agenda subjects, observe them in a Slack listing, and publish the agenda within the crew channel on the day of the assembly.
- Streamlining Incident Response: Collect incident particulars, create a devoted channel with the suitable crew members, and log the difficulty in instruments like Jira Cloud to trace progress towards decision.
These templates are designed to avoid wasting time and scale back the complexity of constructing workflows, permitting customers to automate each widespread duties and extra intricate processes with ease.
- Beginning Workflows from Third-Celebration App Actions: One of the highly effective new options is the flexibility to provoke workflows in Slack based mostly on occasions occurring in built-in third-party instruments. This integration helps centralize undertaking administration and reduces the necessity for context switching, which may drive down productiveness. For instance:
- If a important cellular app outage is logged in PagerDuty, a workflow in Slack can mechanically be triggered. This workflow would possibly embody creating an incident channel, including the appropriate crew members, organising a canvas, and sharing all related data from PagerDuty.
This function ensures that important updates and actions from exterior apps are seamlessly built-in into Slack, enabling groups to reply extra effectively.
- Enhanced Developer Instruments for Customized Workflow Creation: Slack has additionally launched new developer instruments that make it simpler for builders to create {custom} workflow steps. These instruments are a part of Slack’s open API platform and permit builders to construct and deploy specialised workflows sooner. Key enhancements embody:
- Customized Step Administration: Builders can create and handle {custom} steps instantly from the Slack app settings web page by way of a brand new, intuitive consumer interface.
- Versatile Internet hosting Choices: Customized steps can now be hosted wherever, giving builders the pliability to securely carry their providers into Slack.
- Integration with Present Slack Apps: Builders can improve current custom-built Slack apps, similar to bots, by including {custom} steps that can be utilized inside Workflow Builder. This enables for deeper integration between Slack apps and time-saving workflows.
Moreover, builders can select their most well-liked programming languages, similar to TypeScript, JavaScript, Python, and Java, when growing {custom} steps utilizing Slack’s SDK or Bolt framework.