← Docs

Docs · Connector reference

Alibaba Qwen (DashScope) connector reference

Operations, inputs, troubleshooting, and questions for the Alibaba Qwen (DashScope) connection. Policy decides each change before the credential is resolved, and the action record carries the result.

Set up and verify the Alibaba Qwen (DashScope) connection

  1. Choose one task and its account, and match the reads and actions on the overview page to it before granting provider permissions.
  2. Prepare the connection settings from the overview page, connect the provider in Deixic, and choose which tools your agent can use.
  3. Try a small task with a known result, and compare the returned identity and resource with what the account owner expects.
  4. Configure approval for sensitive changes, review the destination and inputs, and check the result in the provider before expanding the workflow.

Information your agent can use

ResourceRecord identityStart withPage coverage
Model catalogmodelTop levelPage number
FilesidTop levelNone configured
BatchesidTop levelNone configured
BatchidBatchesNone configured
Record identity
Match on these fields before joining or deduplicating results; where none is specified, check the returned record first.
Start with
Resolve the parent identifier first.
Page number
Page-number pagination. Keep filters and ordering consistent while checking successive pages.
None configured
No page continuation is configured for this resource. Check the response and any provider limits before treating it as a complete inventory.

Supported operations

Review the inputs before granting an action to an agent. Required inputs must be supplied, optional inputs narrow the request, and provider permissions apply in addition to Deixic policy.

Read
Retrieves information; check the returned scope and identifiers before use.
Action
Can change provider state; review the target and inputs, then retain the result to avoid repeating completed work.
OperationEffectApprovalProvider permissionsInputs
Chat CompletionsReadBy policymodels.invoke9
Files DeleteActionApproval requiredfiles.write1
Batches CreateActionApproval requiredbatch_jobs.write4
Batches CancelActionApproval requiredbatch_jobs.write1

Inputs by operation

Chat Completions Read
Inputs for Qwen Chat Completions
InputRequirementAccepted value
enable_searchOptionalboolean
enable_thinkingOptionalboolean
max_tokensOptionalintegerMinimum: 1Maximum: 32768
messagesRequiredarrayMinimum items: 1Maximum items: 128
modelRequiredstringMinimum characters: 1Maximum characters: 256
streamOptionalvalue
temperatureOptionalnumberMinimum: 0Maximum: 2
thinking_budgetOptionalintegerMinimum: 1Maximum: 32768
top_pOptionalnumberMaximum: 1
Files Delete Action · approval required
Inputs for Qwen Files Delete
InputRequirementAccepted value
file_idRequiredstring
Batches Create Action · approval required
Inputs for Qwen Batches Create
InputRequirementAccepted value
completion_windowRequiredvalue
endpointRequiredstring; one of: /v1/chat/completions, /v1/chat/ds-test, /v1/embeddings
input_file_idRequiredstringMinimum characters: 1Maximum characters: 1024
metadataOptionalobject
Batches Cancel Action · approval required
Inputs for Qwen Batches Cancel
InputRequirementAccepted value
batch_idRequiredstring

When the Alibaba Qwen (DashScope) task does not produce the expected result

Connected, but the expected data is missing

Check the identity behind the bearer token connection and its access to the specific resource; a successful connection does not establish access to every object.

Resolve parent resources first: Batches. A matching display name is not enough for a child lookup.

The answer covers only part of the data

Check the resource’s page coverage, query filters, and result limit, and have the agent state the account and time window it inspected, so a partial response yields a scoped answer.

The agent keeps doing the same work

Inspect the action history for repeated targets and inputs, keep the successful result’s identifiers with the task, and refresh a lookup only when the information changed.

A change is waiting or failed

Check whether the call awaits approval, was rejected by policy, lacks an input, or failed at the provider, and after a timeout inspect the destination before repeating a write.

See how an action proceeds and how to review an approval.

Questions about the Alibaba Qwen (DashScope) connector

Can I use my existing agent with Alibaba Qwen (DashScope)?

Yes: connect your agent to Deixic through MCP, choose which connected tools it can use, and Deixic checks calls routed through its gateway; Dex is available if your team also wants an agent.

Can an agent change data in Alibaba Qwen (DashScope)?

This connector supports 2 actions, listed on its overview page. Configure a connection and choose the tools and provider permissions your task needs; an available action is not permission for every agent to run it, and Deixic policy and any required approval still apply to calls through the gateway.

What do I need to connect Alibaba Qwen (DashScope)?

Prepare API key; the connection uses Bearer token, and the connected identity’s provider permissions determine which resources it can access.

Does connecting Alibaba Qwen (DashScope) keep every answer up to date?

No: an earlier answer is still an earlier answer, so for a decision that depends on current state, have the agent refresh the source and retain the lookup time, and save stable instructions separately from facts that can change.