Does Camunda 8 SAAS version supports custom connector SDK so that we can create custom conector through code? Or it supports only using templates through UI?
Hi there and welcome to the Camunda forum!
Yes, we do have a Connector SDK you can use to create custom connectors with Java. This is supported in both SaaS and self-managed deployments.
I’d also recommend browsing the connectors on our Marketplace for connectors built by Camunda, partners, and community members.
Thanks, How can I create a connector using a connector SDK and use it in my SAAS version? Is there a import connector feature? I am aware of creating connector using templates in cloud, but I want to create a custom connector using SDK and use it in the cloud SAAS version.
Gotcha, there’s not an import feature, but the instructions are largely the same for both SaaS and self-managed.
To add your connector to SaaS, you follow the instructions in this section of the docs. You have to provide the runtime environment (Docker, Spring Boot, etc.) and make sure your custom Connector is registered to it. Make sure that you are using the SaaS Zeebe endpoint.
1 Like
Hey there, just to add more context here, you will need to run your own instance of the Connector runtime and connect it to your SaaS cluster. As Mia mentioned, it’s mostly similar to just running a self-managed Connector runtime, you can find more specific instructions for your use case here.
That article also covers overriding the connector type property - you don’t need this if you are developing your own connector and not trying to run an out-of-the-box connector in hybrid mode. But you can make use of the configuration examples from the article to connect to a SaaS cluster.
2 Likes
Thanks for the response. If I need to run my own connector instance, what is the difference between job worker and connector? I believe job worker also works the same - means we have to host the jobworker our own and connect it to SAAS.
From the perspective of the engine, outbound Connectors and job workers are the same thing.
With an outbound Connector, you get to use the Connector SDK and the pre-built Connector runtime, which may make some things easier for you by providing access to secrets, uniform response mapping and so on, while you only focus on the business logic.
Inbound Connectors are different - for them the Connector SDK also offers lifecycle management bound to process deployment events. But you can still implement your inbound event listener by just calling the Zeebe API directly and not using the Connector SDK if you wish.
2 Likes
Thanks.
So one more question - Does both custom Connector and job worker needs Zeebe client to work?
Correct, both approaches use the Zeebe client to complete jobs - but in the Connector SDK it is hidden behind higher-level abstractions 
2 Likes
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.