When to build one, and how to ship it

A custom connector is worth building when the value is real and the alternative is a manual seam. Key points:

• Reach for the built-in library first. IntegraCI ships a broad connector library across CI/CD, security, cloud, and observability. If your tool is already covered, connect your account and move on.
• Build a custom connector when your tool is not in the library, it is a home-grown internal system, or you need behaviour the generic path doesn't cover. The test is whether bringing the tool under the control plane removes a manual seam where results go dark or actions get skipped.
• Build, test, register. Implement the SDK contract for your tool, test it against the tool's API (or a recorded fixture) so the read and dispatch paths behave, then register it so the platform discovers it and surfaces it in the marketplace alongside the built-in connectors. Once registered, your tool reads results and dispatches actions under the same governance, audit, and isolation as everything else.