> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/process-node-parts/get-resources-from-token-beta.md).

# Get Resources from Token (BETA)

## Description

Each LogicNets part has a write cycle that renders the part to the display. The Get Resources from Token part gets the resources of all parts that were written to the screen in the last write cycle. With this information it determines if the resource is attached to a topic in the Knowledge Center. If the resource is attached to a topic in the Knowledge Center, the system saves the resources to the result collection. With this part, you can retrieve resources from another token; for example, you could use Token 4 to display the Knowledge Center topics that the system rendered in Token 3.

Note: This part is currently in Beta phase.

**Node Type:** This part is in process nodes.

**Used With:** This part can be used with all frameworks.

## Editor Fields

| Tab   | Field Name        | Description/Use                                                                                                             | Type/Options | Optional/Mandatory |
| ----- | ----------------- | --------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------------ |
| Basic | Result collection | This is the name of the variable in which the system saves the resources.                                                   | Collection   | Mandatory          |
| Basic | Token id          | This is the id of the token from which you get the resources. If this field is empty the system uses the standard ai token. | Number       | Optional           |


---

# 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://community-test.logicnets.com/release-9/platform-documentation/process-node-parts/get-resources-from-token-beta.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.