Dani here We're about halfway through launch day and the questions have been great. A few keep coming up, so here are the answers in one place for anyone just arriving.
"If someone copies my Managed widget onto their site, does it use my credits?"
No. The widget checks which site it's on before it loads. If that site isn't on your allowed list, it doesn't appear at all, so there are no messages and no credits used.
"Does it keep the conversation if a visitor comes back?"
Yes. History is saved in the visitor's browser, so it survives reloads and return visits on the same device. If you'd rather start fresh each time, there's a setting for that.
"Can it know who the logged-in user is?"
Yes. Pass the user's details as metadata and your n8n workflow gets them with every message.
Congrats @ross_jenkins @dani_martin1 @nicholas_adenikinju 🎉
Charging clients per message straight from the analytics panel is great, and something most widget tools totally ignore.
Is the n8n community node going to replace webhooks completely for most setups, or is it more for beginners? Good luck today!
@ross_jenkins @nicholas_adenikinju @kate_ramakaieva Thank you, really appreciate it! 🙏
Quick clarification on the analytics so nobody gets the wrong idea: the panel doesn't charge clients itself. It shows message counts for each Managed widget over any date range you pick, plus sessions, errors, devices and locations. Agencies put one client on each widget and use those numbers to bill per message in whatever invoicing tool they already use. You're right that most widget tools don't give you that.
On the community node: it doesn't replace webhooks, it runs on one. The n8nChatUI Trigger is a webhook underneath. What it removes is the plumbing around it. Normally you'd build a Webhook node, check auth, tidy up the incoming data, then shape the reply for a Respond to Webhook node. The node does that for you: it checks Basic Auth or JWT, gives you a clean { message, sessionId, pageUrl, metadata } to work with, and the reply node lets you add up to 4 suggested-reply buttons.
So it isn't only for beginners. It's simply a faster setup, and experienced builders save the most time with it. If you need full control over the raw request, the plain Webhook node still works exactly as before. One limit for now: it's a community node, so it installs on self-hosted n8n and isn't available on n8n Cloud yet.
Thanks again for the support today!
— Dani
Agency clients always want the chat widget to look like their brand and not like n8n, so live preview plus voice and file uploads in a no-code builder is exactly the gap this fills for me.
@karimbenkeroum That's great to hear, and it's exactly the problem we had in mind. Clients don't care that it runs on n8n. They want it to look like their own website.
A few things that should help with agency work:
One widget per client, all in one account. Clone a widget you've already styled as a starting point, then change the colours, avatar and copy for each brand.
Remove our footer so it's fully white-label.
Lock each widget to its client's domain (Managed widgets) so it only loads on their site.
Message counts per widget in the analytics, if you bill clients for usage.
If you set it up for a client and anything feels clunky in an agency workflow, tell us. That feedback is really useful to us right now.
— Dani
The RTL support for Arabic is a useful detail. Does RTL also flip the input bar and file upload layout, and can one widget switch the welcome message and follow-up prompts by visitor language?