Integrations
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
The Duaer Qwen Cloud credential uses an API key from Alibaba Cloud Model Studio:
- Sign in to the Model Studio international console, switch to the Singapore region, and create a key on the API Key page.
- In Duaer, create a Qwen Cloud credential and paste the key into API Key.
- 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
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, Qwen Cloud Chat Model.
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.
In this section
Built-in integrations in Duaer
Built-in triggers, actions, and credentials in Duaer. Triggers start a workflow. Actions run a step after it has started.
IntegrationsRisks of community nodes in Duaer
Before you install a community node in Duaer, know the code comes from a source the instance admin trusts, and know what permissions it gets.
IntegrationsTroubleshoot community nodes in Duaer
When a Duaer community node will not install or run, check the version, permissions, and node docs, then the instance logs.
IntegrationsMake custom API calls for an app in Duaer
When a Duaer app node does not expose the API you need, use HTTP Request and reuse that app’s saved authentication.
IntegrationsIntegrations in Duaer
Built-in triggers, actions, and credentials in Duaer. Community nodes are extra packages. Custom operations reuse saved authentication with HTTP Request.
CredentialsBuilt-in credentials in Duaer
Per-service credential notes for Duaer built-ins. The create flow is in the credentials overview; node docs link to the matching service page.
Create nodesCreate a custom node for Duaer
Write a node package for Duaer when built-in nodes and custom operations are not enough and you will reuse the step.