Use Jira Automation with Confluent Kafka

Use these actions to manage Kafka topics and cluster metadata in Confluent Cloud from Jira Service Management Automation rules.

Actions

Create Confluent Kafka topic

Create a new Kafka topic in a Confluent Cloud cluster. Use this to provision topics for new services or workflows.

Fields

• Cluster ID (required): Confluent Cloud cluster ID (for example, lkc-d6889o). This tells the action which cluster to use.

• Topic name (required): Name of the topic to create. Use a clear, consistent naming convention.

• Partitions (required): Number of partitions. Choose based on expected throughput and consumer parallelism.

• Replication factor (required): Replication factor for the topic. Higher values improve resilience but consume more resources.

Delete Confluent Kafka topic

Delete a Kafka topic from a Confluent Cloud cluster. Use this to clean up unused topics.

Fields

• Cluster ID (required): Cluster that contains the topic.

• Topic name (required): Topic to delete. Ensure the data is no longer needed.

Get Confluent Kafka topic

Retrieve metadata for a Kafka topic, including configuration and partition details.

Fields

• Cluster ID (required): Cluster that contains the topic.

• Topic name (required): Topic to look up.

List Confluent Kafka topics

List all Kafka topics in a Confluent Cloud cluster.

Fields

• Cluster ID (required): Cluster to list topics from.

Get Confluent Kafka partitions (all partitions)

Get all partitions for a Kafka topic. Useful for capacity planning and consumer parallelism.

Fields

• Cluster ID (required): Cluster that contains the topic.

• Topic name (required): Topic to inspect.

Get Confluent Kafka partition (specific partition)

Retrieve metadata for a specific Kafka partition, including leader and replica details.

Fields

• Cluster ID (required): Cluster that contains the topic.

• Topic name (required): Topic that owns the partition.

• Partition ID (required): ID of the partition to inspect.

Update Confluent Kafka partitions

Increase the partition count for a Kafka topic. Use this to scale throughput.

Constraints

• Partition count can only be increased, not decreased.

• Changing partitions may trigger consumer rebalancing and affect ordering guarantees.

Fields

• Cluster ID (required): Cluster that contains the topic.

• Topic name (required): Topic to update.

• Partitions (required): New total partition count. Must be greater than the current count.

List Confluent Kafka brokers

List all broker IDs in a Confluent Cloud cluster.

Fields

• Cluster ID (required): Cluster to inspect.