Webhook Debugger & Logger runs in two modes: on the Apify platform, where you get a public webhook URL within seconds, or self-hosted via Node.js or Docker for environments where you control the infrastructure. Choose the path that fits your workflow.Documentation Index
Fetch the complete documentation index at: https://supahooks.ar27111994.dev/llms.txt
Use this file to discover all available pages before exploring further.
- Apify platform
- Node.js
- Docker
Run on Apify
The Apify platform is the fastest way to get a live webhook endpoint. No installation, no port forwarding — Apify handles the public URL and storage for you.Open the actor in the Apify Store
Go to apify.com/ar27111994/webhook-debugger-logger and click Try for free.
Configure your input
Set your preferred options in the input form. A minimal configuration to get started:See Input reference for all available options.
Start the actor
Click Start. The actor generates your webhook endpoints immediately and exposes them through the Apify web server URL.
Keep the actor warm with Apify Standby mode so your webhook endpoints stay ready for incoming traffic without paying a cold-start penalty on each request. This is especially useful for long-running debug sessions or when you need the endpoint available on demand.
Environment configuration
These are the key environment variables for both Node.js and Docker deployments.| Variable | Purpose | Default |
|---|---|---|
ACTOR_WEB_SERVER_PORT | HTTP port the server listens on | 8080 |
INPUT | Full actor input as a JSON string — sets urlCount, retentionHours, authKey, and all other options | unset |
APIFY_LOCAL_STORAGE_DIR | Directory for captured events, webhook state, and large payload offloads | ./storage |
LOG_LEVEL | Logging verbosity (info, debug, warn, error) | info |