n8n IMAP Trigger and PDF Attachments: Diagnosing Why Attachments Aren't Appearing
A community report describes an n8n workflow where the IMAP trigger fires on new mail but attachments, specifically PDFs, do not appear in the node input. This is a common integration pitfall caused by node selection, credential setup, and binary property handling.
The problem described is familiar to automation engineers: a trigger node reports incoming email but the expected file attachments are not present in the node output. In n8n there are multiple email-related nodes (Email Trigger, IMAP node, n8n-nodes-imap community node), and they differ in how they surface attachments and binary data. Common causes include using a webhook/schedule-based node that only provides metadata, credentials that limit access to full message bodies, and forgetting to inspect binary properties rather than JSON fields.
First, confirm which node you are using and inspect the raw output. The built-in Email Trigger typically exposes attachments as binary data on the workflow item under a binary property (for example binary.mimeType and binary.data). If you are using a community IMAP node that only supports polling or webhooks, it may return only headers by design. Enable debug logging and inspect the node's full execution output in n8n to find any binary keys.
Next, verify credentials and IMAP flags. Some servers expose attachments only when the full message body is requested. Ensure the node is configured to fetch the entire message, not just headers. Check node settings like 'Download Attachments' and ensure the workflow reads binary property names; if you need the file in JSON, add a Move Binary Data node or use the HTTP Request node to upload the binary content. Also confirm file size limits and server timeouts that might drop large PDFs.
For business workflows, treat this as an opportunity to harden email automation: add tests that assert binary attachment presence, implement retries for intermittent IMAP failures, centralize credential management, and prefer maintained nodes with clear attachment handling. If the community node lacks triggers, consider using the native Email Trigger or an enterprise connector for your mail provider to ensure reliable binary handling and to simplify compliance with data handling policies.
Original Source
n8n Community