langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-22 04:25:29 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

How to publish an application as a tool? #14261

New Issue
Closed
opened 2026-02-21 19:16:24 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 19:16:24 -05:00
Owner
Copy Link
Copy Source

Originally created by @Rendtime on GitHub (May 28, 2025).

Self Checks

  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
  • Please do not modify this template :) and fill in all the required fields.

How to publish an application as a tool?

Image

My version is 1.3.1, isn't this version available？？？

Originally created by @Rendtime on GitHub (May 28, 2025). ### Self Checks - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:) - [x] Please do not modify this template :) and fill in all the required fields. ### How to publish an application as a tool? ![Image](https://github.com/user-attachments/assets/c638c865-f640-41a3-badf-92c0e7facf7f) My version is 1.3.1, isn't this version available？？？
yindo added the 🙋‍♂️ question label 2026-02-21 19:16:24 -05:00
yindo closed this issue 2026-02-21 19:16:24 -05:00
yindo commented 2026-02-21 19:16:24 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (May 28, 2025):

To publish an application as a tool in Dify, you generally need to use the workflow feature. After building and debugging your workflow, you can click the "Publish" button in the upper right corner. This allows you to release the workflow as different types of applications, including as a tool. Published workflow tools can then be used as nodes in other workflows, enabling modular and reusable automation. The process typically involves configuring the tool's input and parameters, and optionally setting up authorization or importing custom tools via OpenAPI/Swagger if needed. For more details, see the official documentation on publishing workflow applications as tools.

Regarding version 1.3.1, I was unable to find specific documentation or issues confirming whether this version supports publishing applications as tools. The general process described above applies to recent versions of Dify, but if you do not see the "Publish as Tool" option in your interface, it may be due to version limitations or UI changes introduced after 1.3.1. If that's the case, you may want to review the release notes or consider updating to a newer version for full support.

If you have access to the "Workflow → Publish as Tool" option, you should be able to proceed as described. If not, please let me know what you see in your interface, and I can help troubleshoot further.

To reply, just mention my name @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Join Discord Share on X

@dosubot[bot] commented on GitHub (May 28, 2025): <!-- Answer --> To publish an application as a tool in Dify, you generally need to use the workflow feature. After building and debugging your workflow, you can click the "Publish" button in the upper right corner. This allows you to release the workflow as different types of applications, including as a tool. Published workflow tools can then be used as nodes in other workflows, enabling modular and reusable automation. The process typically involves configuring the tool's input and parameters, and optionally setting up authorization or importing custom tools via OpenAPI/Swagger if needed. For more details, see the official documentation on [publishing workflow applications as tools](https://github.com/crazywoola/dify-docs-mintlify/blob/main/en/guides/workflow/node/tools.mdx). Regarding version 1.3.1, I was unable to find specific documentation or issues confirming whether this version supports publishing applications as tools. The general process described above applies to recent versions of Dify, but if you do not see the "Publish as Tool" option in your interface, it may be due to version limitations or UI changes introduced after 1.3.1. If that's the case, you may want to review the release notes or consider updating to a newer version for full support. If you have access to the "Workflow → Publish as Tool" option, you should be able to proceed as described. If not, please let me know what you see in your interface, and I can help troubleshoot further. <!-- Dosu Comment Footer --> *To reply, just mention my name [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/53304b5d-9d69-4c0b-91a0-1fb42d2bd1df?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/53304b5d-9d69-4c0b-91a0-1fb42d2bd1df?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/53304b5d-9d69-4c0b-91a0-1fb42d2bd1df?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/53304b5d-9d69-4c0b-91a0-1fb42d2bd1df?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/53304b5d-9d69-4c0b-91a0-1fb42d2bd1df?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/53304b5d-9d69-4c0b-91a0-1fb42d2bd1df?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/53304b5d-9d69-4c0b-91a0-1fb42d2bd1df?feedback_type=other)</sup>&nbsp;&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/20369)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 🙋‍♂️ question
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#14261
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?