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
nikola470•1h ago
The idea for ParseForce came from repeatedly dealing with workflows where important data only arrived via email.
Most existing solutions rely on regex or fixed patterns, which tend to break when email formats change. That becomes a constant maintenance problem.
The approach here is a bit different: instead of matching patterns, you define the schema you want (for example invoiceNumber, items, total, etc.) and the system extracts the data into structured JSON using AI.
The goal was to make email integrations feel more like webhook integrations.
Curious how others here are currently handling email parsing in their systems.