n8n email has no attachment? Trace the file data

An n8n email can send cleanly and still miss the one thing the recipient was waiting for: the document. For a business sending an onboarding pack, report, booking confirmation or signed form, a green execution is not a complete handover.

Abstract workflow nodes tracing a missing document attachment

Start with three pieces of evidence:

  • the file exists where it is created or downloaded;
  • the file reaches the sending node as file-type data;
  • an approved internal recipient can open the received document.

A filename sitting in JSON is not proof that an attachment is available. It may tell you that a document ought to exist. It does not mean the email node has the file data needed to attach it.

Start with one harmless document

Use a synthetic file with a distinctive name, such as test-onboarding-pack.pdf. Run the same route used for the real email, but do not pass a genuine customer document around while you are diagnosing the fault. It creates needless exposure and muddies which execution produced which result.

Find the producer first. It may be a download step, file-read step, document generator, or a node that turns content into a file. Inspect its output and note the binary property name carrying the document.

n8n treats file-type information as binary data, separate from JSON, and its official binary data guidance explains why the binary property name must match the file-consuming node’s expected input.

Where an attachment usually goes missing

The weak point is commonly a transformation between file creation and sending. A workflow may download a PDF under a binary property called data, then pass through a Code node or a record-shaping step that creates a fresh item containing only JSON. The email body can still mention test-onboarding-pack.pdf. The email can still send. The actual file has already left the route.

For an illustrative onboarding workflow, the message might add the recipient’s name and refer to an attachment by filename. If the reshaping step does not retain the binary property, the sending node receives a recipient, subject and body, but no corresponding document. That is a technically successful incomplete handover.

n8n email attachment binary data missing usually means either the file was not retained through a later node, or the sender is configured to consume a different binary property from the one that arrived. Verify the binary property at the producer, after each transformation and at the sender, then send the synthetic file to an approved internal mailbox and open it.

Follow the file, not the reassuring status

Work forward from the producer one connection at a time. In each execution view, inspect whether the binary property remains on the item, whether the file name and type still look right, and whether the route has changed item counts.

Record a few boring details as you go. They save a lot of speculative edits later.

  • the node name and execution branch;
  • the binary property present on the item;
  • the displayed filename and file type;
  • the item count before and after the transformation;
  • the property expected by the next file-consuming node.

Branches and merges deserve particular attention. A route that builds an email body may preserve JSON neatly while losing binary data. Likewise, several incoming items can mean the recipient details sit on one item and the attachment sits on another. That is not necessarily an attachment-retention problem. It may be a record-linking problem instead.

If the document is attached to the wrong person, rather than absent altogether, keep that diagnosis separate and use the guide to tracing wrong customer data item linking in n8n. Trying to repair both failures at once is a decent way to lose the evidence for either.

Match the email node to the file it receives

Open the installed email node and inspect its attachment setting against the final item entering the node. Node fields and labels can differ by version and provider, so do not copy a forum setting blindly. Check the options available in the version actually running.

The attachment input must point to the binary property containing the file, not to a JSON field holding a filename, path or download URL. A file reference is metadata about where a document may be found. File-type data is the document available for the sending node to attach.

Confirm the filename as well as the property name. A sender pointed at data when the final item contains attachment will have nothing useful to attach. Equally, a property can exist but hold a different file than the one you intended to deliver.

Run a controlled receipt check

Once the sender configuration matches the arriving binary property, send only to an approved internal recipient. Use a mailbox separate from the sending account where possible. Then inspect the received message, download the document and open it.

A paperclip icon is encouraging, but it is not the finish line. A zero-byte or corrupt file still fails the handover. Keep the execution reference, synthetic filename and result in the workflow notes, especially where the workflow handles onboarding, fulfilment or other customer-facing documents.

For wider workflow handover work, a business automation delivery review can define acceptance checks around test data, approved recipients and operational ownership. If an attachment failure needs an alert, the notification should identify the affected customer journey and who needs to act. The guide to assigning workflow failure alerts to an owner covers that boundary.

The repair route worth using

  1. Create or download one synthetic file with a unique filename.
  2. Run the exact email route manually.
  3. Inspect the binary property at the producer and after every transformation.
  4. Confirm the final email node expects that same property.
  5. Send to an approved internal recipient only.
  6. Download and open the received document before returning the route to customers.

Treat the attachment as part of the deliverable that must be verified. The email status is merely evidence that a message left the system. It is not evidence that the promised document reached anyone in usable form.

Share a redacted execution and a synthetic attachment for a workflow review.