Some apps just don't play nice with Power Automate.

Not every app has a built-in Power Automate action. When there isn't one, a custom connector is how you build it - wrapping an external API, an internal API behind an on-premises data gateway, or even simplifying a chatty Graph/REST API call into a single friendly action.

Simple API - simple connector. Not so simple API? That's where the fun starts.

Non-standard HTTP verb, a literal / inside a path parameter, credentials that can't live in a static connection... That's when a custom connector alone stops being enough, and you need an Azure Function behind it.

This session is a tour of both pieces:
•⁠ ⁠how to build and use a custom connector in a flow
•⁠ ⁠how to build and call an Azure Function directly from a flow
•⁠ ⁠how to have a custom connector call an Azure Function instead of the raw API

The running example is a real integration to a system Power Automate was never meant to talk with.