Webhook API – inbound email –> webhook
Email-to-JSON webhooks with built-in cron, simpler than configuring Mailgun inbound routes.

Replaces regex email parsing with AI + schema validation, but Zapier and Make already handle this.
Backend developers, automation engineers, finance/logistics teams processing structured email data
Zapier · Make · n8n
I built ParseForce because parsing emails has always been surprisingly painful.
Many automation workflows still rely on incoming emails: invoices, order confirmations, shipping notifications, etc. The usual solutions involve fragile regex rules or Zapier-style email parsers that break when email formats change.
ParseForce takes a different approach.
You create a unique inbox and define the data you want to extract. Incoming emails are parsed using AI into structured JSON and delivered to your webhook.
Example workflow:
Email received → ParseForce parses it → structured JSON → webhook to your backend.
Example output:
{ "invoiceNumber": "INV-84217", "items": [ { "name": "Valve kits", "quantity": 60 }, { "name": "Pressure regulators", "quantity": 20 } ], "total": 1284.50 }
Typical use cases:
* extracting invoice data * processing order confirmations * parsing shipping notifications * automating legacy email workflows
The goal was to make email integrations as simple as webhook integrations.
Stack:
* Node.js / TypeScript * PostgreSQL * AI-based schema parsing * webhook delivery system
I’d love feedback from the HN community.
Site: https://parseforce.io
Email-to-JSON webhooks with built-in cron, simpler than configuring Mailgun inbound routes.
Clean inbound email parsing when Mailgun and SendGrid already do this.
Email-to-JSON with schema validation and webhook delivery, but LLM extraction isn't novel.
Firecrawl adds monitoring to their 125k-star scraping infra with webhook alerts.
Useful passive monitoring, but AirNow and PurpleAir already cover this for free.
Own KumoMTA infrastructure beats reselling SES, but email-for-agents is getting crowded.