The concept of a Connector consists of two parts:
- The business logic is implemented by a Connector function and executed by a Connector runtime environment.
- The user interface during modeling is provided using a Connector template.
In a Self-Managed environment, you manage the execution environment for Connectors yourself. Using our Connector runtime environments, you can consume any set of Connectors, including the out-of-the-box Connectors and custom Connectors developed using the Connector SDK and Connector templates.
You can find a list of Connectors developed by Camunda, Partners, and the community in our Camunda Connectors Awesome List.
Some out-of-the-box Connectors are licensed under the Camunda Self-Managed Free Edition license.
Connector runtime and function
The Connector runtime environment can be installed using the supported deployment options.
Inbound Connectors require Operate to be deployed as part of your Camunda Self-Managed installation. If you don't use Operate with your cluster, you can still use Outbound Connectors.
For the modeling interface, you need to provide Connector templates.
For the out-of-the-box Connectors provided by Camunda, the Connectors Bundle project provides a set of all Connector templates related to one release version. If you use the Docker Compose installation, you can thus fetch all Connector templates that match the versions of the Connectors used in the backend.
Alternatively, you can fetch the JSON templates from the respective Connector's releases at respective connectors folder in the bundle repository
You can use the Connector templates as provided or modify them to your needs as described in our Connector templates guide.
Check out our Connectors Awesome List to find more Connectors.