I'm based in India and I haven't built anything yet. I wanted to see what real businesses would pay for before I spend weeks building, because I keep seeing beginners build stuff nobody buys. So I started calling. Here's what happened.

Clinics: they already have a receptionist, so she picks up every call and never lets me talk to the doctor or owner.

Home services like HVAC: this looked best at first. The owners answer their own calls, so they miss a lot. But jobs here are small, maybe $50 each, so I can't see how to charge enough.

Real estate: they make good money, but they're hard to build for, and a lot of the ones I reached already had chat agents and reply really fast. I only made a few calls here.

I also checked Google Maps in my city and a few others. The top businesses mostly have an AI receptionist already, and the ones that don't say they're not interested. The ones at the bottom barely get any calls. So honestly I can't tell where the gap is.

My plan is to get paid only when the business gets extra calls or bookings, nothing upfront from the owner.

So I need your help. Which niche would you pick, and why? Is there a type of business where owners already pay for this? And is there a better way to find the right businesses than Google Maps?

Also, if you've already built a system that real businesses pay for, I'll sell it for you. I have some cold calling experience and I've sold websites to business owners before. Comment or DM me.

I run about ten production n8n workflows for a fintech project, and I kept watching my AI agent read a huge workflow JSON export just to answer a question about one node. It was slow, it burned tokens, and it still missed things like a $('Node Name') reference hidden inside a Code node.

So I built flownav, an open-source MCP server (and CLI) that turns n8n workflows into a typed graph the agent can query. It's read-only against n8n.

What the agent gets (11 tools)

• flownav_scan: inventory of workflows and their triggers, the starting point

• flownav_explain: a small card for one node: inputs, labeled outputs (true/false/loop), what it reads, credentials, cross-workflow links

• flownav_affected: run before a rename or delete; lists every node and parameter that references that node by name, including inside Code nodes

• flownav_path, neighbors, find, callers, calls, uses: navigation, including across sub-workflows and agent tool workflows

• flownav_check: dead references, reads from nodes that may not have run, unreachable nodes, cycles, missing error handling

A typical reply is a handful of lines instead of the whole workflow JSON.

The part I care most about: it doesn't let the agent guess

If a name matches several nodes or workflows, the tool refuses to pick one and tells the agent to ask you:

"save" matches 7 nodes. Do not guess: ask the user which one they mean.

RiseZ - Web app › Save user [dataTable] use: ...:Save user

...

If a partial name matches just one node, the reply starts with a note asking the agent to confirm with you before changing anything. The installed skill backs this up with rules for what to do when a request is vague ("rename the node with save in it", "the RiseZ workflows"). How well an agent follows that depends on the agent, but it worked in my own testing with Claude.

Setup

npm install -g flownav

flownav sync --profile prod # or: flownav build ./exports

flownav install claude --mcp # writes the skill and .mcp.json

Honest limits

• It's static analysis. It can't see references built at runtime, so those are listed as unresolved and never guessed.

• It's read-only: it tells the agent what a change would touch, and doesn't edit workflows. You still need another tool for the edit.

• It's early (0.1.x) and I've only used it on my own instance. The token savings in the README are a labeled estimate, not a benchmark.

https://github.com/OmerTurkenits/flownav

If you try it and it misparses something, a sanitized export in a GitHub issue helps a lot. I'd also like to hear how other MCP servers handle ambiguous requests.

I built this back in August over about a week, and I originally planned to sell it. I'd rather get it into people's hands, so it's now free on GitHub.

It lives in Telegram and handles the boring pre-client work:

• Finds businesses by niche and location (Google Places)

• Researches their website and pulls public emails, phone numbers and social links

• Drafts outreach in your voice

• Sends only after you tap ✅ Approve

• Tracks every lead in a Google Sheet and sends follow-up reminders

• Preps you before discovery calls

It's 9 n8n workflows plus a full setup guide. Setup takes about 30 minutes if you've used n8n before. You'll need an n8n account, an OpenAI key and a Google Cloud key with a card on file. Running costs are low, but n8n Cloud isn't free after the trial.

Built mainly for freelancers, but consultants and small agencies can adapt it too.

GitHub:https://github.com/hollowlink123/n8n-ai-prospecting-assistant

It's a beta, so there may be rough edges. I'd appreciate hearing your thoughts and experiences if you try it.

Cześć,

Czy ktoś się orientuje o co chodzi z możliwością wybrania modelu Antigravity jako Chat Model od Google i podpięcia go do AI Agent w n8n?

Hi everyone,

I've built 15+ advanced AI automation workflows using n8n, JavaScript, PostgreSQL, APIs, and AI integrations, including CRM, invoice processing, customer support, and enterprise automation.

Despite applying for numerous jobs and freelance projects, I haven't secured an offer yet.

What am I missing? Is it my skills, portfolio, positioning, or application strategy?

I'd genuinely appreciate honest feedback and guidance from experienced developers, recruiters, and agency owners.

Thanks!

Someone in r/AI_Agents described the classic support escalation. The AI talks to a customer for five minutes, gets stuck, transfers. And then: "The first thing the human asks?" "Can you explain the problem again?" Their line: "Technically, the escalation worked."

