{"id":110765,"date":"2017-01-23T05:24:28","date_gmt":"2017-01-23T13:24:28","guid":{"rendered":"https:\/\/cm-edgetun.pages.dev\/en-us\/power-platform\/blog\/power-automate\/search-by-service\/"},"modified":"2025-06-11T08:16:05","modified_gmt":"2025-06-11T15:16:05","slug":"search-by-service","status":"publish","type":"post","link":"https:\/\/cm-edgetun.pages.dev\/en-us\/power-platform\/blog\/power-automate\/search-by-service\/","title":{"rendered":"Search by service when you build flows and other new features"},"content":{"rendered":"

Search by service<\/h2>\n

When you build a flow from scratch<\/a>, you first choose the trigger to start the flow, and then the actions that you want to run. Previously, every single trigger and action that Microsoft Flow supported was included in a big flat list. We have added so many new services (now 90 total), that it could be difficult to find the trigger you wanted. Starting this week, you can now also browse triggers by the service they use. Simply select a service and you can see all of the triggers:<\/p>\n

\"\"<\/p>\n

Select See More<\/b> to see the full list of all services that are supported. Once you have selected a trigger, you can repeat the exact same process for adding an action:<\/p>\n

\"\"<\/p>\n

As before, you can still search across all of the triggers and actions, but now, you can also search the service names and descriptions as well.<\/p>\n

Switch case<\/h2>\n

Microsoft Flow supports nested conditionals, which make it possible to have very advanced branching logic. Today, we are making it very easy to have parallel branches of conditional logic based on a single value: known as a Switch case<\/strong>.<\/p>\n

\"\"<\/p>\n

You can find switch by selecting the More …<\/strong> option after selecting New Step<\/strong> and then choosing Add a Switch Case<\/strong>. Inside a Switch Case you will select a value from the trigger or a previous step to switch on. For example, if you use this template for a SharePoint approval flow<\/a>, the switch is on the option the approver selects in the approval email.\u00a0<\/p>\n

\"\"<\/p>\n

Below the Switch On, you can add as many cases you want. There is also a Default<\/strong> case that will run if the value is not found in any of the cases that you define. With switch case it should be much easier to build flows that work with many different options from a single step.<\/p>\n

Improved Email handling with Office 365 Outlook and Outlook.com<\/h2>\n

One of the most common scenarios for Microsoft Flow is to help you handle the daily flood of emails. Microsoft Flow has new features in both the Office 365 and Outlook.com services:<\/p>\n