> For the complete documentation index, see [llms.txt](https://docs.rewst.help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rewst.help/documentation/automations/subworkflows/prod-task-sentinelone-get-license-counts.md).

# \[PROD - TASK] SentinelOne: Get License Counts

This workflow acts as a critical building block by querying the SentinelOne platform to retrieve client site information, enabling MSPs to effectively track and manage endpoint security licenses across multiple clients. It delivers essential visibility into license distribution and utilization, which directly supports compliance management, client billing accuracy, and renewal planning for cybersecurity services. The workflow functions by connecting to the SentinelOne API, retrieving a comprehensive list of all managed client sites, and preparing this data for license count analysis in subsequent automation processes. MSPs managing multiple SentinelOne deployments can leverage this automation to eliminate manual license auditing processes, proactively identify licensing gaps, and generate accurate reports for both internal operations and client discussions.

This workflow contains 5 tasks.

### Inputs

This subworkflow has no inputs.

### Outputs

* **automation\_log**: Standardized Rewst automation log
* **sentinel\_counts**: List of SentinelOne companies and their counts.

### Key tasks

* **sentinel\_one\_list\_sites**: SentinelOne integration: List Sites
* **Begin**: Core integration: noop
* **build automation log**: Logging

### Jinja examples

#### Example 1

```jinja
{{ [ { "company": site.name, "count": site.activeLicenses, "sku": site.sku, "company_id": site.id |d } for site in CTX.all_sites ] }}
```


---

# 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.rewst.help/documentation/automations/subworkflows/prod-task-sentinelone-get-license-counts.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.