HTTP 请求工具节点#

¥HTTP Request Tool node

Legacy tool version

添加到工作流的 HTTP 请求工具节点的新实例将使用标准的 HTTP 请求节点作为工具。本页介绍传统的独立 HTTP 请求工具节点。

¥New instances of the HTTP Request tool node that you add to workflows use the standard HTTP Request node as a tool. This page is describes the legacy, standalone HTTP Request tool node.

你可以通过在画布上打开节点时检查节点是否具有“添加”选项属性来确定工作流中使用的工具版本。如果显示此按钮，则说明你使用的是新版本，而不是本页所述的版本。

¥You can identify which tool version is in your workflow by checking if the node has an Add option property when you open the node on the canvas. If that button is present, you're using the new version, not the one described on this page.

HTTP 请求工具的工作方式与 HTTP 请求节点类似，但它设计用于与 AI 代理配合使用，以从网站或 API 收集信息。

¥The HTTP Request tool works just like the HTTP Request node, but it's designed to be used with an AI agent as a tool to collect information from a website or API.

本页列出了 HTTP 请求节点支持的操作列表以及更多资源的链接。

¥On this page, you'll find a list of operations the HTTP Request node supports and links to more resources.

Credentials

请参阅 HTTP 请求凭据以了解有关设置身份验证的指导。

¥Refer to HTTP Request credentials for guidance on setting up authentication.

Parameter resolution in sub-nodes

Sub-nodes behave differently to other nodes when processing multiple items using an expression.

Most nodes, including root nodes, take any number of items as input, process these items, and output the results. You can use expressions to refer to input items, and the node resolves the expression for each item in turn. For example, given an input of five name values, the expression {{ $json.name }} resolves to each name in turn.

In sub-nodes, the expression always resolves to the first item. For example, given an input of five name values, the expression {{ $json.name }} always resolves to the first name.

模板和示例#

¥Templates and examples

HTTP 请求工具节点#

模板和示例#

相关资源#