I built a WhatsApp Concierge automation in n8n using:
The system works but has several bugs in the state logic and handoff.
I’m looking for a paid consultation (1–2 hours) where someone can review my workflow and suggest fixes.
Timezone: EST / Mexico
Budget: open
Hello Benjamin, thank you for writing.
I will send you more details in the next few days.
We stay in touch.
Hi @GeniusAISolutions , welcome to the n8n community.
If you need any help, feel free to reach out to me here in the community chat.
Thank you Tamy, I will share more details with you in the next few days. We keep in touch.
Hi,
This sounds like a good fit if the issue is around WhatsApp, Airtable, OpenAI or workflow routing.
My approach for a paid debugging session would be:
- review the current workflow or screenshots first
- identify where the data shape breaks
- check Airtable field mapping, webhook payloads and OpenAI response format
- add logs/test nodes so the failure is visible
- fix the smallest possible part first, then document the change
I work with AI-assisted development, n8n-style automation logic, APIs, WhatsApp/customer flows and structured testing. I prefer a clear, bounded debugging scope so you get something useful quickly.
Current work:
Contact: jorgelg1177@gmail.com
Hey, I can help with this.
I’ve built almost the exact same stack WhatsApp Cloud API, state machine logic, OpenAI, and human handoff flows in n8n. Most recently a chatbot for Servis Tyres with session-based state across 9 categories and a 101-rep lookup table, and a hotel concierge voice system with booking logic and agent handoff. State bugs and handoff edge cases are the most common issues I debug in these systems.
I’m available for a 1-2 hour paid review session. We can do a live call where I look at your workflow directly and walk you through the fixes, or I can do an async audit with a written breakdown — whatever works better for you.
Timezone-wise I’m UTC+5 but I can work EST mornings without issue.
What does your schedule look like this week?
I moved this to Jobs since it is a paid request for help and seems to fit the hiring category better. That should give it more relevant visibility.
Hi GeniusAISolutions, welcome to the community 
This is very aligned with the kind of AI workflow systems I work on using n8n, WhatsApp APIs, Airtable state handling, and human handoff flows.
Usually the tricky part is keeping conversation state and escalation logic stable as workflows grow.
Quick question:
• are the bugs happening more during state transitions or Telegram handoff?
Related projects:
• AI Voice Agent + API Automation
https://www.upwork.com/freelancers/~0122761e4734295f4b?p=2038586338272239616
• Multi-channel CRM + Automation System
https://www.upwork.com/freelancers/~0122761e4734295f4b?p=2039118619839795200
Happy to connect further.
Hi GeniusAISolutions, I can take this as a focused paid debugging session.
For this stack I would start with one failing conversation path and trace it end-to-end: WhatsApp webhook payload, Airtable state row, OpenAI response shape, Telegram handoff trigger, then the reservation branch. The usual failure is a state transition or stale/missing field after an AI response, so I would add a small debug log/test harness and fix the smallest broken branch first.
I do not need raw credentials to start. Workflow export/screenshare, 1-2 failing examples, current Airtable fields, and expected behavior are enough for the first pass.
I can do a 1-2 hour EST-friendly review and leave you with exact node changes plus a short written fix note. Happy to DM details if it is still open.
Hi — I run a production multi-tenant SaaS built on a similar stack: n8n + OpenAI + WhatsApp + Chatwoot, currently serving 5 US service businesses with live AI agents. Debugging WhatsApp / OpenAI / Airtable flows is daily work for me.
Happy to jump on a screenshare today or tomorrow. My usual format: flat fee for the diagnostic session, and if the fix turns into a bigger rebuild, I tell you upfront before scope creeps.
One question to size it: what’s the symptom — silent failure, wrong/empty output, rate-limits/timeouts, or auth/webhook? That’ll tell me whether to budget 1h or 3h on the call.
Hey Profile - GeniusAISolutions - n8n Community ,
I can not only help you fix this but also fix it with you on the call in real time explaining everything step by step so you now are more knowledgeable.
With that you can have my personal WhatsApp so any questions you have further I will help you with anytime.
I have built exact systems like these with much more advanced tech stacks and can guide you through all the common errors that happen with them.
Okay with EST timings for the call.
Here is my calendar where you can book an intro call and we can talk about this
Hi @GeniusAISolutions, I can help with a bounded 1-2 hour debugging session.
What I understood: the WhatsApp Cloud API → Airtable state machine → OpenAI → Telegram human handoff / reservation flow works, but state transitions and handoff edge cases are breaking.
My first step would be to trace one failing conversation path end-to-end: incoming webhook payload, Airtable record/state update, OpenAI response shape, branch conditions, and the Telegram handoff trigger. The deliverable would be a short fix note plus specific node changes or test cases so you can verify the fix.
Please share only a workflow export/screenshots with secrets removed first; no API keys or live customer data needed for the first review.
One question: does the main bug happen before the Airtable state update, after it, or only when the human handoff should trigger?
Hi Benjamin — I can help with the paid debugging session.
For this WhatsApp/Airtable/OpenAI handoff bug, I’d keep the first session very tight: map the state machine, identify where state changes are duplicated or lost, then give you concrete fixes for retries, handoff flags, and reservation edge cases.
I can do a 1–2 hour review and leave you with a short fix list + patched workflow logic. If you want, send the workflow export or screenshots of the relevant nodes and I’ll outline the first checks before the call.
Hi,
I can help debug this kind of workflow.
For WhatsApp + Airtable + OpenAI issues, I’d usually check it in this order:
If you can share where the workflow currently breaks, I can help narrow it down and clean up the logic.
Hi — for a paid debugging session, I’d focus on isolating the failing node/path rather than rebuilding everything.
I’d ask for a sanitized workflow export or screenshots, then check: trigger payload shape, Airtable field mapping, OpenAI prompt/output parsing, WhatsApp send node credentials/limits, and error handling. The deliverable can be a fixed workflow + short “what broke / how to avoid it” note.
Contact: travisofwork@gmail.com
Hi,
WhatsApp Cloud API + Airtable state machines + OpenAI + Telegram handoff — I’ve built and maintain exactly this kind of system in production. State logic bugs and handoff edge cases are the hardest part to debug because they’re timing-sensitive.
I’m available for a paid 1–2 hour session and can do EST timezone. I’ll come prepared having reviewed your workflow structure beforehand so we don’t waste call time on setup.
DM me or email narotsuhail@gmail.com to schedule.
— Suhail Narot | Fajr AI | fajrai.net
Hi,
This sounds like a good paid debugging session because the workflow already exists and the problem is likely in state transitions / handoff boundaries rather than a full rebuild.
For a 1?2 hour session, I would focus on producing actionable fixes, not a generic audit:
I can do this as a small paid diagnostic first. No production credentials needed up front ? an exported workflow plus anonymized Airtable fields / screenshots are enough to scope it.
Best,
Brian Du
duyonggan@gmail.com
Hey! This is right in my wheelhouse. I work specifically with n8n and have built multi-step AI workflows integrating WhatsApp Cloud API, Airtable, and OpenAI — very similar stack to what you’ve described.
State machine bugs and handoff logic are some of the trickiest parts to get right. Happy to do a focused 1–2 hour session where we go through your workflow, identify the root cause of the state issues, and get the Telegram handoff working cleanly.
I’m EST-friendly and available this week. Want to DM to sort out a time?
Hello GenisAISolutions,
This is like the similar Automation i built recently. Would love to help you if take us onboard. You can visit our portfolio too
Hi GeniusAISolutions, I can help cautiously with a bounded workflow QA/debugging review.
I want to be transparent: I am not claiming senior WhatsApp Cloud API, Airtable, OpenAI API, Telegram, or production n8n expertise. My fit is junior workflow QA support: reviewing the described state logic, checking expected inputs/outputs, documenting handoff paths, and preparing a fix/test checklist.
I can review redacted screenshots, workflow descriptions, sample payloads, Airtable field structure, and current-vs-expected examples. I cannot accept passwords, API keys, tokens, cookies, or private WhatsApp/Airtable customer data directly.
Relevant sample:
If useful, I can start with a small paid diagnostic/planning session focused on likely failure points and a clear checklist of fixes/tests. Timezone: WIB / UTC+7.