My voice AI receptionist built on VAPI hands callers off to n8n for calendar booking, but the events are landing in the wrong time slots. The logic inside each platform works fine on its own; the problem only appears at the hand-off between VAPI and n8n. I need someone who knows both systems well enough to trace how the date-time data travels, spot the mismatch, and put the correct fix in place—whether that means tweaking a VAPI webhook, adjusting n8n node settings, or adding a small conversion step for time zones. You’ll have direct access to the existing VAPI flow and my n8n workflow (self-hosted) so you can test with real calls and see the incorrect output. Once the schedule lands at the right hour consistently, I’ll consider the job complete. Deliverables: • Updated VAPI or n8n workflow (export file) with the fix applied • Brief note explaining what was changed so I can maintain it going forward If this sounds straightforward to you and you’ve untangled VAPI ↔ n8n integrations before, I’m ready to get this patched today.