HN 표시: Webhook API – 인바운드 이메일 –> Webhook

webhook-api email and cron triggers Email or cron → webhook. Configure an endpoint once. Receive structured HTTP POST events from echoValue. # Trigger types: email, cron # Native formats: Slack, Discord, Teams, Telegram, PagerDuty how-it-works Three steps. No server. One endpoint for multiple trigger sources. curl 'https://api.echovalue.dev/webhook' \ -H 'x-token: mytoken' \ -H 'content-type: application/json' \ -d '{"url":"https://myapp.example.com/hooks/events","trigger":"email"}' % {"mailboxId":"r_abcd1234","email":"[email protected]",...} # Or configure a scheduled webhook curl 'https://api.echovalue.dev/webhook' \ -H 'x-token: mytoken' \ -H 'content-type: application/json' \ -d '{"url":"https://myapp.example.com/hooks/events","schedule":{"cron":"*/15 * * * *","timezone":"Europe/Rome"}}' 1. configure endpoint Set your webhook URL once via the API. echoValue delivers trigger events to that endpoint. 2. choose trigger Use an opaque mailbox address for inbound email or a cron schedule for timed delivery. 3. receive events Every trigger sends an HTTP POST to your endpoint with a structured JSON payload. triggers Start with email or schedule delivery with cron. Same endpoint model, same credit system. email trigger Every webhook can get an opaque mailbox address such as @hook.echovalue.dev. Send an email and receive the parsed message as JSON. cron trigger Run scheduled webhook calls for periodic jobs, reminders, heartbeat checks, and automation workflows without hosting a scheduler. structured delivery Receive JSON payloads at your endpoint with a consistent event model across email, cron, and test triggers. email-payload What arrives at your webhook endpoint for the email trigger. { "externalMessageId": "", "receivedAt": "2026-04-04T09:21:35.218Z", "from": { "email": "[email protected]", "name": "John Snow" }, "to": [{ "email": "[email protected]", "name": "Support Inbox" }], "cc": [{ "email": "[email protected]", "name": "Jane Doe" }], "subject": "Alert: Server down", "text": "Server #3 is not responding", "html": "Server #3 is not responding", "headers": { /* raw email headers */ }, "attachments": [ { "filename": "attachment.pdf", "contentType": "application/pdf", "size": 33380, "downloadUrl": "", "downloadUrlExpiresAt": "2026-04-04T09:26:35.218Z" } ], "provider": "mail", "url": "https://hook.echovalue.dev/r_abcd1234" } from / to Sender as an object and recipients as arrays with email and name. Use from.email to filter, route, or allow-list traffic in your handler. subject Perfect for routing logic — treat it as an event type or command keyword. text / html Email body in both plain text and HTML. Parse, store, or forward either format — your call. attachments Each attachment includes a short-lived downloadUrl (60 min TTL), filename, content type, and size in bytes. Max attachment size: 20 MB. native-formats Set format once. No payload handling on your end. # Forward emails directly to Slack curl 'https://api.echovalue.dev/webhook' \ -H 'x-token: mytoken' \ -H 'Content-Type: application/json' \ -d '{"url":"https://hooks.slack.com/services/T00/B00/XXX","format":"slack"}' % {"mailboxId":"r_abcd1234","email":"[email protected]",...} slack discord microsoft teams telegram pagerduty use-cases Turn inbound messages and schedules into webhook-driven automation. automation entry point Zapier, Make, n8n, Power Automate — all accept webhooks. Unlike native email triggers, no OAuth or inbox access needed. Use an opaque mailbox address or scheduled delivery. ai agent input Email is the interface everyone knows. Turn it into programmable input for AI agents — classify, extract, triage, respond. scheduled jobs Run scheduled pings, reminders, periodic syncs, and heartbeat jobs without deploying a cron worker. legacy integration ERP systems, scanners, SCADA, printers — anything that sends email becomes webhook-capable. No code changes on the source. notification hub Centralize email alerts from multiple services into one endpoint. Forward to Slack, PagerDuty, or your own dashboard. IoT & embedded Hardware and industrial devices that can send email but not HTTP. A natural bridge to modern APIs. sms gateways Carrier SMS-to-email becomes SMS-to-webhook in one step. Zero infrastructure to manage. pricing Zero subscriptions. Pay per use. Credits never expire. Cost per operation | Operation | Cost | |---|---| | Configure webhook | 1 credit | | Get webhook config | 1 credit | | Delete webhook | 1 credit | | Email processed (no attachments) | 2 credits | | Email processed (with attachments) | 5 credits | | Scheduled webhook event | 2 credits | Credits are shared across all echoValue APIs. Pay once, use everywhere. Get Support Questions, feedback, or feature requests about Webhook API.