Show HN: Webhook API – inbound email –> webhook

Posted by emiliano on Monday April 27, 2026 @07:40AM
from the show-hn dept.

https://www.echovalue.dev/webhook-api/

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/

any feedback?

( 2 comments | 3 points | on HN )

Re:Show HN: Webhook API – inbound email –> webhook by karerckor on Tuesday April 28, 2026 @03:56AM (#47931620)

Out 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.

[ Parent | on HN ]

Re:Show HN: Webhook API – inbound email –> webhook by emiliano on Tuesday April 28, 2026 @06:07AM (#47932438)

I’m using Cloudflare Email Routing with a catch-all address that triggers a Worker. The Worker parses the email and stores the attachments in R2.

Pretty simple setup, but it works well for this use case

[ Parent | on HN ]