N8N and the like: when to build the WhatsApp service yourself
Published on October 04, 2026 · Updated on October 11, 2026
Tools like n8n and Make connect WhatsApp to other things: calendar, spreadsheet, database, language model.
They are good at what they do.
The real question is not whether they work, but whether someone will look after them later.
What they do well
- Send and receive messages through the official API, with control over the flow.
- Connect systems that were never built to talk to each other, without asking the vendor for an integration.
- Handle repetitive tasks: create a calendar event, add a spreadsheet row, notify someone.
- Stay cheap in money for small and medium volume.
What they won’t do for you
- Write your service content: services, prices, rules and answers.
- Decide what to say when a question is ambiguous.
- Follow up on the questions the flow couldn’t handle, and fix them.
- Keep everything running. A flow nobody watches breaks silently, and the customer gets no reply.
The hidden cost
- Time to build and tweak, which almost always runs over.
- Hosting, when the flow runs outside the builder’s own computer.
- Maintenance every time Meta changes its API and every time the model is updated.
- Silent outages: when it breaks in the middle of the night, the customer is the one who notices.
When building it yourself is worth it
- When you have someone technical on the team, or a trusted contractor with a maintenance agreement.
- When volume and rules are stable.
- When the automation is internal, not your customers’ front door.
When to hire the build
When customer service is your front door, and every outage means an empty slot.
Then you are not hiring a flow, you are hiring the operation: someone watching, fixing and keeping it running.
That is what we do, with no setup fee and a monthly fee of $500 to $1,050.
On the annual plan, 12 months paid upfront, the monthly fee gets a 20% discount ($400, $640 or $840 per month).