Every plan, with AI assists every 30 days
Let AI write the patterns, then read them yourself
Writing patterns is the slow part of reading email into fields. Pick a few of an endpoint's emails that look alike, say what you need, and AI proposes the fields, or a whole layout with the condition that picks its emails. Every pattern is RE2 you can read and change, and it is tried on each email you picked before you see it. The AI only writes patterns: it never reads your mail as it arrives.
Set it up
- 1
Pick the emails
Under the endpoint's Layouts, choose Draft a layout with AI, or Find a field with AI in an open layout, and pick up to 5 of its emails that look alike.
- 2
Say what you need
A field's name and what it is, or for a whole layout, which values matter if you want to say.
- 3
Agree to send them
Tick the box to send those emails to Anthropic, our AI provider: their subject, sender, recipients, text and headers, never attachments. Nothing is sent until you tick it.
- 4
Check the proposal
Propose shows each pattern with the value it found in every email you picked. A pattern that misses one of them, or does not compile, is never shown.
- 5
Add it, then save
Add field or Add this layout puts it in the editor. Nothing is saved until you save the layouts.
Every setting, in full: AI setup in the layouts docs
What the AI sees
Only what you send with the box ticked, to Anthropic, our AI provider. We do not keep what is sent; a record of each ask holds who asked, when and how it went.
Sent, when you ask
- The 1 to 5 emails you picked, from the endpoint's own
- Their subject, sender, recipients, text and headers
- What you asked for: a field's name and what it is
Never sent
- Attachments, of any email
- Emails you did not pick
- Mail that arrives later: the patterns read it, not the AI
Anthropic is on our list of subprocessors.
How a proposal is checked
Whatever the model answers is treated as a draft. Each pattern is compiled with RE2 and run on every email you picked, and only fields that find a value in each of them come back, shown with the value they found. A layout comes with a match condition that every picked email meets.
The result is the same kind of layout you would write by hand, so you can read it, change it and try it on an email in the preview. Start from a ready-made layout instead when your sender has one.
What to know
- 1 to 5 of the endpoint's own emails per ask
- Subject, sender, recipients, text and headers sent; never attachments
- Sent only once you tick the box, from a signed-in session, never an API key
- Every pattern compiled with RE2 and tried on each email
- Nothing saved until you save the layouts
- Never run over mail as it arrives
- 5, 20 or 500 assists every 30 days, by plan
- An ask that fails on our side or the AI's is not counted
Plans, prices and limits: Pricing
Questions
More on mailhooks.cc
Google Sheets
A row per email or per line item, in a spreadsheet you pick.
File drops
CSV, XML or JSON files on your SFTP, FTP or S3 server.
Your own domain
Mail to orders@inbound.acme.com, sent to the endpoints you choose.
Zapier and Make
Start a Zap or a Make scenario with each parsed email.
Ready-made layouts
Orders, bookings, receipts and reports from the senders you already use.