You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/digital-twins/how-to-use-power-platform-logic-apps-connector.md
+7-5Lines changed: 7 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,24 +32,26 @@ Lastly, you'll need to set up any [Power Platform](/power-platform) services whe
32
32
33
33
For Power Automate and Power Apps, set up the connection first before creating a flow. Follow the steps below to add the connection in Power Automate and Power Apps.
34
34
1. Select **Connections** from the left navigation menu (in Power Automate, it's under the **Data** heading). On the Connections page, select **+ New connection**.
35
-
1. Search for *Azure Digital Twins*, and select the **Azure Digital Twins** connector.
35
+
1. Search for *Azure Digital Twins*, and select the **Azure Digital Twins (preview)** connector.
36
36
1. Where the connector asks for **ADT Instance Name**, enter the [host name of your instance](how-to-set-up-instance-portal.md#verify-success-and-collect-important-values).
37
37
1. Enter your authentication details when requested to finish setting up the connection.
38
38
1. To verify that the connection has been created, look for it on the Connections page.
39
39
:::image type="content" source="media/how-to-use-power-platform-logic-apps-connector/power-connection.png" alt-text="Screenshot of Power Automate, showing the Azure Digital Twins connection on the Connections page." lightbox="media/how-to-use-power-platform-logic-apps-connector/power-connection.png":::
40
40
41
-
For Logic Apps, the connection is added as part of the flow. Continue to the next section to[create a flow](#create-a-flow).
41
+
For Logic Apps, you can use the Azure Digital Twins built-in connection when you[create a flow](#create-a-flow) in the next section. For more information on built-in connectors, see [Built-in connectors in Azure Logic Apps](../connectors/built-in.md).
42
42
43
43
## Create a flow
44
44
45
+
You can incorporate Azure Digital Twins into Power Automate flows, Logic Apps flows, or Power Apps applications. Using the Azure Digital Twins connector and over 700 other Power Platform connectors, you can ingest data from other systems into your twins, or respond to system events.
46
+
45
47
Follow the steps below to create a sample flow with the connector in Power Automate.
46
48
1. In Power Automate, select **My flows** from the left navigation menu. Select **+ New flow** and **Instant cloud flow**.
47
49
1. Enter a **Flow name** and select **Manually trigger a flow** from the list of triggers. **Create** the flow.
48
50
1. Add a step to the flow, and search for *Azure Digital Twins* to find the connection. Select the Azure Digital Twins connection.
49
51
:::image type="content" source="media/how-to-use-power-platform-logic-apps-connector/power-automate-action-1.png" alt-text="Screenshot of Power Automate, showing the Azure Digital Twins connector in a new flow." lightbox="media/how-to-use-power-platform-logic-apps-connector/power-automate-action-1-big.png":::
50
52
1. You'll see a list of all the [actions]() that are available with the connector. Pick one of them to interact with the [Azure Digital Twins APIs](/rest/api/azure-digitaltwins/).
51
53
:::image type="content" source="media/how-to-use-power-platform-logic-apps-connector/power-automate-action-2.png" alt-text="Screenshot of Power Automate, showing all the actions for the Azure Digital Twins connector." lightbox="media/how-to-use-power-platform-logic-apps-connector/power-automate-action-2-big.png":::
52
-
1. You can continue to edit or add more steps to your workflow to build out your integration scenario.
54
+
1. You can continue to edit or add more steps to your workflow, using other connectors to build out your integration scenario.
53
55
:::image type="content" source="media/how-to-use-power-platform-logic-apps-connector/power-automate-action-3.png" alt-text="Screenshot of Power Automate, showing a Get twin by ID action from the Azure Digital Twins connector in a flow." lightbox="media/how-to-use-power-platform-logic-apps-connector/power-automate-action-3.png":::
54
56
55
57
Follow the steps below to create a sample flow with the connector in Power Apps.
@@ -67,7 +69,7 @@ Follow the steps below to create a sample flow with the connector in Logic Apps.
67
69
:::image type="content" source="media/how-to-use-power-platform-logic-apps-connector/logic-apps-action.png" alt-text="Screenshot of Logic Apps, showing the Azure Digital Twins connector." lightbox="media/how-to-use-power-platform-logic-apps-connector/logic-apps-action.png":::
68
70
1. You'll see a list of all the [actions]() that are available with the connector. Pick one of them to interact with the [Azure Digital Twins APIs](/rest/api/azure-digitaltwins/).
69
71
1. After selecting an action from the Azure Digital Twins connector, you'll be asked to enter authentication details to create the connection.
70
-
1. You can continue to edit or add more steps to your workflow to build out your integration scenario.
72
+
1. You can continue to edit or add more steps to your workflow, using other connectors to build out your integration scenario.
71
73
72
74
## See example flows
73
75
@@ -78,7 +80,7 @@ For examples of using the connector in Power Platform flows, see [Azure Digital
78
80
Here are some limitations of the connector and suggestions for working with them.
79
81
80
82
* Some connector actions (such as Add Model) require input in the form of a literal string that starts with *@*. In these cases, escape the *@* character by using *@@* instead. This will keep the literal value from being interpreted as a JSON expression.
81
-
* Since Azure Digital Twins deals with dynamic schema responses, you should parse the JSON received from the APIs before consuming it in your application. For example, here's a set of calls that parse the data before extracting the `dtId` value: `Set(jsonVal, AzureDigitalTwins.GetTwinById(TextInput1.Text).result); Set(parsedResp, ParseJSON(jsonVal)); Set( DtId, Text(parsedResp.'$dtId'));`.
83
+
* Since Azure Digital Twins deals with dynamic schema responses, you should parse the JSON received from the APIs before consuming it in your application. For example, here's a set of calls that parse the data before extracting the `dtId` value: `Set(jsonVal, AzureDigitalTwins.GetTwinById("your_twin_id").result); Set(parsedResp, ParseJSON(jsonVal)); Set( DtId, Text(parsedResp.'$dtId'));`.
0 commit comments