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

Add Google Custom Search JSON API Tool #4054

New Issue
Closed
opened 2026-02-21 18:04:34 -05:00 by yindo · 3 comments
yindo commented 2026-02-21 18:04:34 -05:00
Owner
Copy Link
Copy Source

Originally created by @akan on GitHub (Jun 12, 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).
  • Please do not modify this template :) and fill in all the required fields.

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

Title: Add Google Custom Search JSON API Tool for Enhanced Precision in Search

Post:
I'd like to propose the integration of the Google Custom Search JSON API into the tools available within Dify. This feature addresses a challenge I've encountered where there is a need for more precise and targeted search capabilities beyond what is currently offered.

2. Describe the feature you'd like to see

The feature I'd like to see is the addition of the Google Custom Search JSON API as a tool option within Dify. This would allow users to perform more targeted and precise searches, effectively turning it into a mini knowledge base.

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

The integration of the Google Custom Search JSON API will significantly improve the search precision within Dify, allowing for more accurate information retrieval. This enhancement will streamline the workflow by providing more reliable search results, thus saving time and improving the overall user experience.

4. Additional context or comments

No response

5. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @akan on GitHub (Jun 12, 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] Please do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? Title: Add Google Custom Search JSON API Tool for Enhanced Precision in Search Post: I'd like to propose the integration of the Google Custom Search JSON API into the tools available within Dify. This feature addresses a challenge I've encountered where there is a need for more precise and targeted search capabilities beyond what is currently offered. ### 2. Describe the feature you'd like to see The feature I'd like to see is the addition of the Google Custom Search JSON API as a tool option within Dify. This would allow users to perform more targeted and precise searches, effectively turning it into a mini knowledge base. ### 3. How will this feature improve your workflow or experience? The integration of the Google Custom Search JSON API will significantly improve the search precision within Dify, allowing for more accurate information retrieval. This enhancement will streamline the workflow by providing more reliable search results, thus saving time and improving the overall user experience. ### 4. Additional context or comments _No response_ ### 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 18:04:34 -05:00
yindo closed this issue 2026-02-21 18:04:34 -05:00
yindo commented 2026-02-21 18:04:34 -05:00
Author
Owner
Copy Link
Copy Source

@akan commented on GitHub (Jun 13, 2024):

I've test http request. but got
Run failed: Node HTTP 请求 run failed: The handshake operation timed out
docker-nginx-1 | 172.27.0.1 - - [14/Jun/2024:02:12:27 +0000] "POST /console/api/apps/77f89866-9b37-4987-ad9f-f65b617b7702/advanced-chat/workflows/draft/run HTTP/1.1" 200 13271 "http://39.105.139.233:7078/app/77f89866-9b37-4987-ad9f-f65b617b7702/workflow" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.0.0 Safari/537.36" "-"
docker-ssrf_proxy-1 | 1718331147.604 180478 172.27.0.8 TCP_TUNNEL/200 39 CONNECT www.googleapis.com:443 - HIER_DIRECT/172.217.160.106 -
docker-db-1 | 2024-06-14 02:12:38.999 UTC [23] LOG: checkpoint starting: time
docker-db-1 | 2024-06-14 02:12:41.958 UTC [23] LOG: checkpoint complete: wrote 30 buffers (0.2%); 0 WAL file(s) added, 0 removed, 0 recycled; write=2.915 s, sync=0.020 s, total=2.959 s; sync files=26, longest=0.007 s, average=0.001 s; distance=146 kB, estimate=146 kB

@akan commented on GitHub (Jun 13, 2024): I've test http request. but got Run failed: Node HTTP 请求 run failed: The handshake operation timed out docker-nginx-1 | 172.27.0.1 - - [14/Jun/2024:02:12:27 +0000] "POST /console/api/apps/77f89866-9b37-4987-ad9f-f65b617b7702/advanced-chat/workflows/draft/run HTTP/1.1" 200 13271 "http://39.105.139.233:7078/app/77f89866-9b37-4987-ad9f-f65b617b7702/workflow" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.0.0 Safari/537.36" "-" docker-ssrf_proxy-1 | 1718331147.604 180478 172.27.0.8 TCP_TUNNEL/200 39 CONNECT www.googleapis.com:443 - HIER_DIRECT/172.217.160.106 - docker-db-1 | 2024-06-14 02:12:38.999 UTC [23] LOG: checkpoint starting: time docker-db-1 | 2024-06-14 02:12:41.958 UTC [23] LOG: checkpoint complete: wrote 30 buffers (0.2%); 0 WAL file(s) added, 0 removed, 0 recycled; write=2.915 s, sync=0.020 s, total=2.959 s; sync files=26, longest=0.007 s, average=0.001 s; distance=146 kB, estimate=146 kB
yindo commented 2026-02-21 18:04:35 -05:00
Author
Owner
Copy Link
Copy Source

@akan commented on GitHub (Jun 13, 2024):

It is ok when us serp.

@akan commented on GitHub (Jun 13, 2024): It is ok when us serp.
yindo commented 2026-02-21 18:04:35 -05:00
Author
Owner
Copy Link
Copy Source

@akan commented on GitHub (Jun 13, 2024):

Now I may config ssrf_proxy on the right way. but steel got error:
docker-ssrf_proxy-1 | 1718334435.769 163733 172.27.0.8 TCP_TUNNEL/200 39 CONNECT www.googleapis.com:443 - HIER_DIRECT/172.217.160.106 -
Run failed: Node HTTP 请求 run failed: [SSL: UNEXPECTED_EOF_WHILE_READING] EOF occurred in violation of protocol (_ssl.c:1007)

@akan commented on GitHub (Jun 13, 2024): Now I may config ssrf_proxy on the right way. but steel got error: docker-ssrf_proxy-1 | 1718334435.769 163733 172.27.0.8 TCP_TUNNEL/200 39 CONNECT www.googleapis.com:443 - HIER_DIRECT/172.217.160.106 - Run failed: Node HTTP 请求 run failed: [SSL: UNEXPECTED_EOF_WHILE_READING] EOF occurred in violation of protocol (_ssl.c:1007)
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#4054
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?