Webhooks
by @ops Inbound Email Processing
Receiving and parsing inbound email (a support-desk reply-by-email, a newsletter bounce handler, anything that turns an email into a database record) via your provider's inbound-parse webhook — the inbound-email counterpart to the general Webhook Receiver recipe.
Loads this recipe straight into the wizard — every setting stays editable before you generate anything.
The stack
Install
# pulls this exact recipe straight from the Vault $ npx stacktora install inbound-email-processing --remote $ stacktora sync # generate the files
What you get
More from the Vault
Outbound Webhook Delivery Service
The sending side, not the receiving side — YOUR app delivering webhooks to customers/integrations, with signing, retry/backoff on failure, and a delivery log they (and you) can actually inspect. Pairs with the Webhook Receiver recipe as the complete inbound+outbound picture.
Webhook Receiver & Event Ingestion
Idempotent webhook ingestion with signature verification and a Redis-backed queue plus worker for async, retry-safe processing — the pattern every Stripe/GitHub/Twilio integration needs and almost always ends up building from scratch, badly, under time pressure.
Webhook Testing & Replay Tool Backend
Captures incoming webhook payloads for inspection and replay during development — a debugging tool, not a production integration. The backend behind a self-hosted "webhook.site"-style utility.
.NET + Postgres + Redis: Fintech-oriented Baseline
A security-conscious starting point for financial and payments-adjacent backends: .NET API, Postgres for ledger/transaction records, and Redis for session and rate-limit state. This is a starting baseline only, not a certified or verified PCI-DSS/regulatory-compliant stack — your own security and compliance review is still required before handling real financial data.