PingHook

PingHook — The Zero-Config Webhook Bridge The Vision: "Configuration is Friction" In the modern dev-stack, even the simplest tasks—like getting a notification when a script finishes—require an afternoon of setup. You need to create an account, verify an email, manage an API key in a dashboard, and navigate a complex SDK. PingHook was built on a different philosophy: Statelessness. It is a developer-first utility designed to turn any POST request into a formatted Telegram message in under 60 seconds, with zero signup and zero configuration drift. How it Works PingHook acts as a transparent, stateless bridge between your services and your Telegram. Initialize: Message the PingHook Telegram Bot and hit /start. Receive: You instantly get a unique API key and a base URL. Execute: Send a POST request to that URL from anywhere—a GitHub Action, a Python script, an n8n workflow, or a simple curl command. Core Features 1. Nested Dynamic Labeling (URL-as-Config) This is the most powerful feature of PingHook. Instead of going to a dashboard to create "channels" or "tags," you define your alert hierarchy directly in the URL path. Structure: pinghook.dev/v1/send/{api-key}/{label}/{sub-label} Behavior: Any text you place after your API key is automatically parsed as a label. Example: pinghook.dev/v1/send/xyz_123/Production/DB_Backup will deliver a message to your Telegram clearly tagged with [Production] [DB_Backup]. The Benefit: You can change your monitoring logic on the fly just by editing your script's URL. No UI interaction required. 2. Intelligent Payload Formatting PingHook doesn't just dump raw text. It is built to handle: JSON Payloads: Send a JSON body, and the bridge will "pretty-print" it for mobile readability. Plain Text: Perfect for quick success/failure pings. Silent Metadata: It handles the translation from standard webhooks to Telegram-specific Markdown/HTML automatically. 3. Stateless & Privacy-First Architecture Built with Python and FastAPI, PingHook does not maintain a database of your notifications. It functions as a "pass-through" service. Once the message is delivered to the Telegram API, the data is gone from our end. No accounts to be hacked, no data to be leaked. 4. "Set-and-Forget" Reliability By eliminating the UI layer and focusing on a high-performance backend, PingHook is designed for maximum uptime and minimal latency. It is built to be a digital asset that stays out of your way and just works. Use Cases CI/CD Pipelines: Get a ping when a GitHub Action or GitLab CI build succeeds/fails. Server Monitoring: Set up a cron job to curl PingHook if disk space is low. Web Scrapers: Receive a notification when your script finds a specific price drop or data change. Indie Hacking: Monitor lead generation forms or payment webhooks for your MVP without setting up a full observability suite. Technical Specifications Base URL: https://pinghook.dev/v1/send/ Supported Methods: POST Content-Types: application/json, text/plain Bot Interface: https://t.me/PingHookBot The Maker's Note PingHook isn't trying to replace Datadog or PagerDuty. It’s here to solve the "did this run or not?" problem for developers who value their time. It’s open, it’s fast, and it requires exactly zero configuration to get started. Try it now: https://pinghook.dev