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

[Feature Request] Support multi-method Webhook endpoints for Facebook/Meta integrations #21907

New Issue
Open
opened 2026-02-21 20:14:49 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 20:14:49 -05:00
Owner
Copy Link
Copy Source

Originally created by @saalimon on GitHub (Jan 26, 2026).

Originally assigned to: @saalimon on GitHub.

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

Yes. I am attempting to build a Facebook/Meta integration. Facebook requires the developer to provide a single Webhook URL that handles two distinct types of requests:

GET: Used for one-time verification. Meta sends a hub. A challenge parameter that the server must echo back.

POST: Used for the actual event payloads (messages, updates, etc.).

Currently, Dify triggers are bound to a specific method. If I set the trigger to POST, the Facebook verification fails with: HTTP method mismatch. Expected POST, got GET.

If I attempt to create two separate nodes to "overlap" the endpoint, the system cannot route them correctly because they share the same path but require different handling logic.

2. Additional context or comments

I would like to see an enhancement to the Webhook / Event Trigger node that allows for "Multi-method" support or a specific "Handshake" configuration:

Allow a single Webhook trigger to accept both GET and POST. Within the workflow, we could use a conditional branch to check sys.http_method. (similar to webhook node in n8n)

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @saalimon on GitHub (Jan 26, 2026). Originally assigned to: @saalimon on GitHub. ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [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, otherwise it will be closed. - [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? Tell me about your story. Yes. I am attempting to build a Facebook/Meta integration. Facebook requires the developer to provide a single Webhook URL that handles two distinct types of requests: GET: Used for one-time verification. Meta sends a hub. A challenge parameter that the server must echo back. POST: Used for the actual event payloads (messages, updates, etc.). Currently, Dify triggers are bound to a specific method. If I set the trigger to POST, the Facebook verification fails with: HTTP method mismatch. Expected POST, got GET. If I attempt to create two separate nodes to "overlap" the endpoint, the system cannot route them correctly because they share the same path but require different handling logic. ### 2. Additional context or comments I would like to see an enhancement to the Webhook / Event Trigger node that allows for "Multi-method" support or a specific "Handshake" configuration: Allow a single Webhook trigger to accept both GET and POST. Within the workflow, we could use a conditional branch to check sys.http_method. (similar to webhook node in n8n) ### 3. Can you help us with this feature? - [ ] I am interested in contributing to this feature.
yindo added the 💪 enhancement label 2026-02-21 20:14:49 -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#21907
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?