> For the complete documentation index, see [llms.txt](https://docs.airops.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.airops.com/actions/workflow-concepts/workflow-steps/content-processing/group-keywords-into-clusters.md).

# Group Keywords into Clusters

The "Group Keywords into Clusters" step allows you to organize a list of keywords into meaningful, thematic clusters based on semantic similarity. This powerful tool helps you identify related keyword groups for content planning and optimization.

### How to Configure the Group Keywords into Clusters Step

* **Keywords**: List of keywords to be clustered as a JSON array (i.e. \["keyword a", "keyword b"]
* **Clustering Sensitivity**: Choose how sensitive you want the clustering logic to be:
  * Low = lower number of clusters (more coarse clustering)
  * High = higher number of clusters (more fine clustering)

### Output Format

The Group Keywords into Clusters step returns a JSON object containing the organized keyword clusters:

```json
[
 [
  "keyword 1",
  "keyword 2",
  "keyword 3",
  "keyword 4",
  "keyword 5",
  "keyword 6",
  "keyword 7"
 ],
 [
  "keyword 8",
  "keyword 9",
  "keyword 10",
  "keyword 11",
  "keyword 12",
  "keyword 13",
  "keyword 14"
 ],
 // Additional keyword clusters here
]
```


---

# 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.airops.com/actions/workflow-concepts/workflow-steps/content-processing/group-keywords-into-clusters.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.