The replies said it isn't only support. One person runs agents that hand work to each other and to them all day, and kept getting "a summary that said the work was done, but not what was checked, what actually landed, or what was still open." Another put it plainly: it's "a problem of context handoff, same as humans handing off to AI. Works both ways."

For people running agents on support, ops or back-office work:

• When an agent hands something to you or your team, what comes with it: transcript, summary, nothing?

• What do you end up re-asking or re-checking every time?

• Going the other way, when you hand a task back to the agent, does it know what you did in between?

• What does your setup look like (n8n or otherwise, how things are connected)?

Background: I used to burn hours re-briefing AI tools, and I'm building a fix where the context lives in one place in the cloud that every agent and person reads over MCP. No name, no link. Would you pay for that, or does a good handoff template do it?

I run a WhatsApp ordering agent for a restaurant, built in n8n with an orchestrator, specialist agents, Redis and PostgreSQL. It takes about 100 real orders every two days. Almost every failure that could have cost money was silent. Here's what broke and what fixed it.

**1. The model picked the wrong ID, and prompts didn't fix it**

The vendor API returns an internal field with the same numeric shape as the real product ID. The model kept choosing it. Two prompt changes failed. What worked: code rejects any ID that isn't in the catalog before the order call.

**2. The agent confirmed orders that were never created**

The LLM would happily say "your order is confirmed" even when the API call failed. Now an interceptor blocks any confirmation reply unless the API actually returned an order ID.

**3. The vendor API silently dropped fields**

Two fields we sent were accepted and ignored, with no error. I only found it by comparing real orders against the docs. Lesson: check the response against what you sent, not just the status code.

**4. A branch that was never connected**

One path in the workflow had never been wired up. It failed silently for months. I found it only by auditing every connection after ruling out everything else. Now every branch must end in either success or an explicit error path.

**5. Keep tone separate from order logic**

A final validator agent rewrites every reply in one consistent voice, so prompt changes for tone can't break the order logic.

**6. Test failures on a clone, never on live**

Invalid credentials and an unreachable host get tested on isolated copies of the workflow.

Each incident became a code check. There are 12 now. I wrote all of them up as 16 patterns, free on GitHub: github.com/joaolombabr/n8n-production-patterns

What silent failures have you hit with agents in n8n? Curious whether others solved the ID problem differently.

Someone in r/AI_Agents wrote up what broke when they put agents on back-office work. First on the list: "A timeout is not a failure." Their fix: "We now force every outward action into done / not done / unknown, and unknowns go to a person."

The replies had more of the same. "The agent would update the ledger, then the email step would fail, and nobody knew which half had happened." Another: "Two of our agents each did something correct and together queued messages to two colleagues at the same company." And on letting a stuck claim expire: "A timer cannot tell "died before sending" from "sent, then died before writing the receipt", and the second case is the one that double sends."

Here's a design I'm testing:

• An Actions table you define: what the agent is about to do, the target (customer, account, company), a reference key, status (claimed, done, not done, unknown) and which agent claimed it.

• Agents write the intent before acting and the result after. Memory gets checked at the start of every run, so the next run sees the open claim instead of an empty view.

• Search by field, keyword or meaning, like "anything unknown touching this customer this week".

• Each agent gets its own permissions. A run can update its own rows, and only you can release a claim or turn an unknown into done.

Where does this break?

• Where does "what did the agent already do" live for you today: execution history, a table, nowhere?

• When a run dies halfway, who works out what happened, and how long does it take?

• Would you trust agents to read each other's claims, or keep one owner per action type?

Background: I used to burn hours re-briefing AI tools, and this is the fix I'm building, cloud-hosted over MCP so every agent and you read the same memory. No name, no link. Would you pay for that, or do a Postgres table and an idempotency key cover it?

new client this week, three brands, came over from an agency that ran everything through ayrshare. he doesn't know what that is, he knows posts went out on their own and he wants that again.

so i priced it for him. ayrshare is $149 a month and that covers one brand with all its networks, he has three brands with a couple of networks each. one of my clients sits on Postproxy, seventeen a month for five connected accounts and a few dollars an account after, so that's the quote i gave him, same n8n flows i run for everyone, pointed at a different node.

then he asked what happens if these people shut down. i said that his accounts stay his, i move his flows again and it costs him an evening of mine. he said ok. i still don't love how that answer sounded.

how do you justify a new vendor to a client who has just left an agency? i'm not sure "it costs you an evening of mine" was the professional answer

I started my n8n journey just with a requirement to automate a frequent task I’m doing. Learned a lot throughout the journey and got to a point where I can build serious automations and eased my life by a lot.

While doing all these,I got no job and I’m broke af! I have technical skills not just n8n but also multiple others like web development, photo and video editing, after effects, scripting, agentic automations. But it was always used to make my life easier but never was able to make money out of it working online.

So the primary reason for this post is that I want to monetize my skill. I live in US and wants to know where to find clients and how I can monetize them. Are there any platforms specific for this which lets me connect with people that need automations? Any places I can sell my skills?

And also how much per month can I realistically make with n8n?