This is the repository for Camunda Connectors. It manages all parts of the Connectors ecosystem, including the Connector SDK, out-of-the-box Connectors available in Camunda, the Connector Runtime, and the Docker images.

For more information on Connectors, refer to the Camunda documentation.

• License
• Create a Connector
  • Outbound Connector
  • Inbound Connector
• Connector Validation
• Start a Connector
• Build
• Build a release

This is a multi-module project with different licenses applied to different modules.

• Connector SDK including all supporting libraries
• Connector Secret providers implementations
• Connector Runtime and all its submodules
• Http Json Outbound Connector
• Element Template Generator and its submodules

• All Out-of-the-Box Connectors except for REST Connector (see above)
• Docker images of the out-of-the-box Connectors for Camunda, bundled with a runtime

When in doubt, refer to the LICENSE file in the respective module.

Include the connector-core, e.g. via Maven:

<dependency>
  <groupId>io.camunda.connector</groupId>
  <artifactId>connector-core</artifactId>
  <version>${version.connectors}</version>
  <scope>provided</scope>
</dependency>

Set the dependency to a provided scope as the runtimes that execute Connectors provide the necessary classes already.

To find the latest version, check the Maven Central repository.

Define your Connector logic through the OutboundConnectorFunction interface:

@OutboundConnector(
  name = "PING",
  inputVariables = {"caller"},
  type = "io.camunda.example.PingConnector:1"
)
public class PingConnector implements OutboundConnectorFunction {

  @Override
  public Object execute(OutboundConnectorContext context) throws Exception {
    var request = context.bindVariables(PingRequest.class);
    var caller = request.getCaller();
    return new PingResponse("Pong to " + caller);
  }
}

Define your Connector logic through the InboundConnectorExecutable interface:

@InboundConnector(
  name = "SUBSCRIPTION",
  type = "io.camunda.example.SubscriptionConnector:1"
)
public class SubscriptionConnector implements InboundConnectorExecutable {

  private MockSubscription subscription; // imitates some real-world subscription

  @Override
  public void activate(InboundConnectorContext context) throws Exception {
    var properties = context.bindProperties(SubscriptionProperties.class);
    // subscribe to events
    subscription = new MockSubscription(properties.getTopic());
    subscription.subscribe(event -> {
      context.correlate(event);
    });
  }

  @Override
  public void deactivate() throws Exception {
    // unsubscribe from events
    subscription.shutdown();
  }
}

The SDK provides a default implementation for Connector discovery using Java ServiceLoader with the connector-runtime-core module.

To make your Connector discoverable, expose the OutboundConnectorFunction or InboundConnectorExecutable implementation as an SPI implementation. Alternatively, you can use the manual discovery mechanism via properties.

If you want to validate your Connector input, the SDK provides a default implementation using Jakarta Bean Validation with the connector-validation module. You can include it via maven with the following dependency:

<dependency>
  <groupId>io.camunda.connector</groupId>
  <artifactId>connector-validation</artifactId>
  <version>${version.connectors}</version>
  <scope>provided</scope>
</dependency>

Set the dependency to a provided scope as the runtimes that execute Connectors provide the necessary classes already.

Find more details in the validation module.

Connector runtime supports running outbound Connectors as job workers and manages the lifecycle of the inbound Connectors. You can also build your own runtime, tailored towards your environment. For more details, refer to the connector-runtime module.

mvn clean package

1. For minor releases (x.y.0), create a new branch release/x.y from main in advance and rebase it onto main from time to time. This can be done using the CREATE_RELEASE_BRANCH workflow.
2. To trigger the release, publish a new GitHub release and name the tag according to the version you want to release (e.g. 1.0.0). This will trigger a GitHub workflow that builds and publishes the release artifacts, generates a changelog and bundles the element templates into an archive.

We use [backport-action](https://github.com/korthout/backport-action) to backport PRs to older releases. For example, add a label backport release/8.3 to backport a PR to the release/8.3 branch. This will take effect when the PR is meged.

You can also trigger this for already merged PRs by posting a comment on the PR containing /backport.