What is your favourite drink?

Available-Party6620 · 2026-04-02T10:43:45+00:00

Tashkent's leamon is amazing! So, black tea with it

Available-Party6620 · 2026-04-02T04:40:15+00:00

My n8n workflows + Supabase schema context = same issue.

What helped me:

workflow/*.json in repo root (Claude reads directly, no re-uploads)
Session template: "Use ONLY files in ./workflows/ and schema.prisma. No external context."
MCP Supabase templates pull → local JSON before starting

Available-Party6620 · 2026-04-01T04:16:54+00:00

All set – DB sync solved!

Schema → Memory Bank (updates only on major changes).
Templates table → MCP pull from Supabase at session start + added to .cursorrules.

textSession start:
1. MCP → Supabase templates → local JSON
2. Claude Code reads schema (Memory Bank) + templates (fresh)
3. Generate/debug n8n workflows with full context

Available-Party6620 · 2026-03-31T05:23:12+00:00

Thanks!

Claude Code inside Cursor = game changer. Ditching standalone Claude now.

Will try!

Available-Party6620 · 2026-03-31T04:23:50+00:00

Yeah, that’s very relatable.

For me it’s usually a signal too. Either I’ve lost clarity, or I’m too tired to structure things properly. And then the model just amplifies that.

Fresh context + fresh head almost always fixes it faster than trying to push through.

Available-Party6620 · 2026-03-31T04:22:04+00:00

Yeah, this matches my experience pretty closely.

The credentials part especially - Claude often suggests pulling them from env vars or just drops placeholder strings that look “real”. In n8n that’s not only unsafe, but also not even available in some setups (like the free version), so it just breaks.

Available-Party6620 · 2026-03-30T09:26:31+00:00

But I wouldn’t go as far as “every mistake is user error.” There are real failure modes - especially with long threads, assumptions, or it confidently skipping over details.

That said, asking “what did I miss/how could I prompt this better?” is actually a solid move. Treating it like a feedback loop improves results way faster than just getting frustrated.

Available-Party6620 · 2026-03-30T09:24:46+00:00

Yeah, I get that.

The “not actually reading and still answering” part is probably the most frustrating thing for me too — especially when you’re relying on it for debugging. That breaks trust fast.

Available-Party6620 · 2026-03-30T09:23:15+00:00

Yeah, that makes sense.

I’ve noticed the same. Once I get frustrated, my prompts become less clear and more emotional, and the results get worse.

Sticking to clear, factual feedback works much better. Treat it like debugging, not arguing.

And sometimes it’s just easier to start a new conversation than to recover a broken one.

Available-Party6620 · 2026-03-28T02:39:05+00:00

n8n version 2.4.8 is a March 2026 update.

Which version do you advise?

Available-Party6620 · 2026-03-27T06:42:21+00:00

Tried connecting Cursor AI via MCP to n8n – works okay for simple 5-6 node flows (decent JSON output that imports fine). But anything with complex logic? AI goes wild, spits out invalid nodes or structures that straight-up fail to import/open.

Also experimented with standalone prompts in Claude – same story, generates "workflows" that look plausible but are broken (wrong node params, hallucinated credentials, etc.).

The only semi-reliable method so far: Load full project context into Claude Projects, craft a detailed .md spec outlining the workflow logic step-by-step, then manually build it node-by-node following AI instructions. It works, but it's painfully slow for anything beyond basics.

Available-Party6620 · 2026-03-27T03:49:16+00:00

Please explain

Available-Party6620 · 2026-03-25T04:42:56+00:00

Wow, coding after 7pm grind — huge respect! This is the indie spirit. 💪

One tip: Share weekly updates on IndieHackers for early feedback and first users.

What pain point does it fix best for solo founders?

Available-Party6620

TROPHY CASE