Verified65% confidenceFactExact time
The Webhook trigger node in n8n has two modes: test URL and production URL; the test URL path contains the word 'test' and is primarily used for debugging during the development phase in conjunction with the Execute Workflow button.
3
Sources
65%
Confidence
Medium-term (~90 days)
Relevance
10/5/2026
First Seen
Valid until: 1/3/2027
Sources
Related Entities
Related Claims
Unverifiedn8n's Webhook workflow must be in the Active (published) state to continuously listen; during testing, a temporary Test URL is used, and for production deployment it must be switched to the Production URL, as the two addresses are different.72% similarUnverifiedWhen configuring the Webhook, you must enter the callback URL generated by n8n and provide a custom Verify Token; the Webhook is only activated after Meta completes the handshake verification via a GET request.67% similarPartially VerifiedEvent triggers rely on the Webhook mechanism — an external application sends an HTTP request to the URL provided by N8N when the event occurs, and N8N starts the corresponding Workflow upon receiving it.67% similarUnverifiedwebhook.py is a server based on the standard-library ThreadingHTTPServer with five routes in total, including GET /webhook (Meta verification handshake), POST /webhook (parsing Meta's nested payload and replying via Graph API v19.0, printing a [DRY-RUN] log when credentials are not configured), and POST /twilio (receiving form-encoded TwiML), among others.65% similarUnverifiedAfter activating a workflow in n8n, a unique Webhook URL is generated, which can be registered with SaaS platforms that support webhooks such as Typeform, Stripe, and Shopify.65% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/976429API
curl https://kongchang.com/api/v1/knowledge/claims/976429MCP
get_claim(id=976429)