Looking for n8n developer to finish AI booking Agent

Jobs
27

Hi! I’m an AI developer with hands-on experience in n8n, agentic AI workflows, and Replit. I work with a technical partner and we move fast. I’ve read your post carefully . I can start immediately. Happy to do a small paid test task first so you can verify my skills before committing. What’s the best way to share more about the project?

28

Hola SAOVIA,

Me interesa el proyecto. Soy nativo en español y estoy trabajando precisamente en sistemas de agentes para reservas, atención por WhatsApp/voz, agenda y seguimiento de clientes.

Mi enfoque sería revisar el flujo actual y ayudarte a cerrar estas partes:

- lógica de disponibilidad y reservas con Google Calendar

- control de horarios, duplicados y reprogramaciones

- flujo de WhatsApp para confirmación y recordatorios

- conexión ordenada entre Retell/OpenAI, n8n, GoHighLevel y Calendar

- pruebas con casos reales antes de entregarlo

Para ser transparente: no me vendo como un senior tradicional que lo hace todo de memoria. Trabajo con desarrollo asistido por IA, prompts, APIs, n8n y pruebas estructuradas para llegar a una solución funcional y bien documentada. En este caso, el idioma español y la lógica de reservas/WhatsApp encajan muy bien con lo que estoy construyendo en MicroSmart.

Puedes ver mi proyecto aquí:

Si quieres, puedo revisar el JSON actual o una captura del flujo y decirte qué habría que corregir primero. También me puedes escribir a jorgelg1177@gmail.com.

29

Hi,

I can help finish the booking logic and WhatsApp/reminder flow.

For this kind of system, I would keep the first paid milestone narrow:

  • review the existing Retell/OpenAI/n8n/GHL/Calendar flow
  • identify where booking state breaks
  • fix one full booking path end to end
  • add clear fallback behavior when a slot is unavailable
  • add reminder workflow logic
  • return the n8n export plus short setup notes

Spanish project context is fine if the expected customer phrases and booking rules are provided. The first deliverable should be one reliable booking path, not a big rebuild.

1 Like
30

Hi SAOVIA — I’ve built exactly this stack in production. Live Aria demo: SimplyAiAutomate – AI Voice Receptionist for Clinics & Wellness Studios (you can talk to it now).

I run SimplyAiAutomate and build production voice agents on n8n + GHL + Google Calendar. Two relevant builds, both publicly walkable:

-> Dental AI receptionist (full booking flow) — YouTube https://youtu.be/xkmfxyZT9MY?t=251 — 4:11 is the booking flow, 4:32 CRM sync, 6:36 reschedule/emergency handling, 9:17 stack.

-> Active Wellness Spa outbound agent — YouTube https://youtu.be/_CLVTm4Gb24?t=288 — 4:48 is a real call. Built on VAPI + n8n + GHL with phone validation, business-hours logic, pipeline auto-update, AI summary on call end.

On the specific fixes you mentioned:

  • Booking logic — almost always a Retell function-calling + GCal conflict-check issue (timezone, buffer, double-book race). I’ve debugged this exact pattern multiple times.
  • WhatsApp flow — GHL native WhatsApp or Twilio? Both work, second is more reliable for reminders.
  • Reminder automation — n8n scheduled trigger reading GHL pipeline stage → WhatsApp/SMS, with no-show follow-up branch.

On Spanish: I’m based in India and don’t speak Spanish, so live calls with the end client are off the table. What works well is async — Loom walkthroughs, written specs, you handle the client-facing review. I’ve delivered this way before. If real-time Spanish coordination is non-negotiable for you, totally understand.

If you want me to scope it: share the current n8n export (or screenshots of the broken booking node) + one example of what the WhatsApp flow should do, and I’ll send back a fix plan within 24h.

Gopika
Founder, SimplyAiAutomate
simplyaiautomate.com