Time Zone issue in retell and N8N

I am building a voice agent using Retell AI, where the core logic is handled through n8n workflows. So essentially, my system relies on two main components: Retell AI and n8n workflows.

Currently, I am building this voice agent for the UK, so the entire system—both in Retell AI and in n8n—is configured with a UK-based time zone.

After deploying the voice agent in the USA, then if I plan to expand to other regions additional countries. At that point, I will need to update the time zone across the entire Retell AI workflow and all n8n workflow logic.

The challenge is that time zone handling is embedded in multiple places throughout the system. Updating it manually everywhere is complex and inefficient. There is a high risk of missing something during the change, which could lead to inconsistencies and potential system failures.

I want to design a solution that allows me to simplify and centralize time zone management, so changes can be made quickly, safely, and without errors across the entire system.

so, how can I so solve this..

1 comment