agentleFS
tmolavitmolavi/n8n-agent-skills/skills/n8n-binary-data/SKILL.md

n8n-binary-data

Skill1 starsChanged 3 months agoMITView on GitHub

Use when handling files, images, PDFs, attachments, binary properties, vision model inputs, or merging binary with JSON context in n8n.

The file

Files
SKILL.md

n8n Binary & Files

Author: Taghi Molavi

Basics

  • Items can carry binary keys alongside json
  • Downstream must reference the correct binary property name
  • Some nodes clear binary — plan Merge/NoOp checkpoints

Patterns

  • Download → transform → upload/store
  • Email attachments → extract → route by mime
  • Vision: ensure model node receives binary or URL per node docs
  • For agent tools needing files, document size limits

Gotchas

  • CDN/public URL requirements for some AI nodes
  • Base64 in JSON blows tokens — keep binary binary
  • Pair context fields via Merge before multi-input consumers

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.