Azure Logic Apps Connectors
Select an icon to learn how to quickly leverage these APIs to build apps that call these services. These APIs can be used to build logic apps and or power apps or both.
For pricing information and a list of what is included with each Service Tier, see Azure App Service Pricing.
If you want to get started with Azure Logic Apps before signing up for an Azure account, go to Try Logic App. You can immediately create a short-lived starter logic app in App Service. No credit cards required; no commitments.
|Azure Blob||Bing Search||Box||CRM Online|
|Translator||Office 365 Outlook||Office 365 Users||Office 365 Video|
|SharePoint Server||Slack||SMTP||SQL Azure|
These APIs work with 2015-12-01-preview version of the service.
Several APIs provide triggers that can notify your app when specific events occur. For example, the FTP API has the OnUpdatedFile trigger. You can build an either a logic app or power app that listens to this trigger and takes an action whenever the trigger is fired.
There are two types of triggers:
- Poll Triggers: These triggers poll your service at a specified frequency to check for new data. When new data is available, a new instance of your app runs with the data as input. To prevent the same data from being consumed multiple times, the trigger may clean-up data that has been read and passed to your app.
- Push Triggers: These triggers listen for data on an endpoint or for an event to occur. Then, triggers a new instance of your app. The twitter API is one such example.
APIs can also be used as actions within your apps. Actions are useful for looking up data which can then be used in the execution of your app. For example, you may need to look up customer data from a SQL database when processing an order. Or, you may need to write, update or delete data in a destination table. You can do this using the actions provided by the APIs. Actions map to operations that are defined in the Swagger metadata.