Integration · Data streaming
Apache Kafka + OrchestrAI
Catalog exported 2026-09-02 · Apache Kafka website
Manage Kafka topics, inspect consumer groups and offsets, and produce or consume messages from chat.
OrchestrAI exposes 10 Apache Kafka operations: 6 are low-risk (read-only or low-impact), and 4 create or modify resources and run only after you confirm the plan. 2 of them also carry a step-level approval gate.
What teams use it for
Streaming and backend teams use OrchestrAI to check consumer lag on a group, peek at recent messages on a topic while debugging, and reset offsets once a consumer is fixed. Listing, describing, and consuming are low risk, creating a topic and producing messages are medium and run on request, resetting consumer offsets waits for confirmation, and deleting a topic is high risk and confirmed. There is no operation for ACLs, quotas, partition reassignment, or altering topic configuration, so those stay with kafka-configs and your admin tooling.
Every Apache Kafka operation, with its risk level
| Operation | What it does | Risk | Step-level approval |
|---|---|---|---|
Describe Kafka Consumer Group |
Describe consumer group | Low risk | No |
Describe Kafka Topic |
Describe topic configuration | Low risk | No |
Get Kafka Offsets |
Get topic offsets | Low risk | No |
Kafka Consume |
Consume messages from a topic | Low risk | No |
List Kafka Consumer Groups |
List consumer groups | Low risk | No |
List Kafka Topics |
List all topics | Low risk | No |
Create Kafka Topic |
Create a topic | Creates resources | No |
Kafka Produce |
Produce messages to a topic | Creates resources | No |
Reset Kafka Consumer Offsets |
Reset consumer group offsets | Creates resources | Yes |
Delete Kafka Topic |
Delete a topic | Modifies existing | Yes |
Risk tiers come from the catalog: low is read-only or low-impact, medium creates resources and is reversible, high modifies existing resources, destructive may lose data. Every plan that creates or changes resources is shown with its cost estimate and waits for your confirmation. Operations marked with a step-level approval pause again on their own step. Destructive operations require a typed risk phrase.
What you connect
A Apache Kafka credential (stored as kafka).
Connected-service tokens are envelope-encrypted with a per-record key wrapped by a cloud KMS.
Prompts that work
- Describe the consumer group order-processor and show lag per partition on the orders topic
- Consume the last 20 messages from the payments.events topic
- Reset the offsets for consumer group email-sender on topic notifications to the earliest
Before anything runs
Every mutation shows its plan, cost estimate, and blast radius, then waits for your confirmation. Destructive operations require a typed risk phrase. Credentials are minted per run through OIDC federation and discarded afterward; nothing you create here is invisible later, because every resource lands in the desired-state ledger where drift is detected and can be converged. Details on the security page.
Frequently asked questions
- Can OrchestrAI delete a Kafka topic?
- Yes. Topic deletion is high risk because the data goes with it, so OrchestrAI shows the topic name and partition count and waits for confirmation.
- Does resetting Kafka consumer offsets through OrchestrAI need approval?
- Yes. Offset reset is medium risk and marked for confirmation, since it changes where the consumer group resumes reading.
- How does OrchestrAI authenticate to Apache Kafka?
- You add a Apache Kafka credential once in the connections screen. It is envelope-encrypted with a per-record key wrapped by a cloud KMS and is only decrypted inside the run that needs it.
Related integrations
Cloud services this pairs with
Try it on your own account
Connect your cloud read-only and see your resources, drift, and costs before anything runs. $5 minimum to start. Unused credits refunded in your first 14 days.
Unused credits refunded in your first 14 days.