Confluent
by @membranedev
Confluent integration. Manage data, records, and automate workflows. Use when the user wants to interact with Confluent data.
clawhub install confluentπ About This Skill
name: confluent description: | Confluent integration. Manage data, records, and automate workflows. Use when the user wants to interact with Confluent data. compatibility: Requires network access and a valid Membrane account (Free tier supported). license: MIT homepage: https://getmembrane.com repository: https://github.com/membranedev/application-skills metadata: author: membrane version: "1.0" categories: ""
Confluent
Official docs: https://docs.confluent.io/
Confluent Overview
Working with Confluent
This skill uses the Membrane CLI to interact with Confluent. Membrane handles authentication and credentials refresh automatically β so you can focus on the integration logic rather than auth plumbing.
Install the CLI
Install the Membrane CLI so you can run membrane from the terminal:
npm install -g @membranehq/cli@latest
Authentication
membrane login --tenant --clientName=
This will either open a browser for authentication or print an authorization URL to the console, depending on whether interactive mode is available.
Headless environments: The command will print an authorization URL. Ask the user to open it in a browser. When they see a code after completing login, finish with:
membrane login complete
Add --json to any command for machine-readable JSON output.
Agent Types : claude, openclaw, codex, warp, windsurf, etc. Those will be used to adjust tooling to be used best with your harness
Connecting to Confluent
Use membrane connection ensure to find or create a connection by app URL or domain:
membrane connection ensure "https://www.confluent.io/" --json
This is the fastest way to get a connection. The URL is normalized to a domain and matched against known apps. If no app is found, one is created and a connector is built automatically.
If the returned connection has state: "READY", skip to Step 2.
#### 1b. Wait for the connection to be ready
If the connection is in BUILDING state, poll until it's ready:
npx @membranehq/cli connection get --wait --json
The --wait flag long-polls (up to --timeout seconds, default 30) until the state changes. Keep polling until state is no longer BUILDING.
The resulting state tells you what to do next:
READY β connection is fully set up. Skip to Step 2.CLIENT_ACTION_REQUIRED β the user or agent needs to do something. The clientAction object describes the required action:clientAction.type β the kind of action needed:
- "connect" β user needs to authenticate (OAuth, API key, etc.). This covers initial authentication and re-authentication for disconnected connections.
- "provide-input" β more information is needed (e.g. which app to connect to).
- clientAction.description β human-readable explanation of what's needed.
- clientAction.uiUrl (optional) β URL to a pre-built UI where the user can complete the action. Show this to the user when present.
- clientAction.agentInstructions (optional) β instructions for the AI agent on how to proceed programmatically. After the user completes the action (e.g. authenticates in the browser), poll again with membrane connection get to check if the state moved to READY.
CONFIGURATION_ERROR or SETUP_FAILED β something went wrong. Check the error field for details.Searching for actions
Search using a natural language description of what you want to do:
membrane action list --connectionId=CONNECTION_ID --intent "QUERY" --limit 10 --json
You should always search for actions in the context of a specific connection.
Each result includes id, name, description, inputSchema (what parameters the action accepts), and outputSchema (what it returns).
Popular actions
| Name | Key | Description | |---|---|---| | List Topics | list-topics | Return the list of topics that belong to the specified Kafka cluster. | | List Clusters | list-clusters | Return a list of known Kafka clusters. | | List Consumer Groups | list-consumer-groups | Return the list of consumer groups that belong to the specified Kafka cluster. | | List Brokers | list-brokers | Return the list of brokers that belong to the specified Kafka cluster. | | List Partitions | list-partitions | Return the list of partitions that belong to the specified topic. | | List ACLs | list-acls | Return a list of ACLs (Access Control Lists) for the specified Kafka cluster. | | Get Topic | get-topic | Return the topic with the given topic_name from the specified Kafka cluster. | | Get Cluster | get-cluster | Return the Kafka cluster with the specified cluster_id. | | Get Consumer Group | get-consumer-group | Return the consumer group specified by the consumer_group_id. | | Get Broker | get-broker | Return the broker with the given broker_id for the specified Kafka cluster. | | Get Partition | get-partition | Return the partition with the given partition_id for the specified topic. | | Create Topic | create-topic | Create a topic in the specified Kafka cluster. | | Create ACL | create-acl | Create an ACL (Access Control List) for the specified Kafka cluster. | | Update Topic Config | update-topic-config | Update a single configuration parameter for the specified topic. | | Delete Topic | delete-topic | Delete the topic with the given topic_name from the specified Kafka cluster. | | Delete ACLs | delete-acls | Delete ACLs (Access Control Lists) that match the specified criteria for the given Kafka cluster. | | Produce Record | produce-record | Produce a record to the given topic. | | List Topic Configs | list-topic-configs | Return the list of configuration parameters that belong to the specified topic. | | Update Topic Partition Count | update-topic-partition-count | Update the number of partitions for a topic in the specified Kafka cluster. | | List Partition Offsets | list-partition-offsets | Return the offsets for a specific partition of a topic, including earliest and latest offsets. |
Running actions
membrane action run --connectionId=CONNECTION_ID --json
To pass JSON parameters:
membrane action run --connectionId=CONNECTION_ID --input '{"key": "value"}' --json
The result is in the output field of the response.
Proxy requests
When the available actions don't cover your use case, you can send requests directly to the Confluent API through Membrane's proxy. Membrane automatically appends the base URL to the path you provide and injects the correct authentication headers β including transparent credential refresh if they expire.
membrane request CONNECTION_ID /path/to/endpoint
Common options:
| Flag | Description |
|------|-------------|
| -X, --method | HTTP method (GET, POST, PUT, PATCH, DELETE). Defaults to GET |
| -H, --header | Add a request header (repeatable), e.g. -H "Accept: application/json" |
| -d, --data | Request body (string) |
| --json | Shorthand to send a JSON body and set Content-Type: application/json |
| --rawData | Send the body as-is without any processing |
| --query | Query-string parameter (repeatable), e.g. --query "limit=10" |
| --pathParam | Path parameter (repeatable), e.g. --pathParam "id=123" |
Best practices
membrane action list --intent=QUERY (replace QUERY with your intent) to find existing actions before writing custom API calls. Pre-built actions handle pagination, field mapping, and edge cases that raw API calls miss.π Tips & Best Practices
membrane action list --intent=QUERY (replace QUERY with your intent) to find existing actions before writing custom API calls. Pre-built actions handle pagination, field mapping, and edge cases that raw API calls miss.