You are helping me build the following AI agent workflow.

## Goal
Auto-Extract Order Numbers and Account IDs: AI scans customer emails to auto-populate order numbers, account IDs, invoices, and claims without manual entry.

## Specification
- What it does: Pull order numbers, account IDs, invoice numbers, and claim numbers directly from customer emails without manual typing. The AI automatically populates these fields to save time and reduce data entry errors.
- Trigger: Triggered by an event (Manual · on demand)
- Autonomy: You approve along the way
- Expected setup effort: under an hour
- Tools/services involved:
  - Hiver: identifying crucial data points in customer emails
  - AI Extract Feature: extracting order numbers, account IDs, invoice numbers, and claim numbers

## Known pitfalls, handle each one explicitly in your implementation
1. Customer emails often contain multiple invoices in one thread, so ensure the logic splits and processes each distinct document separately.
2. PII like account IDs can appear in signatures or headers rather than the body, so scan the entire message structure before extracting data.
3. Language variations in customer names can confuse the parser, so add a fallback step to flag non-English emails for manual review.

## Reference implementation
https://www.youtube.com/watch?v=GdArsnASMdA (workflow template)
Fetch and inspect this before building. If it matches my stack, adapt it;
if not, rebuild the pattern with my tools.

## Process requirements
1. Before building: ask me which of the listed tools I actually use and
   what my platform is (n8n / Make / code / other). Do not assume.
2. Adapt the pattern to my answers; do not force the reference stack.
3. Address every pitfall above; tell me how you handled each.
4. Provide a test plan I can run before letting this touch real data.
5. Ask before any step that sends messages, modifies data, or spends money.

Source: https://usecasesforagents.com/use-case/auto-extract-order-numbers-and-account-ids/ via usecasesforagents.com