title | description | services | ms.service | author | ms.author | ms.reviewer | ms.suite | ms.topic | ms.date |
---|---|---|---|---|---|---|---|---|---|
Connectors for Azure Logic Apps | Microsoft Docs |
Automate workflows with connectors for Azure Logic Apps, including built-in, managed, on-premises, integration account, and enterprise connectors |
logic-apps |
logic-apps |
ecfan |
estfan |
klam, LADocs |
integration |
article |
08/23/2018 |
Connectors play an integral part when you create automated workflows with Azure Logic Apps. By using connectors in your logic apps, you expand the capabilities for your on-premises and cloud apps to perform tasks with the data that you create and already have.
While Logic Apps offers ~200+ connectors, this article describes popular and more commonly used connectors that are successfully used by thousands of apps and millions of executions for processing data and information. Connectors are available as either built-ins or managed connectors.
Note
For the full list of connectors and each connector's reference information, such as actions, any triggers, and limits, you can find the full list under the Connectors overview.
-
Built-ins: These built-in actions and triggers help you create logic apps that run on custom schedules, communicate with other endpoints, receive and respond to requests, and call Azure functions, Azure API Apps (Web Apps), your own APIs managed and published with Azure API Management, and nested logic apps that can receive requests. You can also use built-in actions that help you organize and control your logic app's workflow, and also work with data.
-
Managed connectors: These connectors provide triggers and actions for accessing other services and systems. Some connectors require that you first create connections that are managed by Azure Logic Apps. Managed connectors are organized into these groups:
Managed API connectors Create logic apps that use services such as Azure Blob Storage, Office 365, Dynamics, Power BI, OneDrive, Salesforce, SharePoint Online, and many more. On-premises connectors After you install and set up the on-premises data gateway, these connectors help your logic apps access on-premises systems such as SQL Server, SharePoint Server, Oracle DB, file shares, and others. Integration account connectors Available when you create and pay for an integration account, these connectors transform and validate XML, encode and decode flat files, and process business-to-business (B2B) messages with AS2, EDIFACT, and X12 protocols. Enterprise connectors Provide access to enterprise systems such as SAP and IBM MQ for an additional cost. For example, if you're using Microsoft BizTalk Server, your logic apps can connect to and communicate with your BizTalk Server by using the BizTalk Server connector. You can then extend or perform BizTalk-like operations in your logic apps by using the integration account connectors.
Note
For the full list of connectors and each connector's reference information, such as actions and any triggers, which are defined by a Swagger description, plus any limits, you can find the full list under the Connectors overview. For pricing information, see Logic Apps pricing details and the Logic Apps pricing model.
Logic Apps provides built-in triggers and actions so you can create schedule-based workflows, help your logic apps communicate with other apps and services, control the workflow through your logic apps, and manage or manipulate data.
![]() Schedule |
- Run your logic app on a specified schedule, ranging from basic to complex recurrences, with the Recurrence trigger. - Pause your logic app for a specified duration with the Delay action. - Pause your logic app until the specified date and time with the Delay until action. |
![]() HTTP |
Communicate with any endpoint over HTTP with both triggers and actions for HTTP, HTTP + Swagger, and HTTP + Webhook. |
![]() Request |
- Make your logic app callable from other apps or services, trigger on Event Grid resource events, or trigger on responses to Azure Security Center alerts with the Request trigger. - Send responses to an app or service with the Response action. |
![]() Batch |
- Process messages in batches with the Batch messages trigger. - Call logic apps that have existing batch triggers with the Send messages to batch action. |
![]() Azure Functions |
Call Azure functions that run custom code snippets (C# or Node.js) from your logic apps. | ![]() Azure API Management |
Call triggers and actions defined by your own APIs that you manage and publish with Azure API Management. |
![]() Azure App Services |
Call Azure API Apps, or Web Apps, hosted on Azure App Service. The triggers and actions defined by these apps appear like any other first-class triggers and actions when Swagger is included. | ![]() Azure Logic Apps |
Call other logic apps that start with a Request trigger. |
Here are built-in actions for structuring and controlling the actions in your logic app's workflow:
![]() Condition |
Evaluate a condition and run different actions based on whether the condition is true or false. | ![]() For each |
Perform the same actions on every item in an array. |
![]() Scope |
Group actions into scopes, which get their own status after the actions in the scope finish running. | ![]() Switch |
Group actions into cases, which are assigned unique values except for the default case. Run only that case whose assigned value matches the result from an expression, object, or token. If no matches exist, run the default case. |
![]() Terminate |
Stop an actively running logic app workflow. | ![]() Until |
Repeat actions until the specified condition is true or some state has changed. |
Here are built-in actions for working with data outputs and their formats:
![]() Data Operations |
Perform operations with data: - Compose: Create a single output from multiple inputs with various types. |
![]() Date Time |
Perform operations with timestamps: - Add to time: Add the specified number of units to a timestamp. |
![]() Variables |
Perform operations with variables: - Append to array variable: Insert a value as the last item in an array stored by a variable. |
Here are the more popular connectors for automating tasks, processes, and workflows with these services or systems:
![]() Azure Service Bus |
Manage asynchronous messages, sessions, and topic subscriptions with the most commonly used connector in Logic Apps. | ![]() SQL Server |
Connect to your SQL Server on premises or an Azure SQL Database in the cloud so you can manage records, run stored procedures, or perform queries. |
![]() Office 365 Outlook |
Connect to your Office 365 email account so you can create and manage emails, tasks, calendar events and meetings, contacts, requests, and more. | ![]() Azure Blob Storage |
Connect to your storage account so you can create and manage blob content. |
![]() SFTP |
Connect to SFTP servers you can access from the internet so you can work with your files and folders. | ![]() SharePoint Online |
Connect to SharePoint Online so you can manage files, attachments, folders, and more. |
![]() Dynamics 365 CRM Online |
Connect to your Dynamics 365 account so you can create and manage records, items, and more. | ![]() FTP |
Connect to FTP servers you can access from the internet so you can work with your files and folders. |
![]() Salesforce |
Connect to your Salesforce account so you can create and manage items such as records, jobs, objects, and more. | ![]() |
Connect to your Twitter account so you can manage tweets, followers, your timeline, and more. Save your tweets to SQL, Excel, or SharePoint. |
![]() Azure Event Hubs |
Consume and publish events through an Event Hub. For example, get output from your logic app with Event Hubs, and then send that output to a real-time analytics provider. | ![]() Azure Event Grid |
Monitor events published by an Event Grid, for example, when Azure resources or third-party resources change. |
Here are some commonly used connectors that provide access to data and resources in on-premises systems. Before you can create a connection to an on-premises system, you must first download, install, and set up an on-premises data gateway. This gateway provides a secure communication channel without having to set up the necessary network infrastructure.
![]() BizTalk Server |
![]() File System |
![]() IBM DB2 |
![]() IBM Informix |
![]() MySQL |
![]() Oracle DB |
![]() PostgreSQL |
![]() SharePoint Server |
![]() SQL Server |
![]() Teradata |
Here are connectors for building business-to-business (B2B) solutions with your logic apps when you create and pay for an integration account, which is available through the Enterprise Integration Pack (EIP) in Azure. With this account, you can create and store B2B artifacts such as trading partners, agreements, maps, schemas, certificates, and so on. To use these artifacts, associate your logic apps with your integration account. If you currently use BizTalk Server, these connectors might seem familiar already.
![]() AS2 decoding |
![]() AS2 encoding |
![]() EDIFACT decoding |
![]() EDIFACT encoding |
![]() Flat file decoding |
![]() Flat file encoding |
![]() Integration account |
![]() Liquid transforms |
![]() X12 decoding |
![]() X12 encoding |
![]() XML transforms |
![]() XML validation |
Your logic apps can access enterprise systems, such as SAP and IBM MQ:
![]() IBM MQ |
![]() SAP |
Some connectors provide triggers that notify your logic app when specific events happen. So when these events happen, the trigger creates and runs an instance of your logic app. For example, the FTP connector provides a "When a file is added or modified" trigger that starts your logic app when a file gets updated.
Logic Apps provides these kinds of triggers:
-
Polling triggers: These triggers poll your service at a specified frequency and checks for new data.
When new data is available, a new instance of your logic app gets created and runs with the data that's passed in as input.
-
Push triggers: These triggers listen for new data at an endpoint or for an event to happen, which creates and runs new instance of your logic app.
-
Recurrence trigger: This trigger creates and runs an instance of your logic app based on a specified schedule.
Connectors also provide actions that perform tasks in your logic app's workflow. For example, your logic app can read data and use this data in later steps of your logic app. More specifically, your logic app can find customer data from a SQL database, and process this data later in your logic app's workflow.
For more about triggers and actions, see the Connectors overview.
To call APIs that run custom code or aren't available as connectors, you can extend the Logic Apps platform by creating custom API Apps. You can also create custom connectors for any REST or SOAP-based APIs, which make those APIs available to any logic app in your Azure subscription. To make custom API Apps or connectors public for anyone to use in Azure, you can submit connectors for Microsoft certification.
-
For questions, visit the Azure Logic Apps forum.
-
To submit or vote on ideas for Azure Logic Apps and connectors, visit the Logic Apps user feedback site.
-
Are the docs missing articles or details you think are important? If yes, you can help by adding to the existing articles or by writing your own. The documentation is open source and hosted on GitHub. Get started at the Azure documentation's GitHub repository.