An email arrives with a purchase-order PDF and a signature containing two images. The automation saves three files into the document library, and the downstream extraction step tries to read the logo. Before adding more AI processing, define which attachments the business actually wants to accept.

Inspect attachment metadata before copying content

Use a redacted example message to inspect the actual trigger or action output in your flow. Identify the file name, content type, size and inline indicator. Microsoft’s Office 365 Outlook connector reference documents an Is Inline property and explains that Include Attachments controls attachment content rather than whether metadata is returned.

Property names and output structure vary across operations and versions. Select the field from the operation you actually use and inspect its run output; do not paste an expression from a different connector without checking the payload. Test missing or unexpected metadata as a review case rather than silently assuming a business document.

Agree a business intake rule

An inline image is commonly part of a message body, such as a signature. Microsoft Graph’s attachment resource documentation defines the inline flag and distinguishes file, item and reference attachments. An embedded email and a linked cloud file therefore need an explicit handling decision; neither should be treated as an ordinary PDF automatically.

For a PDF-only purchase-order inbox, the rule might exclude inline attachments and admit approved PDF files for further validation. That is an example to agree with the process owner, not a universal setting. A supplier could place a legitimate document image inside the email body. Route that exception for review so the business does not lose the order.

Do not use a name such as “logo.png” or a small-file threshold as the only decision rule. Suppliers can change signature names, and a valid business file can be small. A filename extension is also not proof of safe or valid content. Keep the organisation’s malware controls and file validation in the intake path.

Make skipped and failed items visible

  1. Build test messages with a PDF plus a signature, an inline document image, multiple PDFs, a forwarded message and a cloud-file link.
  2. For each, record which items should be accepted, skipped or sent for review. Compare the actual saved files with that expectation.
  3. Fail the file retrieval and storage steps deliberately in a test environment. Confirm the flow does not report a document as processed when no usable file was saved.
  4. Keep the message and attachment references needed for support, without copying unnecessary private email content into logs.

The failed-write exception guide covers misleading completion messages. Once intake is reliable, use the AI document extraction validation guide to plan checks on the extracted business data.

Review your email attachment workflow

ITZ’s business workflow automation service can help define intake rules and exception ownership. Describe the business documents your inbox should collect.

Bring redacted sample messages and the intended destination. Discuss filtering, content validation and recoverable failures before expanding the automation. Review Your Email Attachment Workflow