Skip to main content
RoutMe
All posts
Playbooks6 min read

How to move a customer support workflow from n8n to RoutMe

A step-by-step migration of a WhatsApp support workflow from n8n to RoutMe Flows: node mapping, the agent step, connectors and a checklist to cut over safely.

JJ

Jesbin James

Engineering

You can move the customer-conversation part of an n8n support workflow to RoutMe by rebuilding it as a Flow: the inbound-message webhook becomes a message trigger, the IF and Switch nodes become If and Switch steps, the HTTP Request node becomes an HTTP call step or a connected tool, and the AI Agent node becomes the agent step. Nodes that talk to unrelated apps stay where they are.

This guide is for teams who built a WhatsApp or website support bot in n8n and now spend more time maintaining it than improving it. It assumes the workflow does something like this: receive a message, work out what the customer wants, look something up, reply, and sometimes pass the chat to a person. That is exactly the shape RoutMe is built for. If your workflow does a lot more than that, read the section on what stays in n8n before you start.

Step 1: List what the workflow actually does

Open the n8n workflow and write down every node in plain words, grouped into four buckets: how a message arrives, how the decision is made, which systems are read or written, and how the reply goes out. Teams are often surprised that a workflow with thirty nodes has only five distinct jobs. Retry wrappers, error branches, signature checks and data reshaping nodes tend to account for most of the count, and most of those exist because n8n gave you a webhook rather than a conversation.

Mark each node as conversation glue or as something else. A node that parses an inbound WhatsApp payload is glue. A node that updates your accounting system after a sale is something else.

Step 2: Map the nodes to Flow steps

A flow in RoutMe is a trigger plus the steps that run when it fires. The graph is validated when you save it, so a broken flow is caught before it sees traffic. Here is how the usual n8n nodes translate.

  • Webhook receiving WhatsApp messages becomes the message received trigger. RoutMe receives the messages itself, so there is no webhook URL to register with Meta and no payload to parse. An optional keyword narrows it to messages containing a word.
  • IF becomes the If step, which has a then branch and an else branch. It compares an event field, a contact attribute or a tag against a value.
  • Switch becomes the Switch step, with one output per case and a default.
  • Filter becomes the Filter step, which continues only when the condition holds.
  • Set becomes a set attribute step when you are storing something on the contact. Free-form data reshaping has no equivalent, so push that logic into your own service.
  • HTTP Request becomes the HTTP call step, which posts JSON to your service and can save the response for later steps. It sends a POST only, so a GET against a third-party API moves behind a tool instead.
  • Wait becomes the wait step (up to 30 days) or the delay until step, which pauses until a clock time such as 09:00 in a timezone you pick.
  • WhatsApp send nodes become send text, for free-form replies inside the 24-hour window, and send template, for anything outside it.
  • AI Agent becomes the agent step, covered in the next section.
  • Code node has no equivalent. Move that logic into a small service your flow calls, or into a tool the agent can use.

Step 3: Replace the LLM chain with an agent step

In n8n, an AI workflow usually chains a model node, a memory node and several tool nodes. In RoutMe the agent step plays that role. You write its instructions, choose which actions it may take, attach the MCP servers it may call, and define up to ten named outcomes, such as resolved, needs a person and not found. The model works for up to six rounds, picks an outcome, and the run continues along the matching edge.

Give the default outcome a safe destination. It is where the run goes if the model finishes without choosing, and the safest fallback is a handoff to a teammate with the transcript. The agent can only do what you list for it. The logic steps and the agent step itself are not tools, so it cannot rewrite its own flow.

For wording the instructions well, see what to put in an AI agent's instructions.

Step 4: Reconnect your systems

Your n8n workflow probably reads orders, bookings or accounts from somewhere. In RoutMe you expose those reads as tools over MCP and attach the server to the agent step. You add the server URL, an optional bearer token, press Test connection, and RoutMe reports the tools it found. In the chat widget, only tools that declare themselves read-only are offered, which is a useful property when anonymous visitors are typing. Agent steps in flows do not apply that filter, so attach only servers whose tools you are comfortable letting the step call. The longer explanation is in connect your systems without glue code.

If a system has no MCP server yet, you have two honest options: write a small one that wraps the few reads you need, or keep the lookup in your own service and call it with the HTTP call step.

Step 5: Move the WhatsApp number and templates

RoutMe connects to WhatsApp through Meta's own Embedded Signup and the Cloud API, so you do not need a Twilio account or another provider in the middle. You log in with the Facebook account that administers your WhatsApp Business Account, pick the number, and RoutMe registers it. If the number is live somewhere else, there is a guided path for migrating it. Templates that are already approved can be imported from WhatsApp, so you keep your approvals instead of waiting for Meta again.

The background is in WhatsApp without Twilio.

Step 6: Add handoff and the inbox

Most n8n bots handle handoff badly because there is nowhere to hand off to. In RoutMe the inbox is part of the product: conversations sit in queues called Open, Mine, Unassigned and Closed, can be assigned to a teammate, and a person can ask for a drafted reply or a short summary of what the customer wants. In a flow, the assign step routes the conversation to a teammate, and the agent step can end on a handoff outcome. See designing the handoff to a human.

Step 7: Test before you cut over

A new flow is created paused and nothing runs until you activate it. Connect a test number, activate the flow, and send real messages. Every execution records a per-node trace, which node ran, which failed and why, so a flow that did not reply is a question you can answer by reading the run. A send text step that hits a closed 24-hour window fails visibly, which tells you where a template belongs.

Migration checklist

  1. 1Every n8n node is labelled as conversation glue or something else.
  2. 2Each glue node has a Flow step, a tool or a line in your own service.
  3. 3Agent instructions, outcomes and the default fallback are written and reviewed.
  4. 4Each system the agent reads is behind an MCP tool, and the credential behind it is read-only.
  5. 5The WhatsApp number is connected and the needed templates are approved or imported.
  6. 6Handoff is wired to a real teammate or queue.
  7. 7A test number has run at least one happy path, one unknown question and one handoff.
  8. 8The n8n webhook for the live number is switched off only after the cutover, and not before.

Want a second pair of eyes on the mapping? Walk through your workflow in a demo, or read how the pieces fit in the Flows overview and the pricing page.

  • Migration
  • n8n
  • Flows
  • WhatsApp
JJ

Jesbin James

Engineering

Writes about integrations, agent tooling, and the parts of the WhatsApp Cloud API that only show up in production.

Frequently asked questions

Can I import my n8n workflow JSON into RoutMe?

No. There is no importer for n8n exports. You rebuild the conversation part as a Flow, either on the canvas, from a ready-made flow, or by describing it in plain words and reviewing the draft. Most support workflows are small enough that this takes less time than expected.

What happens to my n8n nodes that talk to other apps?

Anything that is not about the customer conversation can stay in n8n. Your n8n workflow can post to the RoutMe external events endpoint when something happens, or RoutMe can call your service with an HTTP call step. See n8n vs RoutMe.

Do I keep my WhatsApp number?

Yes, if you own the WhatsApp Business Account it lives on. You connect it through Meta's Embedded Signup, or you migrate a number that is live somewhere else. Existing approved templates can be imported from WhatsApp so you do not recreate them.

Can I run both in parallel while I test?

A phone number delivers its messages to one place at a time, so the clean way is a second test number on RoutMe while n8n keeps the live one. Cut the live number over only when the checklist below passes.

See it on your own data

Connect a system, drop an agent node into a flow, and watch it answer from what is actually true in your systems right now.