inbound-email-to-records

Use it when

• Records arrive as emails: purchase orders, invoices, leads, support requests.
• Volume is up to 300 emails per hour; each email starts one run, at most 20 at the same time.
• A record should exist within 1 minute of the email arriving.

Why this design

Advantages:

• One run per email: the run holds the sender, subject, body and attachments, and a failed run names the email.
• The built-in AI steps read free text and attachments into fields, so no fixed email format is needed.

Trade-offs:

• Senders write in many formats; the extraction step needs clear field instructions and a check for empty values.
• A failed run is not retried on its own; replay it.