Application connectors provide connectivity to specific software applications such as Netsuite, Salesforce, SAP, or Amazon.
Application connectors are tailored for particular software APIs so you can quickly connect and perform data operations. For example, some operations expect a specific format or profile in XML or JSON representing a request message to that application or a response message from it. Operations for application connectors are typically configured with filters to limit the results returned. When you build endpoints into an integration, make your first choice to use an application connector.
The following image is an example of a configured Salesforce connection.
The following image is an example of a configured Salesforce operation.
Connector licenses and classes
Connection licenses are categorized and provisioned by connector classes:
- Small Business — For example, QuickBooks and Sage 50/Peachtree.
- Standard — For example, NetSuite, Salesforce, SFTP, Disk, and so on. Most connectors are Standard class connectors.
- Enterprise — For example, SAP and Oracle E-Business.
- Trading Partner — For example, your trading partner profiles, such as X12, HL7, EDIFACT, and so on.
In general, provisioning of your account is with the number of connection licenses based on your subscription. Therefore, you can deploy up to that many connections across your various integration processes. Each one consumes the licenses as you deploy processes containing unique connections.