How does OCNORA authenticate with Apache Kafka?

With a stored API key credential, shaped blank, or {"username", "password"} for the REST Proxy. A connection test can check it when you add it.

What can I automate with Apache Kafka?

2 typed operations, each with a reference page listing its config fields and the shapes it emits.

What if the Apache Kafka operation I need is not listed?

Where Apache Kafka has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.

Are there templates that use Apache Kafka?

Not yet. Start from a blank workflow, or describe the workflow to Build with AI.

How are Apache Kafka calls controlled?

Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.

Apache Kafka

Chat & messagingAPI keyConnection test available

Apache Kafka via the Confluent REST Proxy (produce / list topics).

OCNORA ships 2 typed Apache Kafka operations. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run.

Ask about Apache Kafka

Before you connect Apache Kafka

Authentication: API key
Credential: blank, or {"username", "password"} for the REST Proxy
Connection test: Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.

What you can do with Apache Kafka

Operations, grouped by what they do to your data.

Read and search 1

List Topics

Other operations 1

Produce

A sample Apache Kafka workflow

1
A core trigger
Start the run from a chat, form, manual, schedule, webhook, workflow trigger — no Apache Kafka trigger is needed.
2
List Topicskafka.list_topics
List topics available via the Kafka REST Proxy.
3
Producekafka.produce
Produce a JSON record to a Kafka topic via the Confluent REST Proxy.

An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.

Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.

Operations 2

Apache Kafka questions

How does OCNORA authenticate with Apache Kafka?: With a stored API key credential, shaped blank, or {"username", "password"} for the REST Proxy. A connection test can check it when you add it.
What can I automate with Apache Kafka?: 2 typed operations, each with a reference page listing its config fields and the shapes it emits.
What if the Apache Kafka operation I need is not listed?: Where Apache Kafka has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
Are there templates that use Apache Kafka?: Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
How are Apache Kafka calls controlled?: Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.

See your first Apache Kafka workflow run.

Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.

Book a technical demo Talk to sales