fsebbah/n8n-workflows

A webhook that refuses every call, in a team's own history.

The team behind fsebbah/n8n-workflows changed its n8n workflow “MENTION---On-Mention-Handler”, and a later commit of its own repaired the break that change made. The break lived less than a day. Run on the first change, the check says:

“Webhook Trigger” does not wait for the Respond to Webhook node after it

Its “Respond” option is “Immediately”, and a Respond to Webhook node follows it. n8n refuses every call to it at run time with “Unused Respond to Webhook node found in the workflow”. Set “Respond” to “Using 'Respond to Webhook' Node”.

The team's two commits

The change, 15 January 2026. Merge pull request #248 from fsebbah/feat/rfc007-mention-service-workflows 383520f
The fix, 15 January 2026. Merge pull request #249 from fsebbah/fix/rfc007-workflows-best-practices 8a76ae3

The workflow's file is workflows/MENTION---On-Mention-Handler.json. Before the change, the check found nothing of this in it; after the fix, it finds nothing again. Each case was read against the team's own fix: the fix changes this step, and the change removes the cause.

Check your workflow Check a change before it ships: paste the workflow. Free. No account. Nothing is stored unless you choose to share it.