- A tool-type plugin has implemented a function, but the result is not as expected, requiring post-processing of the data.
- A task requires a web scraper, and you want the flexibility to choose the scraping service.
- You need to aggregate results from multiple tools, but it’s difficult to handle using a Workflow application.
self.session.tool field of the plugin.
Calling Installed Tools
Allows the plugin to call various tools installed in the current Workspace, including other tool-type plugins. Entry Pointprovider 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.
Calling Workflow as 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
provider is the ID of this tool, and tool_name is specified during the creation of the tool.
Calling Custom Tool
Entry Pointprovider 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.
Related Resources
- Reverse Invocation of Dify Services - Understand the fundamental concepts of reverse invocation
- Reverse Invocation App - Learn how to call Apps within the platform
- Reverse Invocation Model - Learn how to call model capabilities within the platform
- Tool Plugin Development Guide - Learn how to develop tool plugins
- Advanced Tool Plugins - Learn about advanced features like Workflow as Tool (Note: Original link
/plugin-dev-zh/9223-tooldoes not exist in English list, linked to closest match)
Edit this page | Report an issue