Parsers

Ask for fields.
Get fields.

Tell GhostParse what you need from an email (an order number, a total, a tracking code) and every email to that address arrives with it already pulled out, typed and ready to use. Start from a ready-made parser for the email shops get every day, or describe your own.

Start free See the library

tracking@yourshop.com → parser “Royal Mail” → your stack

The email

From: Royal Mail <no-reply@royalmail.com>
Subject: We've delivered your item

Hi Alex,

We delivered your item TT482910374GB
today at 11:42.

Your item was left in your porch,
as requested.

Sent from: Fernhill Roasters
Track it: royalmail.com/track/…

What your app receives

"extracted": {
  "parser": "Royal Mail",
  "fields": {
    "carrier": "Royal Mail",
    "tracking_number": "TT482910374GB",
    "status": "delivered",
    "delivered_at": "2026-10-11",
    "delivery_location": "Porch",
    "retailer": "Fernhill Roasters",
    "estimated_delivery": null
  }
}

How it works

A parser per address.

Give an address a parser, and each email to it is read before it's delivered. The fields arrive in data.extracted on your webhook, and in Slack, Teams, Google Sheets, Make and n8n, where you can use them like any other value.

Rules parsers

For emails that always look the same: take the text after a label (“Order number”), between two markers, or matching a pattern. They run on our servers in a time-limited sandbox, and the email is sent nowhere else.

AI parsers

For everything else: describe each field in plain words (“The tracking number”, “Is the customer asking for a refund?”) and Claude, Anthropic's AI model, reads the email like a person would. It copes with different layouts, tables, free text and other languages.

Typed, every time

Each field is a string, number, whole number, true/false, date or list, and every field is always there: null when the email doesn't contain it. Your code never has to guess.

Never blocks mail

If a parser fails (a rule takes too long, the AI is unavailable, your daily limit is reached) the email is still delivered, with the reason in error.

Route on the result

Send emails to different places by what was found, with routing rules: delivered parcels to a sheet, failed deliveries to Slack.

Try before you use it

Paste an email into the parser's page and see exactly which fields come out, before it touches real mail.

Ready-made parsers

The email shops get every day, already understood.

Couriers, marketplaces, payment providers, suppliers and customers. Pick one on the Parsers page and it's copied into your account, ready to use and yours to change.

Suggested for you

GhostParse looks at which companies have emailed your addresses in the last 30 days (Royal Mail, Etsy, PayPal…) and shows their parsers first, marked “You get these”. Only sender domains are compared, never the emails.

One click

Choose Use. The fields, their descriptions and the instructions for the AI are copied into a new parser in your account.

Make it yours

Rename it, add or remove fields, add your own instructions (“Our order numbers start with FR-”), then choose it for an address on the Domains page.