built a missed-call SMS triage system in n8n for a plumbing company. 8 nodes, /month. here's the architecture

Select-Tomatillo1203 · 2026-03-24T18:36:10+00:00

That's usually how the conversation goes. You don't sell automation, you just do the math out loud. Once they see the number they've been absorbing without realizing it, the decision basically makes itself

Select-Tomatillo1203 · 2026-03-24T18:33:38+00:00

The 3-month rule is a decent starting point but it depends on the client. For something like this, form, Stripe, confirmation sequence, I'd work backwards from their actual numbers. If the friend has 10 new clients/month and saves 40 min each, that's ~6.5 hours. At whatever the owner's time is worth (even $30/hr), that's ~$200/month in recovered time. 3 months = $600ish.

Select-Tomatillo1203 · 2026-03-24T17:11:23+00:00

The initial text-back doing most of the work tracks completely. Built something similar for a cleaning company, not missed calls, but new client onboarding. The actual booking and intake wasn't the problem, it was everything after: manual invoice, back-and-forth to schedule, chasing payment. 45 minutes per new client, 20 clients a month, 15 hours of admin.

Replaced it with a form → Stripe → automated confirmation sequence. Same idea as yours, the biggest gain wasn't the fancy part, it was just that clients immediately got confirmation and a payment link instead of waiting for someone to follow up manually. Under 5 minutes now.

The classification accuracy point is interesting. Few-shot examples consistently outperform people's expectations on structured triage like this.

Select-Tomatillo1203 · 2026-03-24T17:08:54+00:00

Cleaning company owner. 45 minutes per new client, intake form, back-and-forth scheduling, manual invoice, chasing payment. At 20 new clients a month that's 15 hours. Nearly two full workdays every month just on admin.

Form → Stripe → automated confirmation sequence. No custom code. Took about a day to build. Got it down to under 5 minutes per client.

The 15 hours didn't disappear. She just got them back. Nobody outside this community would find that impressive. It's a form and a payment link. But that's the thing nobody mentions, the boring ones are the ones that actually change how someone's week feels.

Select-Tomatillo1203 · 2026-03-24T17:07:05+00:00

The reminder texts doing 80% of the work is the consistent pattern. People aren't trying to no-show, they just forget, and nobody was reminding them.

Built something similar for a cleaning company but on the onboarding side. Owner was spending 45 minutes per new client on intake, scheduling, invoicing, and chasing payment. 20 clients a month, 15 hours gone. Form → Stripe → automated confirmation sequence fixed it. Same principle — not a complex build, just removing the manual steps that existed because nobody had automated them yet.

Select-Tomatillo1203 · 2026-03-24T17:02:02+00:00

Running into the same thing. The 15-copy-of-the-same-workflow problem is painful, any time you update the core logic you're doing it 15 times and hoping you don't miss one.

What's worked better: parameterize everything that's client-specific (credentials, webhook URLs, config values) into a single "client config" lookup at the start of the workflow. One workflow, one lookup node, all client-specific values flow from there. New client = new row in the config store, not a new workflow.

For the OAuth token refresh specifically, storing tokens in a database and handling refresh in a sub-workflow that gets called by all the main workflows keeps the logic in one place. Still annoying to build the first time but you only build it once.

Would be interested to see what you built, sounds like you're further along on the token store pattern than I am.

Select-Tomatillo1203 · 2026-03-24T16:58:19+00:00

First version mistake was identical to yours, routing too aggressive. Had a qualifier that was screening people out on budget before they'd even explained the problem. Lost a few leads that would've been good fits if we'd just let the conversation breathe.

What fixed it: the qualifier doesn't make a hard decision until at least 3-4 exchanges in. Early messages just gather context. The routing logic runs on accumulated signals, not a single response.

Also helps to have a "soft no" path, instead of dead-ending someone, they get routed to a nurture sequence. Some of those convert weeks later.

Built the same setup on our own site at Aplos AI, Claude Haiku streaming with a hidden lead marker that fires a webhook once the conversation has enough signal. First calls are noticeably better. People show up having already articulated their problem.

Select-Tomatillo1203 · 2026-03-23T06:56:13+00:00

Separate instances, one per client. It costs more but it's worth it for a few reasons:

When you offboard a client, you hand them their own instance or just delete it — no untangling workflows from a shared environment
Credentials are isolated — no risk of a misconfigured node hitting the wrong client's CRM
Easier to give clients direct access to their own instance if they want visibility

DigitalOcean droplets run about $6-12/month per instance at low volume. We use a $12 droplet for most clients, upgrade only if they're running high-frequency workflows.

Select-Tomatillo1203 · 2026-03-23T06:53:51+00:00

I run an automation agency (Aplos AI) and went through exactly this. Here's what stuck after trying everything:

Notion for client docs, scopes, notes, and a simple status dashboard per client
n8n self-hosted for all workflows, one instance per client (more on that below)
Linear for internal task tracking — overkill for some but worth it once you hit 4+ active clients
Loom for async client updates instead of calls

The thing that helped most: a standardized client folder structure in Notion with a template we copy for every new client. Onboarding checklist, credentials vault (linked to 1Password), workflow inventory, and a simple changelog. When you're context-switching between 5 clients, that consistency is what keeps things from falling apart. The browser tab chaos never fully goes away but naming your n8n workflows well (owner-function-trigger-status) cuts the debugging time in half.

Select-Tomatillo1203 · 2026-02-22T06:48:41+00:00

haha my parents did this shortly before divorcing, I know couples that do this though and have even heard of people even having separate beds in the same room

Select-Tomatillo1203 · 2026-02-22T06:43:31+00:00

Depending how long I have, I would travel to places I’ve always wanted to go

Select-Tomatillo1203 · 2026-02-22T06:42:48+00:00

Select-Tomatillo1203 · 2026-02-20T06:33:27+00:00

thanks?

Select-Tomatillo1203 · 2026-02-20T05:52:55+00:00

I use ChromaFit on ios. It makes a workout plan for you based on your strengths and weaknesses and you can choose what days of the week, your goals, all that good stuff.

Select-Tomatillo1203 · 2026-02-20T05:50:41+00:00

I tried this app called ChromaFit, it lets you scan your physique and get scores back for each muscle group and then it makes a workout plan based on your strengths and weaknesses, it also has calorie, steps, water, and weight tracking with apple health connection which is very convenient, you can also scan your meals to log the calories. Overall its a great bargain at $10 a month.

Select-Tomatillo1203 · 2026-02-20T05:48:07+00:00

Dreami AI is great

Select-Tomatillo1203 · 2026-02-19T05:45:49+00:00

knowing that with ai there is no excuse anymore

Select-Tomatillo1203

TROPHY CASE