> 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-languages.md).

# Get Languages

## Description

Available in v8.2+, the *get\_languages* part allows you to call and create a collection of languages that you configured in the project settings for your project.

## Use

When you use the *get\_languages* part to create a collection from the languages configured in the project, you can use the collection in your application; for example, to display the language choices in a radio part. This could allow your users to select their preferred language, assuming you have done the following:

1. enabled translations in the project settings
2. created the translation texts (either manually or via the export/import feature)

For more information on using translations with your application, see the [Multi-Language Support](/release-9/platform-documentation/multi-language-and-text-tagging-support.md) section.

## Editor Fields

| Field Name                  | Description/Use                                                            | Type/Options | Optional/Mandatory |
| --------------------------- | -------------------------------------------------------------------------- | ------------ | ------------------ |
| language\_codes\_collection | This is the name of the data object in which the system stores the result. | Text         | Mandatory          |

## Example

Follow this article to receive updates, including when an example project becomes available.


---

# 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-languages.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.