n8n is a workflow automation platform (Berlin-based, open-source core). The signal here is unusually strong: two separate developers independently built Japanese UI localisation forks and distributed them as Docker images. And Zenn/note are full of Japanese how-to guides. People want n8n in Japanese badly enough to build it themselves — and the official product hasn't shipped Japanese yet.
n8n.io and the official docs render in English only (lang="en"). At the same time, two independent developers (Tomatio13 and nemumusito) separately built Japanese UI localisation forks and distributed them as Docker images. Zenn and note.com have substantial Japanese how-to libraries for n8n.
The demand signal is as clear as it gets: people want it enough to fork the UI, package it in Docker, and write documentation for each other. That same Japanese team evaluating a Zapier alternative doesn't know these forks exist — they hit the English-only site and assume n8n isn't for Japan. The value leak is enormous.
An official Japanese UI locale (potentially adopting or acknowledging one of the community forks with their contributors' blessing) plus Japanese landing and docs pages. This is the highest-leverage change because it finally captures the demand that's already there.
The legal pages (n8n.io/legal/) render in English. No 特商法に基づく表記 page was found. The site language is English-only throughout (lang="en").
Before putting a recurring subscription on a company card, Japanese buyers look for 特商法 disclosure. It's the standard "is this a real, accountable foreign business" check. Without it, the purchase gets blocked at the finance approval step.
A single 特商法に基づく表記 page with the required fields: seller, representative, address, contact, pricing, payment terms, refund/cancellation policy. Template-level work.
n8n pricing is in EUR (Starter and Pro plans; enterprise custom). No JPY display or regional pricing option found.
n8n.io/pricing/ — EUR confirmedEUR adds a double conversion step for a Japanese buyer (EUR → mental USD → JPY) plus exchange-rate uncertainty on every recurring charge. For companies doing expense approvals in Japanese accounting software, a EUR line is awkward. JPY display at minimum removes the conversion friction.
JPY display alongside EUR on the pricing page. For enterprise deals, a JPY-denominated invoice option.
With no Japanese pages on n8n.io, there's nothing indexed for Japanese-language queries. The Japanese community content lives on Zenn/note — which is useful for existing users but doesn't capture the evaluation-stage buyer.
A team searching for a Zapier alternative types 「zapier 代替」 or 「ワークフロー自動化 オープンソース」. n8n doesn't appear, and they land on whatever comparison article ranks — usually one listing Make.com, Zapier's own pages, or a domestic tool. The community forks are invisible to this buyer.
Official Japanese landing and comparison pages targeting those queries, with links acknowledging the community forks. The existing Zenn/note content is proof the keyword demand exists.
Two separate uncoordinated forks (Tomatio13, nemumusito) both package Japanese UI. No official n8n statement on the Japanese locale roadmap was found.
Tomatio13 fork nemumusito forkTwo competing unofficial forks mean a buyer has to evaluate which one to trust, neither is officially supported, and both could fall behind the main release. For enterprise adoption, unofficial Docker images that patch the UI are a security and maintainability red flag.
Either acknowledge one fork officially (with the contributor's agreement), or post a clear roadmap statement on when official Japanese UI lands. Ambiguity here costs more than a clear "not yet."
Five signal dimensions, each 0–20. Verified 2026-06-20:
| 1. Japanese marketing funnel | 2 / 20 |
| 2. Legal / trust (特商法) | 0 / 20 |
| 3. JPY billing / payment | 2 / 20 |
| 4. JP search visibility | 2 / 20 |
| 5. Product locale / IME / UX | 14 / 20 |
Dimension 5 is partially credited because the community forks prove a Japanese locale is technically feasible and the existing UI architecture supports it — but it hasn't shipped officially, and two competing forks create fragmentation.
This map is the free slice. The full Japan-readiness audit covers the same gaps end-to-end, with the community fork analysis, 特商法 fields filled in, and a concrete action plan for the Japanese market.
Data verified 2026-06-20 against n8n.io, n8n.io/pricing/, n8n.io/legal/, and community forks listed above. Corrections or opt-out: hello@glovrex.com.