Proposed Pull Request Change

📄 Document Links

View on GitHub View on Microsoft Learn

--- title: Use workflows to integrate Azure IoT Central description: How to configure rules and actions that integrate your IoT Central application with other cloud services by using Power Automate or Azure Logic Apps. author: dominicbetts ms.author: dobett ms.date: 08/06/2025 ms.topic: how-to ms.service: azure-iot-central services: iot-central # This article applies to solution builders. --- # Use workflows to integrate your Azure IoT Central application with other cloud services You can create rules in IoT Central that trigger actions in response to telemetry-based conditions. For example, to send an email when a device temperature exceeds a threshold. The Azure IoT Central V3 connector for Power Automate and Azure Logic Apps lets you create more advanced rules to automate operations in IoT Central: - When a rule fires in your Azure IoT Central app, it can trigger a workflow in Power Automate or Azure Logic Apps. These workflows can run actions in other cloud services, such as Microsoft 365 or a partner service. - An event in another cloud service, such as Microsoft 365, can trigger a workflow in Power Automate or Azure Logic Apps. These workflows can run actions or retrieve data from your IoT Central application. - Azure IoT Central V3 connector aligns with the generally available [1.0 REST API](/rest/api/iotcentral/) surface. All of the connector actions support the [DTDL v2](https://github.com/Azure/opendigitaltwins-dtdl/blob/master/DTDL/v2/DTDL.v2.md) format. For the latest information and details of recent updates, see the [Release notes](/connectors/azureiotcentral/#release-notes) for the current connector version. ## Prerequisites To complete the steps in this how-to guide, you need: [!INCLUDE [iot-central-prerequisites-basic](../../../includes/iot-central-prerequisites-basic.md)] ## Trigger a workflow from a rule Before you can trigger a workflow in Power Automate or Azure Logic Apps, you need a rule in your IoT Central application. To learn more, see [Configure rules](./howto-configure-rules.md). To add the **Azure IoT Central V3** connector as a trigger in Power Automate: 1. In Power Automate, select **+ Create**, then select **All connectors** under **Start from a connector**. 1. Search for *IoT Central*, and select the **Azure IoT Central V3** connector. 1. In the list of triggers, select **When a rule is fired**. 1. Select the **When a rule is fired** step, then ensure that you're connected. 1. Select your IoT Central application and the rule you're using. To add the **Azure IoT Central V3** connector as a trigger in Azure Logic Apps: > [!IMPORTANT] > Triggers in the IoT Central connector don't work unless the Logic App has a public endpoint. To learn more, see [Considerations for inbound traffic to Logic Apps through private endpoints](../../logic-apps/secure-single-tenant-workflow-virtual-network-private-endpoint.md#considerations-for-inbound-traffic-through-private-endpoints). 1. In **Logic Apps Designer**, select the **Blank Logic App** template. 1. In the designer, search for *IoT Central*, and select the **Azure IoT Central V3** connector. 1. In the list of triggers, select **When a rule is fired (preview)**. 1. In the **When a rule is fired** step, select your IoT Central application and the rule you're using. :::image type="content" source="./media/howto-configure-rules-advanced/triggers.png" alt-text="Find the Azure IoT Central - preview connector and choose the trigger"::: You can now add more steps to your workflow to build out your integration scenario. ## Run an action You can run actions in an IoT Central application from Power Automate and Azure Logic Apps workflows. First, create your workflow and use a connector to define a trigger to start the workflow. Then use the **Azure IoT Central V3** connector as an action. To add the **Azure IoT Central V3** connector as an action in Power Automate: 1. In Power Automate, search for *IoT Central* in the **Add an action** panel. 1. Select the **Azure IoT Central V3** connector. 1. In the list of actions, select the IoT Central action you want to use. 1. In the action step, complete the configuration for the action you chose, then select **Save**. To add the **Azure IoT Central V3- preview** connector as an action in Azure Logic Apps: 1. In **Logic Apps Designer**, in the **Choose an action** panel, select the **Custom** tab. 1. Search for *IoT Central*, and select the **Azure IoT Central V3** connector. 1. In the list of actions, select the IoT Central action you want to use. 1. In the action step, complete the configuration for the action you chose. Then select **Save**. :::image type="content" source="./media/howto-configure-rules-advanced/actions.png" alt-text="Find the Azure IoT Central V3 connector and choose an action"::: ## List of actions For a complete list of actions supported by the connector, see [Actions](/connectors/azureiotcentral/#actions). ### Create or update a device Use this action to create or update a device in your IoT Central application. | Field | Description | | ----- | ----------- | | Application | Choose from your list of IoT Central applications. | | Device ID | The unique ID of the device to create or update. | | Device Name | The display name of the device. | | Device Template | Choose from the list of device templates in your IoT Central application. | | Simulated | Choose whether the device is simulated. | | Enabled | Choose whether the device is enabled.| | Organizations | Choose from the list of organizations in your IoT Central application. | ### Delete a device Use this action to delete a device from your IoT Central application. | Field | Description | | ----- | ----------- | | Application | Choose from your list of IoT Central applications. | | Device ID | The unique ID of the device to delete. | ### Execute a device command Use this action to execute a command defined in one of the device's interfaces. > [!NOTE] > This action is deprecated. Use the **Run a device command** action to update both device property and cloud property values. | Field | Description | | ----- | ----------- | | Application | Choose from your list of IoT Central applications. | | Device ID | The unique ID of the device to execute a command. | | Device Component | The interface in the device template that contains the command. | | Device Command | Choose one of the commands on the selected interface. | | Device Template ID | Choose from the list of device templates in your IoT Central application. | | Device Command Request Payload | If the command requires a request payload, add it here. | > [!NOTE] > You can't choose a device component until you choose a device template. ### Get a device by ID Use this action to retrieve the device's details. | Field | Description | | ----- | ----------- | | Application | Choose from your list of IoT Central applications. | | Device ID | The unique ID of the device to get the details. | You can use the returned details in the dynamic expressions in other actions. The device details returned include: **Approved**, **body**, **Device Description**, **Device Name**, **Device Template**, **Provisioned**, and **Simulated**. ### Get device cloud properties (deprecated) Use this action to retrieve the cloud property values for a specific device. > [!NOTE] > This action is deprecated. Use the **Get device properties** action to retrieve both device property and cloud property values. | Field | Description | | ----- | ----------- | | Application | Choose from your list of IoT Central applications. | | Device ID | The unique ID of the device to get the cloud properties. | | Device Template ID | Choose from the list of device templates in your IoT Central application. | You can use the returned cloud property values in the dynamic expressions in other actions. ### Get device properties Use this action to retrieve the property values for a specific device. | Field | Description | | ----- | ----------- | | Application | Choose from your list of IoT Central applications. | | Device ID | The unique ID of the device to get the properties. | | Device Template | Choose from the list of device templates in your IoT Central application. | You can use the returned property values in the dynamic expressions in other actions. ### Get device telemetry value Use this action to retrieve the telemetry values for a specific device. | Field | Description | | ----- | ----------- | | Application | Choose from your list of IoT Central applications. | | Device ID | The unique ID of the device to get the telemetry values. | | Device Telemetry | The name of this device telemetry. | | Device Template | Choose from the list of device templates in your IoT Central application. | You can use the returned telemetry values in the dynamic expressions in other actions. ### Run a device command Use this action to execute a command defined in one of the device's interfaces. | Field | Description | | ----- | ----------- | | Application | Choose from your list of IoT Central applications. | | Device ID | The unique ID of the device to get the telemetry values. | | Device Command | Choose from the list of available device commands. After you choose a device command, a field is added for the device command connection timeout, device command response timeout, and, if applicable, the device command request payload. | | Device Template | Choose from the list of device templates in your IoT Central application. | ### Update device cloud properties (deprecated) Use this action to update cloud property values for a specific device. > [!NOTE] > This action is deprecated. Use the **Update device properties** action to update both device property and cloud property values. | Field | Description | | ----- | ----------- | | Application | Choose from your list of IoT Central applications. | | Device ID | The unique ID of the device to update. | | Device Template ID | Choose from the list of device templates in your IoT Central application. | | Cloud properties | After you choose a device template, a field is added for each cloud property defined in the template. | ### Update device properties Use this action to update writable property values for a specific device. | Field | Description | | ----- | ----------- | | Application | Choose from your list of IoT Central applications. | | Device ID | The unique ID of the device to update. | | Device Template | Choose from the list of device templates in your IoT Central application. | | Writable properties | After you choose a device template, a field is added for each writable property and cloud property defined in the template. | ## Next steps Now that you know how to create an advanced rule in your Azure IoT Central application, you can learn [how to use data explorer to analyze device data](howto-create-analytics.md).