Common Connections and Activities¶
A connector provides an interface for creating a connection, the foundation used for generating instances of connector activities. These activities, once configured, interact with an endpoint through the connection.
A connector is used to first configure a connection. Activity types associated with that connection are then used to create instances of activities that are intended to be used as sources (to provide data in an operation) or targets (to consume data in an operation).
Together, a specific connection and its activities are referred to as an endpoint. The activities available depend on the connector. This example shows a Dynamics 365 Sales endpoint with its activities:
The available activity types depend on the individual connector. For many connectors, these activities are available:
Verbose logging can be enabled for many connectors when used with a Private Agent. See the documentation for each connector and Verbose Logging for Connectors for details.
Prerequisites and Supported API Versions¶
A connector requires the use of an agent version 10.1 or later. These agent versions automatically download the latest version of the connector when required. Certain connectors may require a specific or later agent version.
Depending on the connector, schemas may be generated directly from the endpoint, fixed in the connector, or provided by the user. When generated directly from the endpoint, many connectors use a REST API and JDBC driver. Refer to the API documentation, as available, for information on the schema nodes and fields.
Limitations and Supported Features¶
See the documentation for each connector as to any limitations and as to the supported features of the connector endpoint.
Depending on the usage, connectors do not support table and field names that are not valid XML names if they appear as fields or nodes in a schema. A workaround is to rename any table or field names that do not comply with the XML specification.