Inbound (inbound.new)
Email-to-webhook with TypeScript-first DX.
Inbound converts any address into a webhook endpoint with structured JSON, automatic retries, and exponential backoff. Webhook delivery typically under 2 seconds. TypeScript types for the payload.
Growth work lives or dies on targeting and measurement. What matters is whether behavioral triggers can be built without engineering time, whether the event stream supports attribution past the open, and whether deliverability holds when broadcast volume shares a reputation with product email.
Against behavior-triggered journeys, broadcasts, and winback campaigns measured on revenue, Inbound (inbound.new) covers event stream and multi-tenant support, and does not cover scheduling and the suppressions API. Whether that gap matters depends on how central those are to the build.
- Scheduling: No
- Event stream: Yes
- Deliverability: Not applicable; receive-only.
- Operating since: Not published
- Suppressions API: No
- Best published rate per 1,000: Tiers not published in comparable form
- Multi-tenant: Yes
- Free tier: 100/mo
- Starts at: $10/mo for 1,000 inbound emails
Not applicable; receive-only.
Modern stacks that need email-to-webhook with TypeScript.
- › Typed payloads
- › Fast delivery
- › Good free tier
- › Newer entrant
- › Node-only SDK
Features at a glance
| API | Yes |
| SMTP | No |
| SDKs | node |
| Webhooks | Yes |
| Templates | none |
| React Email | No |
| Batch send | No |
| Scheduled send | No |
| Suppressions | No |
| Multi-tenant | Yes |
| Inbound parsing | Yes |
| Event stream | Yes |
| Idempotency keys | Yes |
| Dedicated IP | No |