HTTP(S) Connector is for calling Web APi's etc etc, and has a lot of the headers and other things supported in it.
Custom Connectors are whatever you want them to be. When you build you, you are usually doing it because IT will directly know how to talk to your companies exposed APi's, with its own authentication etc, versus using the HTTP connector, which may in fact work, but not do all the special little things you want your custom API Connector to do
Let's pretend, that every time someone tries to connect using a connector to your API, you want the code to send the words Nice Doggy... but not as part of the URL
You can make your custom connector do that, but the HTTP(s) connector.
Lots of other examples, but think of it as, I have special things I dont want to expose to a standard HTTP Call, and therefor my custom connector is built to do that, versus people being able to just use the HTTPs connector (and btw get charged premium dollars from microsoft)
Was this reply helpful?YesNo
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.