The idea is:
Display the verify token (node ID) in the WhatsApp Trigger node UI so users can easily copy it for Facebook/WhatsApp webhook configuration. Currently, users must export their workflow as JSON and manually extract the node ID to complete webhook setup, as Facebook now requires this verify token field to be filled manually.
My use case:
When setting up WhatsApp Business API webhooks, Facebook requires a "Verify Token" that must match what n8n expects. n8n automatically uses the node's internal ID as this token, but this value is hidden from users. Without access to this ID, users cannot complete the webhook configuration and their WhatsApp integration fails to work.
I think it would be beneficial to add this because:
This solves a critical UX problem that blocks WhatsApp integration setup. Users currently face a confusing dead-end where Facebook demands a verify token but n8n doesn't show what value to enter. Adding a simple read-only field or copy button for the node ID would eliminate this friction and reduce support requests. It would bring the WhatsApp Trigger in line with webhook best practices where all required configuration values are visible to users.
Any resources to support this?
- Facebook Webhook Verification Documentation: https://developers.facebook.com/docs/graph-api/webhooks/getting-started#verification-requests
- WhatsApp Cloud API Webhook Setup: https://developers.facebook.com/docs/whatsapp/cloud-api/webhooks/set-up
- n8n WhatsApp Trigger source code showing automatic node ID usage: https://github.com/n8n-io/n8n/blob/master/packages/nodes-base/nodes/WhatsApp/WhatsAppTrigger.node.ts#L185
Are you willing to work on this?
Yeah, sure!