Build custom connectors for Power Automate

Intermediate
App Maker
Microsoft Power Platform
Power Automate

This Learning Path explores custom connectors and explains how to configure them and use them with Microsoft Power Apps, Microsoft Power Automate, and Microsoft Azure Logic Apps.

Prerequisites

  • A basic understanding of Microsoft Power Automate.
  • Familiarity with Microsoft Power Platform, Power Apps, and Azure Logic Apps

Modules in this learning path

Connectors help make it easier for app and flow makers to connect to other apps, data, and devices in the cloud. Learn how to configure and use custom connectors with Microsoft Power Apps, Microsoft Power Automate, and Microsoft Azure Logic Apps.

Custom connectors can provide access to custom or third-party APIs that are accessible via public endpoints. In this module, learn how to configure custom connectors with authenticated APIs in Microsoft Power Automate.

Extend connector functionality in Microsoft Power Automate and Microsoft Azure Logic Apps, where a system needs to respond to the changes in the underlying data or services. In this module, you will learn how to expand the functionality of custom connectors with the trigger definitions.

Learn how to make your custom connector available to all users in Microsoft Power Platform GitHub repository.

Policies allow you to modify the behavior of a custom connector at runtime. You can use policies to perform data conversion, route requests, set parameter values, and more. You can configure policies directly in the custom connector API properties file before import, or you can do it from the maker portal in the custom connector designer by applying policy templates.

You can define extensions to OpenAPI to configure specific features that are supported by custom connectors in Microsoft Power Automate. This module covers authentication, actions, and triggers that are used with OpenAPI connectors.

The use case for your custom connector will determine how you want to manage the life cycle as it evolves. The primary scenarios are single environment usage, multiple environments usage, and open sourcing/certifying.