Connector library

Implemented source APIs, Messaging & Protocols

Kafka connector.

Read cluster, topic and consumer-group references through six named Standalone Kafka REST Proxy v3 GET actions using managed Basic authentication.

Connector download

Download Kafka

Versioned ZIP for your CXFabric tenant.

Use this connector in a flow

  1. Register the ZIP in your tenant, or add a new version if the connector is already installed.
  2. Create or select a credential if the action requires one.
  3. In a Draft flow, add an available action, choose its version, connect it, and map inputs.
  4. Test the step and flow; review output and failures before activation.

See readme.md in the ZIP for settings and limitations.

Version
v0.2.0.0 Choose version
Release
2026-10-04
Package
Implemented source
Schema credentials
Basic auth
Connection settings
API Base URL
Package size
11 KB
SHA-256
19b205c251d3ca68ad6b884aabf225ce2faf2ef3bf83d084c373475c297987d9

Version history

What's new

  1. v0.2.0.0Latest · 2026-10-04 · Implemented source

    Read cluster references, selected topic metadata and consumer-group state labels through six named standalone Kafka REST Proxy v3 HTTPS actions with managed Basic credentials and bounded, scope-checked results.

  2. v0.1.1.0Earlier · 2026-10-02 · Starter scaffold

    Historical configurable HTTP scaffold, retained unchanged.

Included in this version

Included actions

Implemented in v0.2.0.0. Use a separate flow trigger; no webhook trigger is included.

List clusters

Read selected IDs of clusters known to this configured REST Proxy.

Get cluster

Read one exact cluster reference and verify its native identity.

List topics

Read one native response of selected topic configuration metadata in exact cluster scope.

Get topic

Read exact topic identity, internal flag, partition count and replication factor.

List consumer groups

Read one native response of selected consumer-group state and assignor metadata in exact cluster scope.

Get consumer group

Read exact consumer-group identity, state label, simple flag and partition assignor.

Vendor API

API and access

Implementation considerations
  • Configure an approved standalone HTTPS DNS origin, optional port and exact /v3 path. Store issued username/password in managed basicAuth; requests use native HTTP Basic Authorization. Broker authentication and read ACLs remain external.
  • This package excludes direct brokers, Confluent Server/Cloud /kafka/v3 paths, other authentication modes, records, mutations, consumer membership and lag calculations.
  • Cluster listing describes the configured proxy's native response rather than organization-wide inventory. Exact IDs and requested topic/group scope are checked in declared local ASCII subsets without case normalization.
  • Maximum Items is a local row cap from 1–1000, not a vendor page-size query. Present next metadata supplies only hasMore without following or returning its URL; absent next stays absent. There is no automatic paging, completeness inference or stable-snapshot guarantee. Null arrays fail; excessive or duplicate rows fail without truncation.
  • False flags and empty assignors are preserved. Native state labels remain extensible uppercase tokens; configuration counts and state labels do not establish replica availability, consumer activity or cluster health.
  • Strict JSON/media/UTF-8, a 1 MiB response cap, normal TLS trust and a shared 1–8 second budget fail without redirects, proxies or replay. Hosted import, executor dependencies and live deployment/Basic-auth/broker-ACL behavior remain untested.
  • Six packaged reference reads target standalone Kafka REST Proxy v3 over HTTPS with managed HTTP Basic credentials. The native OpenAPI and standalone security guide ground paths and authentication; hosted dependencies and live proxy/ACL behavior need validation.

Support

Need help with Kafka?

Tell us what you need to connect or change.