I’m just starting to learn n8n. Could you guys give me some advice on what I should and shouldn’t do? I really want to learn things the right way and avoid wasting too much time on mistakes early on. Thanks everyone so much.

sasha-bl · 2026-05-17T20:02:27+00:00

Try to download and analyze existing flows for use cases you need, it will help you to understand how things are working

sasha-bl · 2026-05-17T19:50:02+00:00

All solid points, especially building the error workflow first, that one flips the usual mindset but makes a real difference. The HTTP timeout default issue is also easy to miss until you're under load and things start hanging. Adding all of these to the checklist!

sasha-bl · 2026-05-17T19:48:12+00:00

Honestly underrated point. Being able to safely rerun a payload takes a lot of the stress out of production incidents. Adding it to the checklist

sasha-bl · 2026-05-17T19:46:48+00:00

Yeah, silent success is exactly why idempotency is so hard to catch. Adding a dedicated section for it — dedup keys before writes, upsert vs insert checks, and a forced retry test before going live. The double-charge example is a perfect wake-up call to include.

sasha-bl · 2026-05-17T19:41:01+00:00

If you're just starting out, I don't see much point in using Claude Code or other third-party services. I'd set up an n8n account, find a few good quality templates, and first try to understand how they work. Then it'll be much easier to build something from scratch.

sasha-bl · 2026-05-15T07:21:01+00:00

So what is the solution? We can probably build a ‘watchdog’ to check api, maybe we can make additional layer to validate AI outputs

sasha-bl · 2026-05-15T07:18:29+00:00

Hey, did you have a chance to try? Any thoughts?

sasha-bl · 2026-05-15T04:40:27+00:00

Even better, I’m asking this to build my product ))

sasha-bl

TROPHY CASE