Send email with attachment

Questions
1

Describe the problem/error/question

I am trying to automatically send an email via Gmail that includes an attachment. The attachment is stored in a folder, and all necessary information for sending the email (e.g., recipient address) is contained in the file name and an additional list.
The workflow reads this data correctly and automatically inserts the appropriate email address into the Gmail node.
Sending the email works without any issues as long as there is no attachment.

However, as soon as I add a file as an attachment, the process fails with an error

What is the error message (if any)?

The item has no binary field ‘Bericht’ [item 0] (item 0)

Check that the parameter where you specified the input binary field name is correct, and that it matches a field in the binary input

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
2

Fix Steps:

1. Check the Binary Field Name

Open your Gmail node → Attachments → Binary Property field.
If it says something like:

Bericht

:backhand_index_pointing_right: Change it to exactly match your binary key name from the previous node (usually it’s data, attachment, or file).

You can find the correct name by:

  • Running the previous node alone

  • Opening “Binary” tab in the output

  • Copying that field name

2. Example Working Setup

Let’s say your Read Binary File node outputs:

Binary:
  data

Then in the Gmail node, set:

Binary Property: data

:white_check_mark: That’s it. Gmail will now correctly attach your file.

3. Common Mistake

If you used a Move Binary Data node, sometimes the name changes (e.g. from data → Bericht).
You can fix that by either:

  • Matching the name in Gmail node, or

  • Renaming it back using Move Binary Data.

4. Bonus tip (for loops or multiple emails)

If you’re looping through multiple files:

  • Use Split In Batches before Gmail node

  • Add a short delay (optional)This ensures each file gets its correct recipient and attachment.

WORKFLOW:–

3