When an email is sent to an organization's ingestion address and it contains no valid business-document attachment, Docupath processes the email body itself as the document. The body runs through the same capture, classification, and extraction pipeline as any other document, so content sent in the message body is captured rather than lost.
How It Works
This behavior applies only to the Single Primary Document with Optional Attachments ingestion address. When an email arrives at that address, Docupath decides what to treat as the document using the following precedence:
A valid business document is attached. The attachment is used as the document. The email body is kept as a read-only reference (the Email Body panel) and is not processed.
There are no attachments. The email body is processed as the document.
The only attachments are non-documents (for example logos, signatures, or images with little or no readable text). These are dropped, and the email body is processed as the document.
The email body is empty and there is no valid document. The email fails as before, with a "does not contain enough recognizable text" result.
When the email body is processed as the document, it goes through the same capture, classification, and extraction pipeline used for any document, and the resulting document is named Email.
The Multiple Primary Documents address never turns the email body into a document. On that address, each attachment is processed as its own document, and non-document attachments simply fail on their own.
Supported Configurations and Options
The way the email body is handled depends on which ingestion address the email is sent to.
Ingestion address | Email body behavior |
Single Primary Document with Optional Attachments | The body is processed as the document when the email has no valid business-document attachment. When a valid document is attached, the body is kept as a read-only Email Body reference and is not processed. |
Multiple Primary Documents | The body is never turned into a document. Each attachment is its own document, and non-document attachments fail on their own. |
Other Technical Specifications
Document name: A document created from the email body is named Email.
Supported body formats: Both HTML and plain-text email bodies are supported. They are converted for OCR and extraction.
Viewer presentation: When the email body is the document, it appears in the document viewer as the document itself, with no separate Email Body panel and no attachments listed. When there is a real document, the email body still appears alongside it as the read-only Email Body panel.
Empty-body outcome: If the body is empty and there is no valid document, the email fails with a "does not contain enough recognizable text" result.
Notes
Sub-organization routing behavior is unchanged. The email body is not used for routing; documents are still routed to sub-organizations by Primary Party matching, whether the document came from an attachment or from the email body.
Non-document attachments such as logos, signatures, and images with little or no readable text are dropped rather than processed. On the Single Primary Document with Optional Attachments address, this is what allows the email body to become the document when no valid attachment is present.
Known Limitations and Edge Cases
The Multiple Primary Documents address never processes the email body as a document, even when no valid attachment is present.
An email with an empty body and no valid document fails; there is nothing recognizable to process.