Why does a Zoho Flow email trigger truncate forwarded emails or drop attachments?

Zoho Flow's email trigger is built to parse incoming messages into fields, not to carry full email threads. Forwarded emails nest the original inside quoted content, which can be cut or flattened, and attachments are subject to size and type limits. For reliable results, trigger from a Zoho Mail or other mailbox connector, or forward originals as attachments.

When you email a Zoho Flow address, Flow reads the message and exposes parts like sender, subject, plain body and attachments as variables. Forwarded messages are messy. Different mail clients wrap the original in different ways, sometimes as HTML quotes, sometimes inline, sometimes as an attached message file. Flow may take only the top part or a plain-text version, which looks like truncation.

Attachments add another limit. There are size caps for the trigger and for the app you send the file to, and inline images or embedded message files are not always treated as normal attachments. Very large emails may arrive with the body but without files. The exact limits change, so check Zoho Flow's current help pages.

Practical fixes help. Use a mailbox trigger from Zoho Mail or Gmail instead of the forwarding address, so Flow reads the original message directly. If you must forward, forward as attachment, or set an automatic forwarding rule rather than manual forwarding. Keep files within the limits, and log the raw body in a test step so you can see exactly what Flow receives.

Written by Flowpeak, a Zoho implementation partner. Zoho pricing and features change, so confirm current details on the official Zoho site. Free checklists | Ask us a question