NodeTrigger

People building automations need endpoints that can receive webhooks from services like Stripe or Shopify, or that can execute a task and return a result to another tool like n8n or Make. Today this usually means writing fragile custom HTTP handlers, verifying signatures manually, building retry logic for failed deliveries, and juggling ad-hoc inboxes or endpoints that mix responsibilities. If a destination is down, an unhandled webhook can simply disappear, and there is often no dashboard showing delivery history, request status or latency. This leaves automation builders babysitting endpoints instead of building workflows.

NodeTrigger offers two endpoint types with a strict timing contract: a Route stores an incoming event, immediately acknowledges the sender with a 200, then filters, transforms and fans it out to destinations like Slack, n8n or a database with automatic retries if a destination fails. An Action holds the connection open while it executes a task, such as generating a QR code, taking a screenshot, converting a file, generating a PDF, or calling another URL, and returns the computed result directly in the response. Stripe and Shopify signatures are verified at the door, every URL is individually signed, and payloads, logs and secrets stay private to the account. A dashboard shows Routes and Actions side by side with delivery history, status and latency, and customers can run endpoints under their own domain.