Microsoft Azure Logic Apps is an Azure cloud service that helps you schedule, automate, and orchestrate tasks, business processes, and workflows when you need to integrate apps, data, systems, and services across enterprises or organizations. Well that is the official definition any way. I like to think of them as a serverless way to bridge the gaps between systems like Slack, CRM, Twitter, Email and other APIs.
What really has always impressed me about Logic Apps is that they are incredibly simple to setup and use, where in years past, you as a developer, would have to write a lot of code to integrate each of the actions that they can take. Instead of having to spend hours per integration point, the work becomes just a few minutes of configuration inside of the Azure Portal and Logic Apps designer.
That is why I was surprised a few weeks back when I was using an Azure Logic App to integrate with my Kentico Xperience website and internal Slack team. During that work, I received a message from the third-party service that I was using, that my Webhook URL was too long. WTF? “How can a Webhook URL be too long?”, was my first thought when I saw that message. Then when I went to see where I could to configure the URL endpoint in my Logic App, I was again surprised that this didn’t seem possible.
Keep reading after the jump to find out how I solved the problem of my Azure Logic App HTTP endpoint being too long to use. Hint, with Azure, there is almost always a way to workaround issues like this.