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

Dify API's as Blocks / Tools - No Code Enhancement #2573

New Issue
Closed
opened 2026-02-21 17:47:26 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 17:47:26 -05:00
Owner
Copy Link
Copy Source

Originally created by @Darren-A11att on GitHub (Apr 24, 2024).

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).
  • Pleas do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing?

I can't easily build no-code apps that utilise all of Dify's API's.

2. Describe the feature you'd like to see

I would like each of Dify's API's added as Blocks or a Tool so that I build no-code workflows that utilise all of dify's functionality.

For example:
I want to build a work flow to scrape webpages and add the scraped content to a specific knowledge base. The workflow would look something like this:

  1. Input URL to scrape
  2. Use Webscraper or JinaReader (+summary) to pull the text of the site
  3. Call Knowledge API to get knowledge list (maybe display as buttons?)
  4. Select the kowledge base I want to add to the scraped text to
  • The text is then chunked and added to that knowledge base

Another Example:
I would like to add "Add to knowledge" as a Tool when creating an Agent, so I can then have either a specific response or the entire conversation history added to a specific knowledge base.

Here is why:

Dify has an extensive API library that can give user far more capability to create apps that make their use of dify more powerful than it already is.

However, the API's endpoints are not already built into Dify's Blocks or Tools.

To add to this, in the API docs, the requests are already provided in curl format, but, (no-code) users can't use these.

Then, you could do "some code", except, the only block I can add is a HTTP request.

The issue is, that the example in the API Docs is a CURL and this doesn't map to the HTTP request module.

Example:

Create Document from text
/datasets/{dataset_id}/document/create_by_text

This api is based on an existing Knowledge and creates a new document through text based on this Knowledge.

curl --location --request POST 'http://localhost/v1/datasets/{dataset_id}/document/create_by_text'
--header 'Authorization: Bearer {api_key}'
--header 'Content-Type: application/json'
--data-raw '{"name": "text","text": "text","indexing_technique": "high_quality","process_rule": {"mode": "automatic"}}'

But the fields I have in the HTTP request are:

  • API Dropdown + URL (this is self-explantory)
  • Headers
  • Params
  • Body
    • None, form-data, x-www-form-urlencoded, raw text, JSON

3. How will this feature improve your workflow or experience?

It will allow me to utilise the full capability of Dify and make builting no code Apps easier.

4. Additional context or comments

I am happy to contribute as a "product manager" or "user" for this feature

5. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @Darren-A11att on GitHub (Apr 24, 2024). ### 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] Pleas do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? I can't easily build no-code apps that utilise all of Dify's API's. ### 2. Describe the feature you'd like to see I would like each of Dify's API's added as Blocks or a Tool so that I build no-code workflows that utilise all of dify's functionality. For example: I want to build a work flow to scrape webpages and add the scraped content to a specific knowledge base. The workflow would look something like this: 1. Input URL to scrape 2. Use Webscraper or JinaReader (+summary) to pull the text of the site 3. Call Knowledge API to get knowledge list (maybe display as buttons?) 4. Select the kowledge base I want to add to the scraped text to - The text is then chunked and added to that knowledge base Another Example: I would like to add "Add to knowledge" as a Tool when creating an Agent, so I can then have either a specific response or the entire conversation history added to a specific knowledge base. Here is why: Dify has an extensive API library that can give user far more capability to create apps that make their use of dify more powerful than it already is. However, the API's endpoints are not already built into Dify's Blocks or Tools. To add to this, in the API docs, the requests are already provided in curl format, but, (no-code) users can't use these. Then, you could do "some code", except, the only block I can add is a HTTP request. The issue is, that the example in the API Docs is a CURL and this doesn't map to the HTTP request module. Example: **Create Document from text** /datasets/{dataset_id}/document/create_by_text _This api is based on an existing Knowledge and creates a new document through text based on this Knowledge._ curl --location --request POST 'http://localhost/v1/datasets/{dataset_id}/document/create_by_text' \ --header 'Authorization: Bearer {api_key}' \ --header 'Content-Type: application/json' \ --data-raw '{"name": "text","text": "text","indexing_technique": "high_quality","process_rule": {"mode": "automatic"}}' But the fields I have in the HTTP request are: - API Dropdown + URL (this is self-explantory) - Headers - Params - Body - - None, form-data, x-www-form-urlencoded, raw text, JSON ### 3. How will this feature improve your workflow or experience? It will allow me to utilise the full capability of Dify and make builting no code Apps easier. ### 4. Additional context or comments I am happy to contribute as a "product manager" or "user" for this feature ### 5. Can you help us with this feature? - [X] I am interested in contributing to this feature.
yindo added the 💪 enhancement label 2026-02-21 17:47:26 -05:00
yindo closed this issue 2026-02-21 17:47:26 -05:00
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 💪 enhancement
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#2573
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?