> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/integrations/catalog/confluent.md).

# Confluent

Manage Kafka topics and connectors, and produce records with Confluent Cloud.

### Connectors

Choose the connector that matches your authentication method. The options below use the names shown in StackAI.

| Connector       | Authentication   |
| --------------- | ---------------- |
| Confluent Cloud | API key or token |

#### Confluent Cloud

Connect to Confluent Cloud to manage Kafka topics, records, and managed connectors.

**Set up in Confluent**

1. Prepare the Confluent account or service that the workflow will access. Grant access to the required resources and operations.
2. **Kafka REST Endpoint:** HTTPS REST endpoint shown on the Kafka cluster settings page, for example <https://pkc-example.us-central1.gcp.confluent.cloud:443>.

**Set up in StackAI**

1. Open **Settings → Connections**, add a connection, and select **Confluent Cloud**.
2. Enter the credentials and connection details in the fields below.
3. Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it.

**Connection fields**

| StackAI field       | Required | What to enter                                                                                                                                                                            |
| ------------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Cloud API Key       | Yes      | Cloud API key used to authenticate to the Confluent Connect API. [Provider instructions](https://docs.confluent.io/cloud/current/access-management/authenticate/api-keys/api-keys.html). |
| Cloud API Secret    | Yes      | Secret paired with the Cloud API key. [Provider instructions](https://docs.confluent.io/cloud/current/access-management/authenticate/api-keys/api-keys.html).                            |
| Kafka API Key       | Yes      | Resource-scoped API key for the selected Kafka cluster. [Provider instructions](https://docs.confluent.io/cloud/current/access-management/authenticate/api-keys/api-keys.html).          |
| Kafka API Secret    | Yes      | Secret paired with the Kafka resource API key. [Provider instructions](https://docs.confluent.io/cloud/current/access-management/authenticate/api-keys/api-keys.html).                   |
| Environment ID      | Yes      | Confluent Cloud environment ID, for example env-abc123.                                                                                                                                  |
| Kafka Cluster ID    | Yes      | Confluent Cloud Kafka cluster ID, for example lkc-abc123.                                                                                                                                |
| Kafka REST Endpoint | Yes      | HTTPS REST endpoint shown on the Kafka cluster settings page, for example <https://pkc-example.us-central1.gcp.confluent.cloud:443>.                                                     |

#### Verify the connection

Check that the connection is healthy. Then run a read operation against a resource the connected account can access. A successful connection check confirms authentication; it does not guarantee permission for every action.

If access is denied, check the credential or OAuth permissions, the selected account or environment, and access to the specific resource. Update expired credentials or reconnect after permissions change.

### Use an action

1. Add the required **Confluent** action to the workflow.
2. Select a connection when the action requests one.
3. Complete the required fields. Use the reference picker when a value comes from another workflow step.
4. Run the workflow and inspect the action’s output. Check the result before using it in a later step.

### Actions

#### Produce Record to Topic

Produce one record to a Kafka topic.

**Inputs**

| Field        | Type            | Required | Description                                                                                         |
| ------------ | --------------- | -------- | --------------------------------------------------------------------------------------------------- |
| Topic Name   | string          | Yes      | Kafka topic that receives the record.                                                               |
| Record Value | object          | Yes      | Record value to publish.                                                                            |
| Value Type   | select (string) | No       | Encoding used for the record value. Available values: JSON, String, Binary (base64). Default: JSON. |
| Record Key   | string          | No       | Optional key used for partitioning and compaction.                                                  |
| Partition ID | integer         | No       | Optional partition to receive the record.                                                           |

**Outputs**

| Field          | Type   | Description                                        |
| -------------- | ------ | -------------------------------------------------- |
| Produce Result | object | Confluent acknowledgement for the produced record. |
| Topic Name     | string | Topic that received the record.                    |

#### List Topics

List Kafka topics in a Confluent Cloud cluster.

**Inputs**

No input fields are required in this catalog entry.

**Outputs**

| Field       | Type   | Description                             |
| ----------- | ------ | --------------------------------------- |
| Topics      | array  | Kafka topics in the configured cluster. |
| Topic Count | number | Number of topics returned.              |

#### Create Topic

Create a Kafka topic in Confluent Cloud.

**Inputs**

| Field              | Type    | Required | Description                                        |
| ------------------ | ------- | -------- | -------------------------------------------------- |
| Topic Name         | string  | Yes      | Name of the Kafka topic to create.                 |
| Partitions         | integer | No       | Number of partitions for the topic. Default: 6.    |
| Replication Factor | integer | No       | Number of replicas for each partition. Default: 3. |

**Outputs**

| Field      | Type   | Description                |
| ---------- | ------ | -------------------------- |
| Topic      | object | The created Kafka topic.   |
| Topic Name | string | Name of the created topic. |

#### Create Connector

Create a connector in Confluent Cloud.

**Inputs**

| Field                   | Type   | Required | Description                                               |
| ----------------------- | ------ | -------- | --------------------------------------------------------- |
| Connector Name          | string | Yes      | Unique name for the connector.                            |
| Connector Configuration | secret | Yes      | Connector-specific configuration JSON. Values are masked. |

**Outputs**

| Field          | Type   | Description                                |
| -------------- | ------ | ------------------------------------------ |
| Connector      | object | The connector returned by Confluent Cloud. |
| Connector Name | string | Name of the created connector.             |

#### Get Connector Status

Get a connector's runtime status.

**Inputs**

| Field          | Type   | Required | Description                       |
| -------------- | ------ | -------- | --------------------------------- |
| Connector Name | string | Yes      | Name of the connector to inspect. |

**Outputs**

| Field            | Type   | Description                                |
| ---------------- | ------ | ------------------------------------------ |
| Connector Status | object | Current connector and task runtime states. |
| State            | string | Current top-level connector state.         |

### Important behavior

Actions that create, update, send, or delete data can change the connected service. Review their inputs before running them. A retry can repeat an operation; consider this when configuring retries for actions that change data.

The catalog lists the fields and capabilities available in the supplied provider definition. Availability can also depend on your deployment and organization’s Feature Access settings.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/integrations/catalog/confluent.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
