|
1 | 1 | ---
|
2 |
| -title: Traige incoming emails with power automate |
| 2 | +title: Triage incoming emails with Power Automate |
3 | 3 | titleSuffix: Azure Cognitive Services
|
4 |
| -description: Traige incoming emails with power automate |
| 4 | +description: Learn how to use custom text classification to categorize and triage incoming emails with Power Automate |
5 | 5 | services: cognitive-services
|
6 | 6 | author: aahill
|
7 | 7 | manager: nitinme
|
8 | 8 | ms.service: cognitive-services
|
9 | 9 | ms.subservice: language-service
|
10 | 10 | ms.topic: tutorial
|
11 |
| -ms.date: 06/03/2022 |
| 11 | +ms.date: 01/27/2023 |
12 | 12 | ms.author: aahi
|
13 |
| -ms.custom: |
14 | 13 | ---
|
15 | 14 |
|
16 |
| -# Tutorial: Traige incoming emails with power automate |
| 15 | +# Tutorial: Triage incoming emails with power automate |
17 | 16 |
|
18 |
| -In this tutorial we will triage incoming email using custom single text classification project type. When a new email is received, the content of the body gets classified and depending on the classificaiton result, a message is sent to the specialized team on Microsoft Teams. |
| 17 | +In this tutorial you will categorize and triage incoming email using custom text classification. Using this [Power Automate](https://learn.microsoft.com/power-automate/getting-started) flow, when a new email is received, its contents will have a classification applied, and depending on the result, a message will be sent to a designated channel on [Microsoft Teams](https://www.microsoft.com/microsoft-teams). |
19 | 18 |
|
20 | 19 |
|
21 | 20 | ## Prerequisites
|
22 |
| -* Azure subscription, <a href="https://portal.azure.com/#create/Microsoft.CognitiveServicesTextAnalytics" title="Create a Language resource" target="_blank">create a Language resource </a> in the Azure portal to get your key and endpoint. After it deploys, click **Go to resource**. |
23 |
| - * You will need the key and endpoint from the resource you created in your power automate flow. |
24 |
| - * Successfully created and deployed a [single text classification custom model](../quickstart.md). |
25 | 21 |
|
| 22 | +* Azure subscription - [Create one for free](https://azure.microsoft.com/free/cognitive-services) |
| 23 | +* <a href="https://portal.azure.com/#create/Microsoft.CognitiveServicesTextAnalytics" title="Create a Language resource" target="_blank">A Language resource </a> |
| 24 | + * (optional) A trained model if you're using a custom capability such as [custom NER](../custom-named-entity-recognition/overview.md), [custom text classification](../custom-text-classification/overview.md), or [conversational language understanding](../conversational-language-understanding/overview.md). |
| 25 | + * You will need the key and endpoint from your Language resource to authenticate your Power Automate flow. |
| 26 | +* A successfully created and deployed [single text classification custom model](../quickstart.md) |
26 | 27 |
|
27 |
| -## Create a power automate flow |
28 | 28 |
|
29 |
| -1- [Signin to power automate](https://make.powerautomate.com/) |
| 29 | +## Create a Power Automate flow |
30 | 30 |
|
31 |
| -2- From the left side menu, choose *My flows* and create a *Automated cloud flow* |
32 |
| -:::image type="content" source="../media/create-flow.png" alt-text="A screenshot of the flow creation." lightbox="../media/create-flow.png"::: |
| 31 | +1. [Sign in to power automate](https://make.powerautomate.com/) |
33 | 32 |
|
34 |
| -3- Name your flow as *EmailTriage*, from triggers search for *email* and choose *When a new email arrives* option then click *create* |
35 |
| -:::image type="content" source="../media/email-flow.png" alt-text="A screenshot of the language flow." lightbox="../media/email-flow.png"::: |
| 33 | +2. From the left side menu, select **My flows** and create a **Automated cloud flow** |
36 | 34 |
|
37 |
| -4- Start by adding the right connection to your email. This connection will be used to access the email content. |
| 35 | + :::image type="content" source="../media/create-flow.png" alt-text="A screenshot of the flow creation screen." lightbox="../media/create-flow.png"::: |
38 | 36 |
|
39 |
| -5- To add a Language connector, search for *Azure Language* |
40 |
| -:::image type="content" source="../media/language-connector.png" alt-text="A screenshot of azure language connectors." lightbox="../media/language-connector.png"::: |
| 37 | +3. Name your flow `EmailTriage`. Below **Choose your flow's triggers**, search for *email* and select **When a new email arrives**. Then click **create** |
41 | 38 |
|
42 |
| -6- Search for *CustomSingleLabelClassification* |
43 |
| -:::image type="content" source="../media/single-classification.png" alt-text="A screenshot of Classification connector." lightbox="../media/single-classification.png"::: |
| 39 | + :::image type="content" source="../media/email-flow.png" alt-text="A screenshot of the email flow triggers." lightbox="../media/email-flow.png"::: |
44 | 40 |
|
45 |
| -7- Start by adding the right connection to your connector. This connection will be used to access the classification project. |
| 41 | +4. Add the right connection to your email account. This connection will be used to access the email content. |
46 | 42 |
|
47 |
| -8- In documents id field, add **1**. |
| 43 | +5. To add a Language service connector, search for *Azure Language*. |
| 44 | + |
| 45 | + :::image type="content" source="../media/language-connector.png" alt-text="A screenshot of available Azure Language service connectors." lightbox="../media/language-connector.png"::: |
48 | 46 |
|
49 |
| -9- In documents text field add *body* from dynamic content. |
| 47 | +6. Search for *CustomSingleLabelClassification*. |
50 | 48 |
|
51 |
| -10- Fill in the project name and deployment name of your deployed model |
| 49 | + :::image type="content" source="../media/single-classification.png" alt-text="A screenshot of Classification connector." lightbox="../media/single-classification.png"::: |
52 | 50 |
|
53 |
| -:::image type="content" source="../media/classification.png" alt-text="A screenshot project details." lightbox="../media/classification.png"::: |
| 51 | +7. Start by adding the right connection to your connector. This connection will be used to access the classification project. |
54 | 52 |
|
55 |
| -11- Add condition to send a Microsoft Teams message to the righ team. Choose *results* from dynamic content and add the condition. For this tutorial, we are looking for *Computer_science* related emails. In the *Yes* condition, choose your desired option to notify the team. In the *No* condition, you can add further condition to check other cases and do alternative actions. |
| 53 | +8. In the documents ID field, add **1**. |
56 | 54 |
|
57 |
| -:::image type="content" source="../media/email-triage.png" alt-text="A screenshot of email flow." lightbox="../media/email-triage.png"::: |
| 55 | +9. In the documents text field, add **body** from **dynamic content**. |
| 56 | + |
| 57 | +10. Fill in the project name and deployment name of your deployed custom text classification model. |
| 58 | + |
| 59 | + :::image type="content" source="../media/classification.png" alt-text="A screenshot project details." lightbox="../media/classification.png"::: |
| 60 | + |
| 61 | +11. Add a condition to send a Microsoft Teams message to the right team by: |
| 62 | + 1. Select **results** from **dynamic content**, and add the condition. For this tutorial, we are looking for `Computer_science` related emails. In the **Yes** condition, choose your desired option to notify a team channel. In the **No** condition, you can add additional conditions to perform alternative actions. |
| 63 | + |
| 64 | + :::image type="content" source="../media/email-triage.png" alt-text="A screenshot of email flow." lightbox="../media/email-triage.png"::: |
58 | 65 |
|
59 | 66 |
|
60 | 67 | ## Next steps
|
61 | 68 |
|
62 |
| -[Language studio overview](../../language-studio.md) |
| 69 | +* [Use the Language service with Power Automate](../../tutorials/power-automate.md) |
| 70 | +* [Available Language service connectors](/connectors/cognitiveservicestextanalytics) |
0 commit comments