> For the complete documentation index, see [llms.txt](https://docs.appfarm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appfarm.io/library/action-nodes/set-client-language.md).

# Set client language

The Set client language action node changes the language used by an app, instantly altering the text and formatting of dates, numbers and currency. To set a language, it must be first added under [Internationalization](https://docs.appfarm.io/reference/resources/internationalization.md).

{% hint style="info" %}
Showroom: [Set client language example](https://showroom.appfarm.app/action-nodes/set-client-language), with its setup in Appfarm Create ([register](https://showroom.appfarm.app/sign-up) for access).
{% endhint %}

## Usage

This action node is typically used to allow a user to set a language preference for your app(s). It is possible to store a language as an object class property, for example as part of an object attached to a user, and enable that language using Set client language.

For a step-by-step guide to adding a language switcher to an app, see[ Change the active language](https://docs.appfarm.io/how-to/enhance-your-app/change-the-active-language.md).

## Properties

<table><thead><tr><th width="269">Property</th><th>Description</th></tr></thead><tbody><tr><td><strong>Language</strong></td><td>The language to switch to. Select a language from the list of languages added to the solution, or click the menu next to the property and select <strong>Data binding</strong> to set the language dynamically using a <a href="https://docs.appfarm.io/reference/platform-concepts/data-bindings.md">data binding</a>. A data-bound value must be a language added under Internationalization. If it is empty, the node fails with "Could not find language id to set." Picking the default language resets the app to the default language and formats.</td></tr></tbody></table>


---

# 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.appfarm.io/library/action-nodes/set-client-language.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.
