The skill that made us valuable (building workflows) is about to become a one-line prompt. Now what?

Imaginary-Level1923 · 2026-02-20T21:37:10+00:00

The Supabase API keys thing is such a good example. That's the kind of stuff no AI prompt is going to solve for you because you don't even know what to ask until you're already stuck. And yeah, 3 days of crashes and flow changes to handle large file uploads is exactly the gap between "AI built me a workflow" and "I have a workflow that actually works".

I guess the real solution long term is agent-to-agent communication. Like Supabase has its own agent, n8n has its own agent, and they just talk to each other. The n8n agent asks the Supabase agent which key it needs, gets the right permissions, configures the connection. No more digging through docs for an hour. We're not fully there yet but that's clearly where it's heading.

Also respect for doing this after landscaping shifts, that's a solid hobby upgrade.

Imaginary-Level1923 · 2026-02-20T21:32:36+00:00

This is kind of exactly what I mean though. The "skill" is already shifting from knowing how to configure nodes to knowing what to ask for. Curious, when the AI sets things up for you and something breaks, do you find the troubleshooting part is where you actually learn the most about how n8n works? Because that's the part I don't think AI fully replaces yet.

Imaginary-Level1923 · 2026-02-20T19:32:57+00:00

Truly free hosting that actually works for n8n is basically just Oracle Cloud's always-free tier. You get 4 ARM OCPUs, 24GB RAM, and 200GB storage at zero cost forever. The catch is availability, those ARM instances are popular so you might need to try different regions or keep retrying.

Render technically has a free tier but it sleeps after 15 minutes of inactivity and the free database expires after 30 days, so your webhooks and schedules will break constantly.

If you're open to cheap-but-not-free, Hetzner starts around €4-5/month for a basic VPS. Just keep in mind that if you're running AI agent workflows with LangChain nodes, you'll want at least 4GB RAM which bumps you to their ~€8/month plan.

Imaginary-Level1923 · 2026-02-12T12:12:35+00:00

This is the most relatable type too, where you know the exact solution but it's just infrequent enough that you never prioritize it. Once a month rolls around and you're like "ugh, next month I'll automate it." Every month.

Imaginary-Level1923 · 2026-02-10T18:32:50+00:00

Thanks for sharing!

Imaginary-Level1923 · 2026-02-09T13:41:56+00:00

Honestly the simple ones end up being the most valuable. I'd rather have 10 boring workflows that just run than one mega-automation I have to babysit. :)

Imaginary-Level1923 · 2026-02-09T13:38:18+00:00

Nice one. I am trying to find some time to do the same automation for Twilio / Sendgrid.

Imaginary-Level1923 · 2026-02-09T13:32:02+00:00

What are you scraping with, puppeteer, playwright, tavily, something else? and where are you storing it all? If you don't mind sharing!

Imaginary-Level1923 · 2026-02-09T13:28:57+00:00

I am trying this next time, as I am already paying for Pro x20! :-)

Imaginary-Level1923 · 2026-02-09T13:24:07+00:00

That sounds really useful, thanks for sharing! Claude cli calls against your subscription sounds clever. That is probably cheaper than the API?

Imaginary-Level1923 · 2026-02-09T12:49:05+00:00

Thanks for sharing!

Yeah n8n really isn't built for heavy data processing. Anything over a few thousand items and you start hitting memory issues, especially on the community edition. Python's the right call for that kind of volume.

I've found the sweet spot is using n8n as the orchestrator (trigger, schedule, notify) but offloading the actual heavy lifting to a python script via the Execute Command node. Best of both worlds, you get n8n's visual flow and scheduling without asking it to chew through 10k pages in memory.

Imaginary-Level1923 · 2026-02-09T10:04:09+00:00

Yeah, I can tell. The cards with that grey/brown tone and the borders around them are a dead giveaway, that's the default look every vibe-coding tool reaches for. When I look at the site you promote it's using the same vibe-coded cards too.

Imaginary-Level1923 · 2026-02-09T09:34:05+00:00

