This document details how plugins can reverse invoke Tool services within the Dify platform. It covers three types of tool invocation methods calling installed tools (Built-in Tool), calling Workflow as Tool, and calling custom tools (Custom Tool). Each method includes corresponding entry points and interface parameter descriptions.
Reverse invoking a Tool means that a plugin can call other tool-type plugins within the Dify platform. If you are unfamiliar with the basic concepts of reverse invocation, please first read Reverse Invocation of Dify Services.
Consider the following scenarios:
In these cases, you need to call other existing tools within your plugin. These tools might be from the marketplace, a self-built Workflow as a Tool, or a custom tool.
These requirements can be met by calling the self.session.tool
field of the plugin.
Allows the plugin to call various tools installed in the current Workspace, including other tool-type plugins.
Entry Point
Interface
Here, provider
is the plugin ID plus the tool provider name, formatted like langgenius/google/google
. tool_name
is the specific tool name, and parameters
are the arguments passed to the tool.
For more information on Workflow as Tool, please refer to the Tool Plugin documentation. (Note: Original link /plugin-dev-zh/9223-tool
does not exist in English list, linked to closest match).
Entry Point
Interface
In this case, provider
is the ID of this tool, and tool_name
is specified during the creation of the tool.
Entry Point
Interface
Here, provider
is the ID of this tool, and tool_name
is the operation_id
from the OpenAPI specification. If it doesn’t exist, it’s the tool_name
automatically generated by Dify, which can be found on the tool management page.
/plugin-dev-zh/9223-tool
does not exist in English list, linked to closest match)Edit this page | Report an issue