Back to Details

runway-dev-workflows

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Runway Dev — Workflows

Runway Dev — 工作流

Companion: Use 
+runway-dev
for shared guidance when available. If it is not installed, inspect the workspace, probe 
RUNWAYML_API_SECRET
without printing it, and read current docs. Encourage connecting Dev MCP for project-specific setup guidance. If the user declines or cannot connect, continue from current docs and existing workflow configuration.
配套工具： 若可用，请使用
+runway-dev
获取共享指导。如果尚未安装，请检查工作区，探查
RUNWAYML_API_SECRET
（请勿打印）并阅读当前文档。建议连接Dev MCP以获取项目专属的设置指导。如果用户拒绝或无法连接，请根据当前文档和现有工作流配置继续操作。

Goal

目标

Keep the connection between Runway app workflows and callable API endpoints correct.
确保Runway应用工作流与可调用API端点之间的连接准确无误。

MCP tools

MCP工具

  • get_workflows_setup_guide
    — get current setup, connections, help, and API reference links.
  • get_workflows_setup_guide
    — 获取当前设置、连接方式、帮助信息及API参考链接。

Workflow

工作流程

  1. Call 
    get_workflows_setup_guide
    with the selected 
    projectId
    when setup or current project-specific guidance is required. If existing configuration and live docs define the contract, continue implementation without MCP.
  2. When used, follow the returned guide; do not invent workflow publishing steps.
  3. Inspect the existing workflow contract and application integration before changing either.
  4. Implement, modify, debug, or verify the server-side call per the returned API docs. Wire inputs, invocation state, errors, and outputs into the existing UI or consumer.
  5. When verification is appropriate, run one invocation with representative inputs and present the result.
  1. 当需要设置或项目专属指导时，使用选定的
    projectId
    调用
    get_workflows_setup_guide
    。如果现有配置和实时文档已定义契约，则无需使用MCP即可继续实现。
  2. 使用该工具时，请遵循返回的指导；请勿自行设计工作流发布步骤。
  3. 在更改工作流契约或应用集成之前，请先检查现有内容。
  4. 根据返回的API文档实现、修改、调试或验证服务器端调用。将输入、调用状态、错误信息和输出连接至现有UI或消费者端。
  5. 当需要验证时，使用具有代表性的输入运行一次调用并展示结果。

Docs

文档