Skip to content

Webhook Inbound Email

Use an inbound email webhook when you want echoValue to give you a mailbox address and forward each received email to your webhook URL.

Use webhook.echovalue.dev when you need a temporary HTTPS webhook URL for testing.

  • An opaque email address such as r_xxxxx@hook.echovalue.dev
  • Optional email attachment forwarding via includeAttachments
  • Optional format adapters such as slack, discord, teams, telegram, pagerduty, or custom
  • The inbound email payload documented in Webhook Payloads
Terminal window
curl 'https://api.echovalue.dev/webhook' \
-H 'x-token: mytoken' \
-H 'Content-Type: application/json' \
-d '{
"webhookId": "support-alerts",
"url": "https://hooks.slack.com/services/XXX/YYY/ZZZ",
"format": "slack",
"includeAttachments": false
}'
{
"webhookId": "support-alerts",
"webhook": "https://hooks.slack.com/services/XXX/YYY/ZZZ",
"headers": {},
"format": "slack",
"options": {},
"includeAttachments": false,
"email": "r_abcd1234@hook.echovalue.dev",
"hash": "a1b2c3d4e5f6..."
}
  • Use format, template, options, and includeAttachments only in inbound email mode.
  • Do not send schedule in this mode.
  • If format is omitted, the raw inbound email payload is forwarded as JSON.
  • Inbound email payloads are limited to 1 MiB after parsing.
  • echoValue outbound webhook delivery has a 10s timeout, follows at most 10 redirects, and has no application-level retry.
  • Delivery succeeds only when your webhook returns a 2xx response. 4xx/5xx responses are recorded as failed delivery.
  • Inbound email delivery is best effort. Design your webhook to accept duplicate messages and recover from missed deliveries.
  • echoValue does not retain routed email content after webhook delivery.
  • Turn support mailbox traffic into Slack or Discord messages
  • Trigger PagerDuty incidents from inbound alert emails
  • Forward normalized email data into your own application

See also: