- A tool-type plugin implements a function, but the result is not as expected and the data needs post-processing.
- A task requires a web scraper, and you want the flexibility to choose the scraping service.
- You need to aggregate results from multiple tools, which is difficult to handle in a Workflow application.
self.session.tool field.
Call Installed Tools
Call any tool installed in the current Workspace, including other tool-type plugins.Entry Point
Interface
provider: The plugin ID plus the tool provider name, formatted likelanggenius/google/google.tool_name: The specific tool name.parameters: The arguments passed to the tool.
Call Workflow as Tool
See the Tool Plugin documentation for more information on Workflow as Tool.Entry Point
Interface
provider: The ID of this tool.tool_name: The name specified when the tool was created.
Call Custom Tool
Entry Point
Interface
provider: The ID of this tool.tool_name: Theoperation_idfrom the OpenAPI specification. If nooperation_idexists, this is thetool_nameautomatically generated by Dify, which you can find 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
Edit this page | Report an issue