> 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/rewst-master-v2-psa-datto-list-members.md).

# \[Rewst Master v2] PSA-Datto: List Members

This workflow queries and retrieves a comprehensive list of members (technicians and resources) from Datto Autotask PSA, serving as a critical building block for workflows that need to identify available staff, assign responsibilities, or generate reports. MSPs would find this function valuable for automated ticket routing based on technician availability, staff utilization reporting, and as an essential component in onboarding/offboarding automation sequences. Technically, the workflow executes a simple but powerful resources\_query action against the Datto PSA API, retrieving member data that can be filtered and utilized by parent workflows for decision-making processes. This reusable component eliminates the need to repeatedly code PSA member queries across multiple automations, providing standardized access to resource information throughout your automation ecosystem.

This workflow contains 1 task.

### Inputs

* **choose\_variable** - string

### Outputs

* **options**: Array of member objects.

### Key tasks

* **list\_members**: Datto Autotask PSA integration: resources\_query

### Jinja example

```jinja
{{ [{"id": resources.id, "label": resources.firstName~" "~resources.lastName, "default": true if resources.id == ORG.VARIABLES[CTX.choose_variable]|d|int else false} for resources in TASKS.list_members.result.result if (resources.isActive == true) and (resources.userType != 13) ] }}
```

This is used in publishing the members data alias.


---

# 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/rewst-master-v2-psa-datto-list-members.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.