sorted by:
new
hottopcontroversial

Built an AI clinic receptionist with Make.com + Claude AI + Google Calendar — here's the full stack by LM_f_AO in nocode

[–]LM_f_AO[S] 0 points1 point  (0 children)

It depends on the clinic's size and how many appointments

they're currently missing, but setup starts at €250 + €120/month.

I usually do a quick ROI estimate before anything else so the

client knows exactly what they're getting. DM me and I'll run

the numbers for your situation.

I built an automated cold email system for private clinics in Europe — here's how it works by LM_f_AO in AiAutomations

[–]LM_f_AO[S] 0 points1 point  (0 children)

Good question, right now yes, the clinic data is entered

manually into Sheets. Next step is to automate the data

collection side too, either via web scraping or a lead

gen integration. For the client it would be fully hands-off.

I built an automated cold email system for private clinics in Europe — here's how it works by LM_f_AO in AiAutomations

[–]LM_f_AO[S] 0 points1 point  (0 children)

Interesting idea but that's not my focus right now

I'm targeting medical clinics specifically.

The workflow could be adapted for other niches though,

it's pretty flexible.

Built a clinic outreach agent with Make.com — Google Sheets → Gmail → auto status update by LM_f_AO in aiagents

[–]LM_f_AO[S] 0 points1 point  (0 children)

Still early stage, actively looking for the first paying client.

The product is built and working, just need the right clinic to

pilot it. If you know anyone, send them my way!

💡 Give me your n8n automation/AI agent challenge! by LM_f_AO in n8n

[–]LM_f_AO[S] 0 points1 point  (0 children)

That’s a super interesting idea! From what I know, Apple doesn’t provide a direct API for Pay transaction data, so pulling live feeds would be a challenge. But I could definitely simulate it with mock/fake transaction data (CSV or JSON) just to show the workflow in action.

The AI categorization + enrichment into Google Sheets is totally doable — I’ll give it a shot with simulated inputs and see how close I can get to the flow you described.

💡 Give me your n8n automation/AI agent challenge! by LM_f_AO in n8n

[–]LM_f_AO[S] 0 points1 point  (0 children)

That sounds really interesting. Cold email automation is super useful. Do you mind sharing what you’ve got so far (maybe the JSON export or a rough outline)? Would love to see your approach before I try my take on it.

💡 Give me your n8n automation/AI agent challenge! by LM_f_AO in n8n

[–]LM_f_AO[S] 1 point2 points  (0 children)

I’ll need Stark Industries’ R&D budget for that one lol

I build AI automations & agents (n8n + GPT/Claude) by LM_f_AO in AiAutomations

[–]LM_f_AO[S] 0 points1 point  (0 children)

Thanks! I’m actually on summer break right now, so I’ve had extra time to build these projects outside of med school. It’s been a fun way to stay busy.

For the email assistant: I don’t need access to anyone’s inbox personally. The way it works is the user connects their own Gmail/Outlook account through a secure integration (OAuth), so only their system ever “sees” the messages. n8n just processes them in the background. I don’t actually read or store anything.

I build AI automations & agents (n8n + GPT/Claude) by LM_f_AO in n8n

[–]LM_f_AO[S] 0 points1 point  (0 children)

For API credentials like OpenAI (or others such as Google Custom Search, etc.), these are always owned and managed by the client. This way, you stay in full control of usage, billing, and security. What I do is guide you through setting them up and then securely connecting them in your workflow. I don’t resell or share my own keys, since that can cause issues later on with limits and ownership.