Skip to content

执行子工作流(Execute Sub-workflow)#

使用 Execute Sub-workflow 节点在运行 n8n 的主机上运行不同的工作流。

🌐 Use the Execute Sub-workflow node to run a different workflow on the host machine that runs n8n.

节点参数(Node parameters)#

源(Source)#

选择节点应从何处获取子工作流的信息：

🌐 Select where the node should get the sub-workflow's information from:

  • 数据库：选择此选项可通过 ID 从数据库加载工作流。你还必须输入以下任意一项：
    • 从列表中选择：从可用于你账户的工作流列表中选择一个工作流。
    • 工作流 ID：输入工作流的 ID。工作流的 URL 在 /workflow/ 之后包含该 ID。例如，如果工作流的 URL 是 https://my-n8n-acct.app.n8n.cloud/workflow/abCDE1f6gHiJKL7，则 工作流 ID 为 abCDE1f6gHiJKL7。
  • 本地文件：选择此选项以从本地保存的 JSON 文件加载工作流。你还必须输入：
    • 工作流路径：输入本地 JSON 工作流文件的路径，以便节点执行该文件。
  • 参数：选择此选项从参数加载工作流。你还必须输入：
    • 工作流 JSON：输入你希望节点执行的 JSON 代码。
  • URL：选择此选项从 URL 加载工作流。你还必须输入：
    • 工作流 URL：输入你要从中加载工作流的 URL。

工作流输入(Workflow Inputs)#

如果你使用 数据库 和 从列表 选项选择子工作流，子工作流的输入项将会自动显示，准备好让你填写或映射值。

🌐 If you select a sub-workflow using the database and From list options, the sub-workflow's input items will automatically display, ready for you to fill in or map values.

您可以选择删除请求的输入项，在这种情况下，子工作流将收到该项的值为 null。您还可以启用 尝试转换类型 功能，以尝试自动将数据转换为子工作流项所需的类型。

🌐 You can optionally remove requested input items, in which case the sub-workflow receives null as the item's value. You can also enable Attempt to convert types to try to automatically convert data to the sub-workflow item's requested type.

如果子工作流的工作流输入触发器节点使用“接受所有数据”输入数据模式，则输入项不会出现。

🌐 Input items won't appear if the sub-workflow's Workflow Input Trigger node uses the "Accept all data" input data mode.

模式(Mode)#

使用此参数来控制节点的执行模式。可从以下选项中选择：

🌐 Use this parameter to control the execution mode for the node. Choose from these options:

  • 一次运行所有项目：将所有输入项目传递到节点的单次执行中。
  • 每个项目运行一次：依次针对每个输入项目执行该节点一次。

节点选项(Node options)#

此节点包括一个选项：等待子工作流完成。这让你可以控制主工作流是否应在继续下一步之前等待子工作流完成（开启状态），或者主工作流是否应在不等待的情况下继续（关闭状态）。

🌐 This node includes one option: Wait for Sub-Workflow Completion. This lets you control whether the main workflow should wait for the sub-workflow's completion before moving on to the next step (turned on) or whether the main workflow should continue without waiting (turned off).

模板和示例(Templates and examples)#

Template widget placeholder.

设置并使用子工作流(Set up and use a sub-workflow)#

本节逐步介绍如何设置父工作流和子工作流。

🌐 This section walks through setting up both the parent workflow and sub-workflow.

Create the sub-workflow#

  1. Create a new workflow.

    Create sub-workflows from existing workflows

    You can optionally create a sub-workflow directly from an existing parent workflow using the Execute Sub-workflow node. In the node, select the Database and From list options and select Create a sub-workflow in the list.

    You can also extract selected nodes directly using Sub-workflow conversion in the context menu.

  2. Optional: configure which workflows can call the sub-workflow:

    1. Select the Options Options menu menu > Settings. n8n opens the Workflow settings modal.
    2. Change the This workflow can be called by setting. Refer to Workflow settings for more information on configuring your workflows.
  3. Add the Execute Sub-workflow trigger node (if you are searching under trigger nodes, this is also titled When Executed by Another Workflow).
  4. Set the Input data mode to choose how you will define the sub-workflow's input data:
    • Define using fields below: Choose this mode to define individual input names and data types that the calling workflow needs to provide. The Execute Sub-workflow node or Call n8n Workflow Tool node in the calling workflow will automatically pull in the fields defined here.
    • Define using JSON example: Choose this mode to provide an example JSON object that demonstrates the expected input items and their types.
    • Accept all data: Choose this mode to accept all data unconditionally. The sub-workflow won't define any required input items. This sub-workflow must handle any input inconsistencies or missing values.
  5. Add other nodes as needed to build your sub-workflow functionality.
  6. Save the sub-workflow.

Sub-workflow mustn't contain errors

If there are errors in the sub-workflow, the parent workflow can't trigger it.

Load data into sub-workflow before building

This requires the ability to load data from previous executions, which is available on n8n Cloud and registered Community plans.

If you want to load data into your sub-workflow to use while building it:

  1. Create the sub-workflow and add the Execute Sub-workflow Trigger.
  2. Set the node's Input data mode to Accept all data or define the input items using fields or JSON if they're already known.
  3. In the sub-workflow settings, set Save successful production executions to Save.
  4. Skip ahead to setting up the parent workflow, and run it.
  5. Follow the steps to load data from previous executions.
  6. Adjust the Input data mode to match the input sent by the parent workflow if necessary.

You can now pin example data in the trigger node, enabling you to work with real data while configuring the rest of the workflow.

Call the sub-workflow#

  1. Open the workflow where you want to call the sub-workflow.
  2. Add the Execute Sub-workflow node.

  3. In the Execute Sub-workflow node, set the sub-workflow you want to call. You can choose to call the workflow by ID, load a workflow from a local file, add workflow JSON as a parameter in the node, or target a workflow by URL.

    Find your workflow ID

    Your sub-workflow's ID is the alphanumeric string at the end of its URL.

  4. Fill in the required input items defined by the sub-workflow.

  5. Save your workflow.

When your workflow executes, it will send data to the sub-workflow, and run it.

You can follow the execution flow from the parent workflow to the sub-workflow by opening the Execute Sub-workflow node and selecting the View sub-execution link. Likewise, the sub-workflow's execution contains a link back to the parent workflow's execution to navigate in the other direction.

数据如何在工作流之间传递(How data passes between workflows)#

As an example, imagine you have an Execute Sub-workflow node in Workflow A. The Execute Sub-workflow node calls another workflow called Workflow B:

  1. The Execute Sub-workflow node passes the data to the Execute Sub-workflow Trigger node (titled "When executed by another node" in the canvas) of Workflow B.
  2. The last node of Workflow B sends the data back to the Execute Sub-workflow node in Workflow A.