StackOSWork, organized
LibraryWorkflowsAgentsOrchestratorsIntegrationsArticles

Kling AI text-to-video and image-to-video provider.

1 listed action1 capability groups

Connection facts

What the Kling AI 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
jwt-access-key
Setup
Use the official Kling AI/API console and documentation to obtain access keys, then store both AccessKey and SecretKey in StackOS.
Capability groups
Video Generation
Action boundaries
1 cost-bearing action

Action catalog

Actions listed for Kling AI.

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 Kling Video

Generate and persist Kling videos from text, one input image, or first and last frame images.

Direct answer

How does the Kling AI integration work?

People continue using Kling AI 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. 03Kling AIDoes its bounded part
  4. 04Checked resultKeeps the proof

More from Utilities

Related integrations.

See the plugin →

Common questions

Kling AI and StackOS.

What can the Kling AI integration do in StackOS?

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

Does StackOS replace Kling AI?

No. Kling AI 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.