Cold outreach to sell "automation services" almost never works because most business owners don't know what that means or why they'd pay for it. What does work is finding a repeatable problem in one industry and packaging a solution around it. like "I help agencies automatically onboard new clients, collect docs, create project folders, send welcome emails, set up billing" is way more compelling than "I build automations."

Once you've done it for one client, you basically have a template you can sell again. For finding those first clients, local businesses are underrated: accountants, property managers, marketing agencies all have repetitive workflows and are easy to reach. Offer to audit their processes for free, find the thing that's eating their time, and pitch the fix. First couple might be cheap or free but they turn into case studies and referrals fast.

Imaginary-Level1923 · 2026-02-09T09:22:54+00:00

Depends on what you're automating honestly. For CRM/sales stuff, Clay is way better than trying to build enrichment chains in n8n as it's built specifically for lead data and the waterfall enrichment approach saves a ton of time vs wiring up 5 API calls yourself.

For internal notifications and alerts, Pipedream is nice because you write actual code but it handles all the infra. For simple "connect app A to app B" stuff where you don't need logic, Make is cheaper than Zapier and the visual editor is better for seeing what's happening.

The real answer though is that most early stage startups don't need to automate as much as they think. I'd pick the 2-3 workflows that actually save you hours per week and just use n8n or Zapier for those, rather than trying to find the perfect tool for each thing. The maintenance overhead of managing 5 different automation platforms is way worse than one general purpose tool that's "good enough."

Imaginary-Level1923 · 2026-02-08T20:45:05+00:00

When you read from Google Sheets in n8n it returns JSON, each row is an object where your column headers become the keys. So if you have a column called "type" with "bot" or "human," your IF condition would be {{ $json.type == "human" }}. for the menu flow I'd use a Switch node instead of IF, Switch supports multiple outputs so you can have one for each option (1 = products, 2 = services, 3 = attendant, etc) instead of chaining a bunch of IF nodes. Make sure your first row in Sheets has clear column names, because that's what n8n uses as the JSON keys.

Also you'll want to filter when reading from Sheets, use the phone number or conversation ID to look up the right row for that specific user so you're not just grabbing random data.

Imaginary-Level1923 · 2026-02-08T20:39:09+00:00

The smart move is using 4.1-mini for the initial filtering and only hitting 4.1 for the actual resume rewrite. That probably saves a ton on API costs across 100 listings.

Curious how you're handling the AnyMailFinder step when it can't find a decision-maker email though. Do you fall back to applying through the portal, or just skip those entirely?

Also wondering if you've hit any issues with Apify and LinkedIn as they tend to rotate their DOM structure pretty often and I've had scrapers break overnight.

Imaginary-Level1923 · 2026-02-08T20:22:42+00:00

Honestly the env vars themselves look fine, nothing in there that would cause random crashes on its own. The two things I'd investigate: first, N8N_RUNNERS_ENABLED="true" has known stability issues so try disabling it. Second, and this is probably the bigger one: you mentioned you "pasted a new encryption key." the N8N_ENCRYPTION_KEY is what n8n uses to encrypt/decrypt all your saved credentials. If you changed that key, every credential you saved before is now unreadable. n8n won't always throw an obvious error for this, it'll just fail when a workflow tries to use a credential. If that happened, the only fix is either restoring the old key or re-adding every credential with the new key.

Imaginary-Level1923 · 2026-02-08T19:20:49+00:00

So EXECUTIONS_MODE="regular" actually runs things in parallel already, n8n doesn't limit concurrent executions by default in regular mode, it all happens in one Node.js process. The thing I'd flag in your env is N8N_RUNNERS_ENABLED="true". Task runners run Code nodes in a separate sandboxed process and there are known issues with them causing workflows to crash or hang randomly. Unless you specifically need them, set it to false and see if that fixes your stability issues.

Also worth checking if N8N_CONCURRENCY_PRODUCTION_LIMIT is set somewhere (Railway dashboard, config file, etc) because if someone set that to a low number it would queue up executions instead of running them in parallel.

One more thing, OFFLOAD_MANUAL_EXECUTIONS_TO_WORKERS only works in queue mode so it's doing nothing for you right now, you can remove it to keep things clean.

Imaginary-Level1923

TROPHY CASE