3 ms·
Show HN: Webhook API – inbound email –> webhook
Hi HN,
I often run into systems that can send email but cannot call a webhook directly
I built a tool that creates an opaque email address <mailboxId>@hook.echovalue.dev and forwards inbound messages as structured JSON to a configured endpoint. It can also call a webhook from a cron schedule, so small scheduled jobs do not need their own worker
There are built-in formats for Slack, Discord, Teams, Telegram and custom JSON templates.
Pricing is pay-as-you-go and intentionally low. It is mostly there as an abuse limit rather than a subscription model
Docs:
https://docs.echovalue.dev/webhook/ https://docs.echovalue.dev/webhook/
any feedback?
- karerckor 5mo agoOut of curiosity — what's the inbound email pipeline behind this? AWS SES + Lambda or something custom? Asking because I've been weighing the same options for a side project and the trade-offs aren't obvious.