After the holiday season, the Azure Logic Apps team were back with their monthly Google Hangout session – the seventh in the series – on January 28, 2015. This was quite an interesting session with lots of updates on the new features that were built over the last couple of months. We recommend you to read our earlier blog posts to understand the progress made by the Azure Logic Apps team in the past. (July, September, October, November).
Availability of Webhooks
Finally, after months of development, Webhooks can now be used in Logic Apps! The integration is so tight that when you post to Webhooks, the URL will not expose the subscription id and the resource group name. Also, when you want to move your resource or the Logic App, the static endpoint name is not affected by the resource move.
The endpoint has a SAS style authentication. When you get the endpoint URL for the triggers, its actually a SAS URL that can be independently called and its built in such a way that the custom code can now call the logic app directly! With this, you get full access to the headers and body in any format as you want.
HTTP Webhook Trigger
It’s a cool new functionality where with this Logic App trigger, you can subscribe to any other service (such as Github, SendGrid etc.,) and start getting events from the other services when some important event happens (like a commit, or a specific event). You no longer need to set up a listener or something similar to get the events from the services.
If you have a manual trigger, or you want a response from a HTTP Webhook trigger, you can send a response back from the Logic App and establish the request-response mechanism within the Logic App. This adds the HTTP request-response capability out-of-the-box with Logic Apps, instead of forcing you to use the HTTP listener to achieve this.
New Metrics for Azure Logic Apps
Run Throttles – There are times when the Logic App actually starts throttling when its pushed beyond the limit specified. With the Run Throttles metrics, you can now find out the events that point to when a logic app actually throttled during a period, and the root cause for the behavior.
What’s In Progress
Schema validation on Manual Triggers – possibility to describe a schema to the manual trigger and capability to validate the incoming request based on the defined schema)
WebHook Action – Intermediate between the HTTP Webhook Trigger and the subscribed service (such as GitHub, SendGrid, and so on). The action can actually wait for the responses to come back to the trigger.
Alerts – receive email notifications when something goes wrong in the Logic Apps
Logic Apps Designer Improvements (Coming Soon! Keep a watch out)
Managed APIs – all out of the box connectors will be managed by default. All you would hereafter need to do is the connection configuration management.
Auto discovery of custom APIs – Designer has the capability to automatically discover any custom API app (Web app/Mobile App), if the custom API definition has the URL on the API definition property
HTTP + Swagger
More control flow support
Call workflow improvements and designer experience
Improved trigger user experience – You can see all the triggers that you can actually call, and explicitly pick one or more triggers to run, and view the progress in the portal
The new logic apps designer definitely looks cool and it eases the effort involved in creating a logic app. Its definitely something the community needs to keep a watch on in the coming weeks. Stay tuned for more blogs from our side on the new logic apps designer.
If you are working on logic apps and have something interesting, feel free to share them with the Azure Logic Apps team via email or you can tweet to them at @logicappsio. You can also vote for features that you feel are important and that you’d like to see in logic apps here.
You can watch the full video here