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

Using MAKE.com workflow automation: bad_request: The browser (or proxy) sent a request that this server could not understand #7396

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

Originally created by @mijoro7 on GitHub (Dec 25, 2024).

Self Checks

  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • 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.

Dify version

0.14.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Using Makedotcom and Dify chatflow API to automate tasks.
Chatflow "Query": "{text}" is from a previous module and sent automatically inside the Curl command as a variable.
I always get this issue when executing the scenario.

But when I test it manually using Postman, it works without any issue.
I copy-pasted the same variable value in Postman, so I don't think it's a formatting issue.

Check those image below:
Via Make: https://i.imgur.com/7ESPtQs.png
Via Postman: https://i.imgur.com/YD3lUDp.png

One thing that I want to request also is the ability to trigger/launch a chatflow or workflow via webhook.
If it was possible the issue above would be fixed as I can just use an webhook to launch the chatflow instead of doing an API call.
The data (query text) will be sent via the webhook instead.

✔️ Expected Behavior

To get a 200 OK response like with Postman

❌ Actual Behavior

I get a bad_request: The browser (or proxy) sent a request that this server could not understand whenever I try to automate things via Make

Originally created by @mijoro7 on GitHub (Dec 25, 2024). ### Self Checks - [X] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [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. ### Dify version 0.14.2 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Using Makedotcom and Dify chatflow API to automate tasks. Chatflow "Query": "{text}" is from a previous module and sent automatically inside the Curl command as a variable. I always get this issue when executing the scenario. But when I test it manually using Postman, it works without any issue. I copy-pasted the same variable value in Postman, so I don't think it's a formatting issue. Check those image below: Via Make: https://i.imgur.com/7ESPtQs.png Via Postman: https://i.imgur.com/YD3lUDp.png ---- One thing that I want to request also is the ability to trigger/launch a chatflow or workflow via webhook. If it was possible the issue above would be fixed as I can just use an webhook to launch the chatflow instead of doing an API call. The data (query text) will be sent via the webhook instead. ### ✔️ Expected Behavior To get a 200 OK response like with Postman ### ❌ Actual Behavior I get a bad_request: The browser (or proxy) sent a request that this server could not understand whenever I try to automate things via Make
yindo closed this issue 2026-02-21 18:20:24 -05:00
yindo commented 2026-02-21 18:20:24 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jan 25, 2025):

Hi, @mijoro7. I'm Dosu, and I'm helping the Dify team manage their backlog. I'm marking this issue as stale.

Issue Summary

  • You are experiencing a "bad_request" error when using the Dify chatflow API with MAKE.com.
  • The request works correctly in Postman, suggesting a potential issue with the API call setup in MAKE.com.
  • You suggested adding a webhook option to trigger the chatflow as a possible solution.
  • There have been no further comments or updates on this issue.

Next Steps

  • Please confirm if this issue is still relevant with the latest version of the Dify repository. If it is, you can keep the discussion open by commenting here.
  • If there is no further activity, this issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Jan 25, 2025): Hi, @mijoro7. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog. I'm marking this issue as stale. **Issue Summary** - You are experiencing a "bad_request" error when using the Dify chatflow API with MAKE.com. - The request works correctly in Postman, suggesting a potential issue with the API call setup in MAKE.com. - You suggested adding a webhook option to trigger the chatflow as a possible solution. - There have been no further comments or updates on this issue. **Next Steps** - Please confirm if this issue is still relevant with the latest version of the Dify repository. If it is, you can keep the discussion open by commenting here. - If there is no further activity, this issue will be automatically closed in 15 days. Thank you for your understanding and contribution!
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
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#7396
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?