๐โจ How do you handle human takeover in n8n chatbots?
When building chatbots with n8n, one question kept coming up from clients: โCan I see the conversations?โ โCan I jump in when the bot messes up?โ The bot itself wasnโt the problem. The real challenge was giving clients a clean, simple way to be involved without digging through executions, logs, or raw webhook data. So over the last few months, Iโve been building Trilox. Trilox is a shared inbox for n8n chatbot conversations with human takeover: * Bots handle chats by default * Humans can jump in instantly when needed * Conversations can be handed back to the bot * WhatsApp, Telegram, Messenger, web widget โ all in one inbox Iโm also building a dedicated n8n community node that plugs directly into workflows: * Record bot + visitor messages * Check whoโs handling the conversation * Escalate to a human when needed * Receive human replies via webhook Weโre currently pre-launch and sharing progress publicly. If this is something youโd use, you can join the waitlist to be the first to know when it opens: ๐ https://trilox.io Would love to hear how others are handling human-in-the-loop chatbots in n8n ๐