# n8n chat nodes vs n8n + LangBot

Source: https://langbot.app/en/compare/n8n-vs-n8n-with-langbot · Last reviewed: 2026-11-11

Build chatbots directly with n8n's chat and messaging nodes, or let LangBot handle the chat platforms and call one n8n workflow. Compare effort, platforms and group-chat handling.

## In short

n8n can build a chatbot by itself with its chat trigger and per-platform nodes, and that is a good fit for one channel. As you add platforms, each one needs its own trigger, message format, session handling and reply node. With LangBot, one n8n webhook workflow serves every connected platform, and LangBot handles sessions, group-chat triggers and delivery.

| | n8n + LangBot | n8n on its own |
| --- | --- | --- |
| Get it running | cloud.langbot.app: point it at your workflow webhook, no deployment | n8n Cloud or self-hosted n8n, plus per-platform setup |
| Model access | LangBot Models available for the built-in Agent, no API key needed | Configure each model provider's credentials in n8n |
| Events beyond messages | Member joins, reactions, recalls and card clicks can trigger agents | Depends on each channel node |
| Platform plumbing | Handled by LangBot adapters | Built per platform in the workflow |
| One workflow, many platforms | Yes: one pipeline bound to many bots | Separate triggers and reply nodes per platform |
| Chinese IM (WeCom, Lark, DingTalk, QQ, WeChat) | Built-in adapters | Depends on available nodes or custom HTTP work |
| Streaming replies | Supported with n8n streaming response mode | Depends on the channel node |
| Licence | Apache 2.0 | Sustainable Use License (fair-code) |

## What LangBot gives you out of the box

### No deployment: cloud.langbot.app

Sign up at [cloud.langbot.app](https://cloud.langbot.app) and build a bot in the browser with a setup wizard. There is a free plan, the public HTTPS URL webhook platforms need is included, and a Dedicated environment is available for production. Self-hosting stays free and unlimited.

### Official model service: LangBot Models

Claude, GPT, Gemini, DeepSeek, Qwen, GLM, Kimi, Grok and more, plus embedding, rerank and speech models, with no model API key to obtain. Cloud plans include monthly credits; self-hosted instances signed in with a LangBot Space account get the models added automatically with a free starter quota. Your own API keys keep working alongside.

### Control your bots in natural language

Agents, a unified API and standard platform events and APIs work together. Every Workspace operation (bots, routing, pipelines, models, knowledge bases, monitoring) is one catalog shared by the HTTP API, the MCP server, the Workspace Assistant and plugins, and adapters expose standard platform APIs such as send, reply, edit and recall messages, query groups and members, and, where the platform allows, mute or remove members. So you can change how a bot behaves by telling the Workspace Assistant, or let an authorized agent act on the platform from a chat instruction. Writes need your confirmation or an explicit permission grant.

### Workspace Assistant

Describe what you want in plain language. The assistant inspects your existing models, knowledge bases and pipelines, proposes a configuration and applies it only after you confirm each change.

### Rich APIs and flexible tools

An HTTP Service API with API keys, LangBot's own MCP server, the `lbctl` CLI and outgoing event webhooks for your systems. Agents can use MCP tools (stdio and HTTP), Skills, a code sandbox (Docker, nsjail or E2B), knowledge bases with rerank, and platform events such as member joins, reactions and card clicks.

### Rich, stable plugin interfaces

Plugins run in a separate Plugin Runtime process and are hot-pluggable. The Python SDK offers Runner, Tool, Command, EventListener, KnowledgeEngine, Parser and Page components, and a Workspace API whose operations a plugin must declare and a member must grant. The [LangBot Space marketplace](https://space.langbot.app/market) lists plugins, MCP servers and Skills, with reviewed Certified Plugins.

### Open source, with official backing

Apache 2.0 with free commercial use, an official managed service, and optional Enterprise Support with contracts and invoices.

## When n8n alone is enough

One channel, simple request/response logic, and you are already comfortable maintaining the channel's node in n8n.

## When to add LangBot

- You want the same workflow answering on Telegram, Slack, Discord, WeCom, Lark or DingTalk.
- You want group-chat rules, per-user sessions and monitoring without building them in the workflow.

Point LangBot's n8n runner at a workflow that starts with a Webhook or "On chat message" trigger. See the [n8n runner guide](https://langbot.app/docs/en/usage/pipelines/n8n) or a recipe such as [n8n on Slack](https://langbot.app/docs/en/recipes/n8n/slack).

## FAQ

### Which data does LangBot send to the workflow?

The message text plus variables such as the session ID, sender ID, conversation ID and group name, so the workflow can keep context per user or group.

### Does it support streaming?

Yes. Set the trigger's Response Mode to Streaming and use an AI Agent node; LangBot streams to platforms that support it.

## Further reading

- [n8n](https://n8n.io)
- [n8n runner guide](https://langbot.app/docs/en/usage/pipelines/n8n)