-
Notifications
You must be signed in to change notification settings - Fork 18.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Triggers that categorize webhook no longer fire since the upgrade. #13974
Comments
Hey @jpmarobiin, We have created an internal ticket to look into this which we will be tracking as "GHC-1232" |
Hey @jpmarobiin More details are needed, can you be more specific and provide an example that fails? I have added a webhook trigger to a workflow and a Telegram trigger and it is working as expected so it doesn't look like all webhook triggers are failing. |
Incredible, nothing works for me. Neither my triggers nor my webhooks triggered from Bubble. I also have this workflow /Zcsq6q3gMVO3n0BL but I actually have several. |
Hey @jpmarobiin That id means nothing to me as I am not able to access cloud instances from here as this is not a place for support it is for reporting bugs. Are you able to share the json for a workflow that doesn't work? As a test what happens if you make a new workflow and just add a webhook trigger node to it then activate it and load the webhook url in your browser does that work? |
I can, but in private. But I don't understand, everything was working fine,
and I think it was the upgrade that broke everything. Thanks for your help.
I'm struggling...
Le lun. 17 mars 2025 à 21:55, Jon ***@***.***> a écrit :
… Hey @jpmarobiin <https://github.com/jpmarobiin>
That id means nothing to me as I am not able to access cloud instances
from here as this is not a place for support it is for reporting bugs.
Are you able to share the json for a workflow that doesn't work?
As a test what happens if you make a new workflow and just add a webhook
trigger node to it then activate it and load the webhook url in your
browser does that work?
—
Reply to this email directly, view it on GitHub
<#13974 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/BQRD5CC3IYI6BCJTOOMZHST2U4ZEVAVCNFSM6AAAAABZEDQUBKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMZQHEYDINZSG4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
[image: Joffcom]*Joffcom* left a comment (n8n-io/n8n#13974)
<#13974 (comment)>
Hey @jpmarobiin <https://github.com/jpmarobiin>
That id means nothing to me as I am not able to access cloud instances
from here as this is not a place for support it is for reporting bugs.
Are you able to share the json for a workflow that doesn't work?
As a test what happens if you make a new workflow and just add a webhook
trigger node to it then activate it and load the webhook url in your
browser does that work?
—
Reply to this email directly, view it on GitHub
<#13974 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/BQRD5CC3IYI6BCJTOOMZHST2U4ZEVAVCNFSM6AAAAABZEDQUBKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMZQHEYDINZSG4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
[image: twitter] <https://twitter.com/mascletjp>
[image: linkedin] <https://www.linkedin.com/in/mascletjp/>
Jean-Paul Masclet
Associé
Robiin - Expertise fiscale
0667273088
***@***.***
www.robiin.fr
|
Hey @jpmarobiin Have you tried the test with a new workflow that only includes a webhook trigger node to see if that works? |
Describe the problem/error/question
Triggers that categorize webhook no longer fire since the upgrade.
What is the error message (if any)?
NoN message erreur
Please share your workflow/screenshots/recording
No run
Share the output returned by the last node
Debug info
core
storage
pruning
client
Generated at: 2025-03-16T22:17:12.799Z}
The text was updated successfully, but these errors were encountered: