Documentation Index
Fetch the complete documentation index at: https://wsignal.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Overview
wsignal listens on your local machine. ngrok gives that local server a public URL so external webhook providers can deliver requests to it.
The setup is:
- Start
wsignalon its local port. - Start
ngrokand forward traffic to that same port. - Configure your provider to send webhooks to the
ngrokURL plus the matchingwsignalendpoint path.
Default Starter Flow
If you used the starter config fromwsignal init --yes, wsignal listens on:
- Port:
8787 - Endpoint path:
/webhook
wsignal:
ngrok:
ngrok will print a public forwarding URL such as:
Multiple Endpoints
ngrok only forwards to the local wsignal port. wsignal still handles routing by path.
For example, if your config contains:
https://example.ngrok.app/githubhttps://example.ngrok.app/stripehttps://example.ngrok.app/alerts
Verifying Traffic
After you configure the remote webhook URL:- Trigger a test event from the provider.
- Check the running
wsignal devterminal. - Review stored records locally:
github or stripe, inspect those instead:
Common Issues
404 No webhook endpoint matched this request.
The provider is calling the wrong path.
Example:
- Config path:
/webhook - Wrong public URL:
https://example.ngrok.app/ - Correct public URL:
https://example.ngrok.app/webhook
405 Method not allowed.
The provider is using a different HTTP method than the one configured for the endpoint.
If the endpoint only allows POST, a GET validation request will fail unless you add that method to the endpoint config.
No requests are reaching wsignal
Check:
wsignal devis runningngrokis forwarding to the correct port- Your provider is using the current
ngrokURL - The provider URL includes the correct endpoint path
Example End-to-End Test
Startwsignal:
ngrok:
curl: