What is new in Nodium, November 2026: n8n, MCP, a full free plan

This month, Nodium opened up. The free plan now includes every feature, n8n users can drop WhatsApp into a workflow, AI agents find Nodium in the official MCP Registry, and the SDK, examples and a starter kit are open source on GitHub.

Updated November 11, 2026Read as Markdown

Every feature on the free plan

Build no longer hides anything. Templates, broadcasts, Flows, clients, webhooks, the API and the Nodium agent are all there, in small quantities, so you can build the whole integration before you pay. Launch, at €19 a month, lifts the quantities. See pricing.

A simpler connect link

The hosted connect link you send to a customer now asks for their business details once, in a short form, then opens Meta's signup window already filled in. Customers no longer type the same details twice, and fewer of them give up halfway.

• Prefill the form through the API with prefill when you create the link: name, display name, email, website, address, country, category, description.
• Or store the details on the client once with PATCH /tenants/{id} and business: every later link reuses them.
• The page asks first which app the number is on, and refuses a regular WhatsApp number before Meta does.

WhatsApp in n8n

The Nodium community nodes are on npm as @nodium.io/n8n-nodes-nodium. The trigger creates its own webhook when the workflow is activated and checks the signature of every event; the action sends texts and templates, and reads conversations, numbers, contacts and clients.

• In n8n, Settings › Community Nodes › Install, then @nodium.io/n8n-nodes-nodium.
• Create a Nodium API credential with your API key.
• Start a workflow with Nodium Trigger on message.received, and answer with Nodium › Message › Send Text.

The full walkthrough is in the n8n quickstart. The nodes run on self-hosted n8n; on n8n Cloud, they will be available once n8n has verified them.

Nodium in the MCP Registry

The Nodium MCP server is listed in the official MCP Registry as io.github.Nodium-io/whatsapp. An agent such as Claude Code or Cursor reads conversations, contacts and templates with your API key; sending messages is switched on only when you ask for it, by adding ?send=true to the address. To add it by hand:

Open source on GitHub

• sdk: the TypeScript SDK and the CLI, with examples for Node, Next.js, FastAPI and Laravel.
• whatsapp-saas-starter: a Next.js app that lists your clients, sends them a connect link and answers their conversations, switching to a template when the 24-hour window is closed.
• n8n-nodes-nodium, agent-skills and openapi: the n8n nodes, the files that teach an AI agent to use Nodium, and the OpenAPI description.

All at github.com/Nodium-io, under the MIT licence.

Guides for people and for AI

New guides, comparisons, alternatives and feature pages answer the questions asked before an integration: official or unofficial API, the 24-hour window, Meta's pricing, Tech Provider or Solution Partner. Each page also reads as Markdown: add .md to its address. AI assistants find the whole site in /llms.txt.

Reminder: replies are not always free any more

Since 1 October 2026, Meta charges service messages beyond 1,000 per number each month. Replying inside the 24-hour window stays free up to that allowance; beyond it, each reply is billed by Meta to the number's owner, and refused without a payment method. Nodium flags such a number paymentMissing and says why in message.failed. Details in Meta's pricing explained.

A status page that measures Nodium

The status page now says whether Nodium works, and nothing else: the database, the webhook queue, the scheduled tasks and WhatsApp reception. A customer's slow server, a paused webhook or a quiet day no longer show as degraded.