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 👀

I was spending hours clicking through n8n execution logs trying to monitor chatbot conversations, so I built 4 custom n8n nodes that solve this: Record Message - Groups messages by conversation automatically (chat ID, phone number, or session ID) Escalate to Human - Bot triggers this when it can't answer, assigns to human agent Check Assignment - Checks if bot or human is handling the conversation Get Reply - Pulls human replies from inbox back into n8n workflow The flow: 1. Message comes in → Record it 2. Check who handles it (bot or human) 3. Bot can't answer? → Escalate to human 4. Human replies → Get that reply back to n8n 5. Send to customer Been using this for a few weeks. Way better than execution logs. What features would you want in something like this?