n8n and WhatsApp: Self-Hosted Chat Automation

What connects today

Without a native node, n8n's own building blocks do the connecting.

• Wutt webhooks trigger n8n workflows when events fire
• Wutt's REST API runs inside n8n HTTP Request nodes
• n8n handles orchestration, including its self-hosted flexibility
• No native Wutt node or n8n registry listing yet

What you can build today

Workflows are buildable now, by you or a developer.

• Any system n8n reaches can trigger a WhatsApp message through Wutt
• Wutt events feed downstream steps in your workflow
• Booking and order events start business processes outside Wutt
• n8n's own node library connects to the rest of your stack

The roadmap: a native n8n node

A native Wutt node is on the roadmap. It is not live yet. When it ships, it is planned to include:

• Prebuilt triggers for Wutt messages, contacts, and orders
• Prebuilt actions to send messages and manage contacts
• A listing in the n8n registry
• Cleaner credential handling than manual API keys

Setup steps for today

A webhook-based workflow takes minutes to assemble.

• Generate an API key from your Wutt workspace
• Create the webhook URL in Wutt for the event you want
• Add a Webhook node or HTTP Request node in your workflow
• Test end to end before scheduling the workflow

Honest limitations

Be clear about what today's setup is and is not.

• No native n8n node today; it is roadmap, not a released product
• HTTP and webhook setup needs comfort with configuration or a developer
• Wutt defines the webhook payloads; you map them in the workflow
• WhatsApp sending still follows Meta template rules and opt-in requirements

How Wutt helps

Wutt's external API and webhooks are documented and stable, so workflows built today keep working when the native node ships.