Axera Flow · Case
One n8n workflow, one Evolution instance, one Postgres database serving multiple markets — each with its own language, persona, and escalation rules. Adding a market is a database row, not a code fork.
01 · The problem
Axera Flow operates across two markets that speak different languages, expect different conversational tones, and fall under different privacy regimes (LGPD in Brazil; PIPEDA, Law 25, PIPA in Canada). Hand-rolling two separate bots would mean two codebases, two pipelines, and two credential sets — a non-starter for a one-person operation.
02 · The solution
A multi-tenant architecture: one n8n workflow, one Evolution API instance, one Postgres database, with every market-specific setting (system prompt, language, owner phone, business name) stored as a row in a per-market config table. The webhook reads the instance from the inbound message and injects everything dynamically. Adding a market is a new row — no code fork.
03 · Stack
04 · Results
To add a market
9 min
Workflow changes
0
Markets (BR + CA)
2