> For the complete documentation index, see [llms.txt](https://doc.duaer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.duaer.com/integrations/builtin/credentials/alibaba.md).

# Set up Qwen Cloud credentials in Duaer

Store Qwen Cloud connection details in Duaer for digital-organization nodes to use at runtime. Secrets are protected by the instance encryption key and are not written into node parameters.
## Get a Qwen Cloud API key <a href="#get-an-api-key" id="get-an-api-key"></a>

The Duaer Qwen Cloud credential uses an API key from Alibaba Cloud Model Studio:

1. Sign in to the [Model Studio international console](https://modelstudio.console.alibabacloud.com/), switch to the Singapore region, and create a key on the API Key page.
2. In Duaer, create a Qwen Cloud credential and paste the key into API Key.
3. Keep Region at the default Singapore (International). The credential dialog says only that region is supported for now.

Model Studio keys are issued per region. A key from the Beijing region does not work in Singapore, and the other way round.

## Qwen Cloud fields in Duaer <a href="#qwen-cloud" id="qwen-cloud"></a>

In Duaer, choose Qwen Cloud when you create a credential, then fill in these fields:

- API Key (required, secret)
- Region: The region for the Qwen Cloud API endpoint. Currently only Singapore is supported - other regions are only available through Alibaba Cloud Model Studio. Default: Singapore (International). Options: Singapore (International), US (Virginia), China (Beijing), Hong Kong (China), Germany (Frankfurt).
- Workspace ID (required): The Workspace ID required for the Germany (Frankfurt) region. Not yet supported for Qwen Cloud. Find it in the Alibaba Cloud Model Studio console under the Germany region settings. Shown when Region is Germany (Frankfurt).

When you save, Duaer tests the connection with these values.

Duaer nodes that use it: [Qwen Cloud](/integrations/builtin/app-nodes/n8n-nodes-langchain.alibabacloud.md), [Qwen Cloud Chat Model](/integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.lmchatalibabacloud.md).

## Save the connection in Duaer

Open Credentials and create Qwen Cloud. Fill in the key, OAuth, or server fields. After you save, digital-organization nodes reference this credential instead of putting the secret in a parameter.

Credential values are protected by the instance encryption key. If you change or lose that key, stored credentials cannot be decrypted. See the hosting notes on encryption keys. 

## Who can use this credential

Who can see or edit it follows projects and roles. Do not paste secrets into chat or variables. External vaults are covered under external secrets.
## Questions

### Do Qwen Cloud secret values appear in Duaer node parameters?

No. In Duaer, Qwen Cloud secrets stay in the credential. Nodes only reference the credential. Execution records should not show the plaintext secret either.

### What usually stops a Qwen Cloud credential from saving in Duaer?

Wrong fields, an OAuth callback that does not match the instance URL, or a role that cannot create credentials. Check the fields Qwen Cloud expects, then confirm you can create credentials in that project.

