Tenreply logoTenreply
← Back to Blog
Guide

n8n + WhatsApp API: How to Add a Chat Dashboard to Manage Your Conversations

You've wired up n8n to the WhatsApp API and your automations are running — but your team still has nowhere to read, reply to, and manage the actual conversations. Here's exactly how to fill that gap.

The Gap n8n Leaves Open

n8n is excellent at automation: triggering messages when an order ships, routing webhooks, enriching contact records, syncing data between systems. If you've connected it to the WhatsApp Cloud API, your automated flows are probably working well.

But n8n was never designed to be a conversation inbox. It has no interface for a human to read an incoming customer reply, type a response, see conversation history, assign a chat to a team member, or track what's been answered and what hasn't. The moment a customer replies to one of your automated messages — or starts a brand-new conversation — you need a different tool to handle it.

This is the gap a dedicated WhatsApp dashboard fills, and it's exactly what Tenreply is built for: the human side of the WhatsApp API, sitting alongside your n8n automations.

What n8n Handles vs. What a Dashboard Handles

Think of the two tools as doing complementary jobs:

n8n: Outbound automation and system integrations

  • Send a WhatsApp template message when an order is placed in Shopify
  • Trigger a reminder 24 hours before an appointment
  • Webhook the contents of an inbound WhatsApp message into a Google Sheet or CRM
  • Route specific keywords to different pipelines
  • Sync opt-out requests to your marketing list

WhatsApp Dashboard (Tenreply): Human conversation management

  • Read all incoming messages across your whole team in a shared inbox
  • Reply to customers from a browser — no phone required
  • Assign conversations to specific agents
  • See full conversation history per contact
  • Track open, pending, and resolved conversations
  • Send one-off outbound messages and templates without writing code
  • Track first-response time and agent performance

Both tools connect to the same WhatsApp Business API number. They're additive — not competing.

How the Integration Works

You don't need to choose between n8n and a dashboard. Here's the architecture most teams use:

  1. WhatsApp Cloud API — your Meta-registered number, the source of truth for all messages.
  2. Tenreply — connects to the same API number. All inbound messages land in the shared inbox. Your team reads and replies here.
  3. n8n — connected via Tenreply's outbound webhook (which fires on every inbound message, every send, every assignment). n8n receives these events and runs your automation logic: creating CRM records, triggering follow-up flows, posting to Slack, etc.

Alternatively, if you want n8n to initiate outbound messages through Tenreply's API (rather than calling Meta directly), you can use Tenreply's REST API — this gives n8n full control over sending while Tenreply handles the message storage, delivery tracking, and inbox display.

Step-by-Step: Connecting Your n8n Setup to Tenreply

Step 1 — Connect your WhatsApp number to Tenreply

If you're already using the WhatsApp Cloud API with n8n, you'll have a phone number ID and access token from Meta Business Manager. Bring those into Tenreply: Settings → WhatsApp → Connect. Tenreply registers as an additional webhook endpoint on your number — your existing n8n flows continue working uninterrupted.

If you're using a BSP (like 360dialog) rather than the Cloud API directly, Tenreply supports the same credentials flow.

Step 2 — Register Tenreply's webhook with your n8n flows

Inside Tenreply, go to Settings → Developer → Webhooks → Add Subscription. Paste your n8n webhook URL and select which events you want to receive: message.received, message.sent, conversation.assigned, etc. Tenreply will POST a structured JSON payload to n8n on each event — the same data structure n8n's WhatsApp node uses, so your existing workflows need minimal adjustment.

Step 3 — Let your team use the inbox

Invite team members via Settings → Team Members. Each agent gets a login and sees the shared inbox immediately. Conversations that n8n has already automated (sent a template, logged a CRM record) show up in the inbox with full history — so agents have context before they type the first word.

Step 4 — Use Tenreply's API for n8n-triggered sends (optional)

If you'd rather have n8n call Tenreply's API to send messages (rather than calling Meta's Cloud API directly), the endpoint is straightforward:

POST https://app.tenreply.com/api/messages/send
Authorization: Bearer YOUR_API_KEY
{
  "conversationId": "...",
  "content": { "text": "Your message here" }
}

This approach means all outbound messages — whether sent by a human agent or triggered by n8n — are stored, displayed, and tracked in one place.

The Flows That Work Best Together

Automated first response → human follow-up

n8n sends an instant automated reply when a new customer message arrives ("Thanks for reaching out — we'll be back in touch within the hour"). Tenreply flags the conversation as pending. The next available agent picks it up and replies personally, with the automated message already in the history for context.

Lead qualification bot → agent handoff

n8n runs a qualification flow: asks the customer three questions, parses the replies, scores the lead. When the score hits a threshold, n8n calls Tenreply's API to assign the conversation to a senior sales agent and adds an internal note with the qualification data. The agent opens Tenreply, sees the score, and picks up where the bot left off.

Order update automation → support thread

n8n sends shipping updates automatically via template messages. When a customer replies with a question ("Where is my package?"), the message lands in Tenreply's inbox. The agent has the order number from the original automated message in the conversation thread — no need to ask the customer to repeat themselves.

What You Gain by Adding a Dashboard

  • No messages fall through the cracks — the inbox shows everything unread, regardless of whether n8n processed it.
  • Your team doesn't need to touch code — agents reply from a browser, not from n8n or the terminal.
  • Full history in one place — automated sends and human replies all stored together per contact.
  • Team accountability — who replied, how fast, how many conversations resolved per day.
  • Templates without code — agents can send approved WhatsApp templates with a click, without an n8n flow.

Getting Started

Tenreply offers a 14-day free trial with no credit card required. If you already have your WhatsApp API credentials from n8n, connecting takes under 30 minutes. Your automations keep running in n8n; your team gets a proper inbox to handle the human side.

For developer documentation, the API reference and webhook event catalogue are at tenreply.com/developers.