Utilities plugin

Alibaba Wan

Alibaba Model Studio Wan async video generation provider.

1 listed action1 capability groups

Connection facts

What the Alibaba Wan connector actually exposes.

These details come from the current StackOS provider manifest and action catalog. They describe the available connection—not a promise that every workflow will use every action.

Connection method
api-key
Setup
Register for Alibaba Cloud, enable Model Studio/DashScope, create API credentials, confirm billing, and store the key in StackOS.
Capability groups
Video Generation
Action boundaries
1 cost-bearing action

Action catalog

Actions listed for Alibaba Wan.

Actions listed for this integration. Individual descriptions note availability limits. A workflow still decides which actions belong in the job and where approval is required.

1 matching action

Video GenerationUses a paid service

Generate Alibaba Wan Video

Generate and persist Wan videos through Alibaba Model Studio from text, provider-fetchable images, or provider-fetchable video clips.

Direct answer

How does the Alibaba Wan integration work?

People continue using Alibaba Wan as their tool. StackOS adds it to a visible workflow, keeps the work in order, and passes only the approved action to the integration when that stage is ready.

  1. 01Your requestStart in your AI
  2. 02StackOS planExpands the steps
  3. 03Alibaba WanDoes its bounded part
  4. 04Checked resultKeeps the proof

Common questions

Alibaba Wan and StackOS.

What can the Alibaba Wan integration do in StackOS?

The current catalog includes 1 Alibaba Wan action across Video Generation. The exact actions used depend on the workflow and approval rules.

Does StackOS replace Alibaba Wan?

No. Alibaba Wan remains the tool that performs its part of the job. StackOS organizes the workflow, keeps status and dependencies visible, and calls the tool only when the plan reaches the right approved action.