u/Boring-Shop-9424

Most people build one AI agent that tries to do everything.
I went a different route — 7 specialized agents, each with
a single job, all talking to each other inside n8n + Telegram.

The routing works like this: the main agent reads the message
and outputs DELEGATE:AGENT|task. n8n parses that with regex
and triggers the right sub-flow. Each agent has its own system
prompt and memory via Google Sheets.

Agents I have running:
- MAX — general assistant
- LENA — content writing
- SEM — image analysis (vision)
- ALICE — scheduling
- VICTOR — sales scripts
- NOVA — web search via Tavily
- MILO — data extraction

No custom code. Pure n8n nodes.

Happy to share the workflow structure if anyone's interested.

If you're new to n8n and mixing these up, here's the short version:

$json is the current item's data in the current context. Use it inside a Code node set to "Run Once for Each Item", or inline in expressions like {{ $json.email }}.

$items() is the old-school way to grab an array of items from a specific node. It still works in a lot of workflows you'll find online, but it's legacy syntax. The modern equivalent is $input.all() inside a Code node, or $('Node Name').all() in expressions — both are more explicit about which node's data you're pulling.

Rule of thumb I use: if I'm working with ONE item, $json. If I need ALL items to loop, aggregate, or compare, $input.all(). I basically never reach for $items() anymore, but it's worth recognizing when you see it in older templates.

Curious if anyone still has a real use case for $items() over $input.all() — haven't run into one myself.

If you're new to n8n and mixing these up, here's the short version:

$json is the current item's data in the current context. Use it inside a Code node set to "Run Once for Each Item", or inline in expressions like {{ $json.email }}.

$items() is the old-school way to grab an array of items from a specific node. It still works in a lot of workflows you'll find online, but it's legacy syntax. The modern equivalent is $input.all() inside a Code node, or $('Node Name').all() in expressions — both are more explicit about which node's data you're pulling.

Rule of thumb I use: if I'm working with ONE item, $json. If I need ALL items to loop, aggregate, or compare, $input.all(). I basically never reach for $items() anymore, but it's worth recognizing when you see it in older templates.

Curious if anyone still has a real use case for $items() over $input.all() — haven't run into one myself.

Quick tip for anyone writing Code nodes in n8n: stop accessing nested fields directly.

$json.field.subfield will throw the second `field` doesn't exist on some items in your batch — and with n8n that happens more often than you'd think (APIs returning partial data, webhooks with optional fields, etc).

Just use optional chaining everywhere:

$json.field?.subfield

And if you need a fallback value, stack the nullish coalescing on top:

$json.field?.subfield ?? 'default'

Saved me from a bunch of random workflow failures that only showed up on specific items, not the whole batch — which made them annoying to debug in the first place.

Anyone else have small JS habits like this that cleaned up their Code node errors?

After building 25+ workflows, here are the shortcuts that actually save time:

1. Ctrl+D duplicates a node instantly
2. Rename every node — you won't remember what "HTTP Request 7" does next week
3. Add a Set node after your trigger — keep only the fields you need
4. Use sticky notes to explain complex blocks
5. Group repeated logic into sub-workflows
6. Always test with real data, not mock
7. Save frequently used workflows as templates
8. Use Environment Variables instead of hardcoding tokens
9. Pin data on nodes during development — no need to trigger every time
10. Ctrl+Z works — but not always, save more often

What tips would you add?

Lost 3 workflows after a careless update. Nodes broke, configs got wiped, had to rebuild from scratch.

Now my rule before any n8n update:

**1.**	SSH into the server  
**2.**	docker exec -it n8n\_container n8n export:workflow --all --output=/backups/backup\_$(date +%Y%m%d).json  
**3.**	Copy the backup file off the server  
**4.**	Then update

Takes 2 minutes. Saved me multiple times since.

If you’re running n8n on a VPS — don’t skip this. The update looks smooth until it isn’t.

Anyone else got burned before adding this to their routine?

Add this after every HTTP Request node:
console.log(JSON.stringify($json, null, 2));
return $input.all();
Save a sample response in node notes. When the field disappears — you catch it immediately, not after 200 null rows in your spreadsheet.

What’s your approach to API schema drift?

Enable "Continue on Fail" on non-critical nodes.

Notification nodes, logging, data enrichment — these shouldn't kill your workflow when they fail.

Keep it OFF on payments, DB writes, core logic.
Keep it ON for everything optional.

Add an IF node after to check $json.error if you want to handle failures gracefully.

Small setting, big reliability upgrade. What other resilience patterns do you use in n8n?

Had a workflow silently die on me last week. Webhook was coming in fine, test mode showed all the data — but in production one field was occasionally missing and the whole thing crashed with "Cannot read property 'toLowerCase' of undefined".

Took me way too long to figure out because n8n doesn't always surface these errors cleanly.

Now I wrap anything critical before using it:

In expressions:
{{$json?.customer?.email || 'fallback@domain.com'}}

In Code nodes:
const email = $json.email ?? null;
if (!email) {
return [{ json: { skipped: true, reason: 'missing_email' } }];
}

Especially important if you're pulling from webhooks where the sender controls the payload — you can't trust every field will be there every time.

Anyone else validating $json fields upfront, or do you handle it with IF nodes downstream? Curious what approach people are using in 2026.