FlowClient — White-Label n8n Workflow Portal for Agencies Who Are Tired of Handing Clients Raw JSON
You built the automation, the client wants a dashboard, and right now your best option is 'here is your n8n login, good luck.' FlowClient wraps any n8n workflow in a branded client portal with run history, trigger buttons, and usage billing in under 30 minutes. Charge a 25% margin on top of n8n cloud and never explain what a webhook is to a client again.
Difficulty
intermediate
Category
SaaS
Market Demand
High
Revenue Score
8/10
Platform
Web App
Vibe Code Friendly
No
Hackathon Score
6/10
Validated by Real Pain
— sourced from real community discussions
n8n builders shipping client automations have no native way to give clients a branded portal — they resort to manual exports, bespoke scripts, or raw n8n access.
What is it?
Agencies shipping n8n automations as client MVPs hit the same wall every time: the client wants visibility, control, and a logo that isn't n8n's. The current workaround is exporting JSON, writing bespoke deployment docs, or giving clients raw n8n access and praying. FlowClient solves this with a white-label portal layer that connects to n8n's REST API, surfaces workflow run history, exposes manual trigger buttons, and shows per-client usage stats. The agency sets pricing per execution and FlowClient handles billing via Stripe. Fully buildable because n8n's cloud API is stable, Stripe metered billing is well-documented, and the entire frontend is a dashboard reading from two API endpoints.
Why now?
n8n hit 50k GitHub stars in early 2026 and agency adoption exploded — the ecosystem now has thousands of freelancers delivering client workflows with zero native white-label story.
- ▸Per-client branded portal with agency logo and custom domain (Implementation: Next.js middleware subdomain routing)
- ▸Workflow run history and status feed pulled from n8n REST API in real time
- ▸Manual trigger buttons with input forms auto-generated from workflow webhook schemas
- ▸Stripe metered billing per execution with monthly invoice delivery to clients
Target Audience
n8n automation agencies (est. 8,000+ on Reddit and Discord) reselling workflows to SMB clients
Example Use Case
Sarah runs a 5-person n8n agency, deploys FlowClient for a logistics client, the client logs in and sees 847 successful invoice-processing runs this month, clicks a manual re-trigger when needed, and Sarah bills $0.02 per execution automatically via Stripe.
User Stories
- ▸As an n8n agency owner, I want to give clients a branded portal to view run history, so that I look professional without exposing my internal n8n instance.
- ▸As a client of an automation agency, I want to manually trigger my workflow from a button, so that I do not need to call my agency for routine resets.
- ▸As an agency owner, I want Stripe to automatically bill my client per workflow execution, so that I do not manually invoice at the end of every month.
Done When
- ✓Portal creation: done when agency pastes n8n API key and a branded client URL appears within 60 seconds.
- ✓Run history: done when client logs in and sees last 50 workflow runs with status, timestamp, and duration without any setup.
- ✓Manual trigger: done when client clicks trigger button and a new run appears in history within 10 seconds.
- ✓Billing: done when Stripe charges the configured per-execution rate and agency receives a dashboard confirmation.
Is it worth building?
$99/month x 50 agencies = $4,950 MRR at month 4. $199/month x 150 agencies = $29,850 MRR at month 10. Realistic: 50 paying agencies in 6 months via cold outreach to n8n Discord.
Unit Economics
CAC: $30 via Discord DM outreach at 10% close rate. LTV: $2,376 (24 months at $99/month). Payback: under 1 month. Gross margin: 88%.
Business Model
SaaS subscription per agency seat
Monetization Path
$49/month starter (3 client portals), $99/month growth (10 portals), $199/month agency (unlimited). 14-day free trial converts at 18% for tool-builder audiences.
Revenue Timeline
First dollar: week 3 via beta agency upgrade. $1k MRR: month 2. $5k MRR: month 5. $10k MRR: month 10.
Estimated Monthly Cost
Vercel: $20, Supabase: $25, n8n cloud API calls: $30, Stripe fees: $25. Total: ~$100/month at launch.
Profit Potential
Full-time viable at $8k-$20k MRR with 80-100 agency customers.
Scalability
High — add Make.com support, Zapier Embedded bridge, and white-label domain per client in V2.
Success Metrics
Week 2: 5 beta agencies onboarded. Month 2: 20 paying at $99. Month 4: 50 paying at blended $120 ARPU.
Launch & Validation Plan
Post in r/n8n and n8n Discord offering free white-label portal setup for 5 agencies in exchange for feedback calls before writing a line of code.
Customer Acquisition Strategy
First customer: DM 20 active posters in n8n Discord who mention client work, offer free 60-day setup in exchange for a case study. Ongoing: r/n8n weekly threads, n8n community forums, YouTube tutorials showing client portal setup in 10 minutes.
What's the competition?
Competition Level
Low
Similar Products
Retool (too complex, not n8n-native), Softr (Airtable-focused, no workflow runs), n8n native UI (no white-label, exposes internal tools). Gap: zero products wrap n8n specifically for agency client delivery.
Competitive Advantage
n8n has no native white-label client portal. Retool and Softr require full app builds. This is purpose-built for n8n agencies with zero config required.
Regulatory Risks
Low regulatory risk. GDPR: agency data stays in their own n8n instance, FlowClient only proxies run metadata.
What's the roadmap?
Feature Roadmap
V1 (launch): portal creation, run history, manual trigger, Stripe metered billing. V2 (month 2-3): custom domain per portal, webhook input forms, usage alerts. V3 (month 4+): Make.com support, white-label email domain, team seats.
Milestone Plan
Phase 1 (Week 1-2): n8n API proxy, portal CRUD, run history table ships. Phase 2 (Week 3-4): Stripe metered billing, manual trigger, Supabase auth live. Phase 3 (Month 2): 5 beta agencies using in production, first paid upgrade.
How do you build it?
Tech Stack
Next.js, n8n REST API, Stripe metered billing, Supabase, Resend — build with Cursor for API layer, v0 for dashboard UI
Suggested Frameworks
Next.js App Router, Supabase Auth, Stripe Billing
Time to Ship
2 weeks
Required Skills
n8n API, Next.js, Stripe metered billing, Supabase RLS.
Resources
n8n REST API docs, Stripe metered billing guide, Supabase RLS docs.
MVP Scope
app/page.tsx (agency landing), app/dashboard/page.tsx (portal list), app/portal/[id]/page.tsx (client view), app/api/n8n/runs/route.ts (proxy to n8n API), app/api/billing/route.ts (Stripe metered), lib/n8n.ts (n8n client), lib/db/schema.ts (Drizzle schema), .env.example (n8n URL + key, Stripe keys)
Core User Journey
Agency signs up -> pastes n8n API key -> creates client portal in 5 min -> client logs in and sees live run history -> agency upgrades to paid.
Architecture Pattern
Agency connects n8n API key -> Supabase stores workspace config -> Next.js portal fetches run data from n8n REST API -> Stripe logs execution events -> monthly invoice auto-sent via Resend.
Data Model
Agency has many ClientPortals. ClientPortal has many WorkflowLinks. WorkflowLink has many RunEvents. RunEvent triggers BillingRecord.
Integration Points
n8n REST API for workflow data, Stripe for metered billing, Supabase for auth and storage, Resend for invoices, Vercel for hosting.
V1 Scope Boundaries
V1 excludes: Make.com support, custom workflow builder, mobile app, team collaboration inside portals, AI workflow suggestions.
Success Definition
A paying agency their client has never heard of FlowClient, sees only the agency brand, and renews without contacting support.
Challenges
Getting agencies to trust a third-party layer sitting in front of their client relationships — this is a distribution and trust problem, not a technical one. The first 10 customers require direct relationship selling, not cold traffic.
Avoid These Pitfalls
Do not build a full no-code workflow editor — that is n8n's job. Do not support Make.com in V1 or scope creep kills the launch. Finding the first 10 paying agencies takes longer than building the product — budget 3x more time for Discord outreach than development.
Security Requirements
Supabase Auth with Google OAuth, RLS on all tables, n8n API keys encrypted at rest via Supabase Vault, rate limiting 60 req/min per IP.
Infrastructure Plan
Vercel for Next.js, Supabase for Postgres and auth, Cloudflare for custom subdomain routing, Sentry for errors, GitHub Actions for CI.
Performance Targets
100 DAU at launch, run history table loads under 500ms, portal page LCP under 2s, n8n API proxy cached for 30s.
Go-Live Checklist
- ☐Security audit complete.
- ☐Payment flow tested end-to-end.
- ☐Sentry error tracking live.
- ☐Vercel monitoring configured.
- ☐Custom domain SSL verified.
- ☐Privacy policy published.
- ☐5 beta agencies signed off.
- ☐Rollback plan documented.
- ☐n8n Discord launch post drafted.
First Run Experience
On first run: a demo agency portal is pre-loaded with 3 sample workflow run events. User can immediately create their own portal by pasting an n8n API key. No manual config required: demo data renders without any real n8n connection.
How to build it, step by step
1. Define Drizzle schema for Agency, ClientPortal, WorkflowLink, RunEvent tables in lib/db/schema.ts. 2. Run npx create-next-app with App Router and Tailwind. 3. Set up Supabase Auth with Google OAuth and RLS on all tables. 4. Build n8n REST API proxy in app/api/n8n/runs/route.ts with API key auth. 5. Build portal list dashboard in app/dashboard using v0 for card components. 6. Build per-client portal page with run history table and manual trigger button. 7. Wire Stripe metered billing product and log execution events on each trigger. 8. Add custom domain support via Next.js middleware subdomain routing. 9. Set up Resend for monthly usage invoice emails to client. 10. Verify: create a test agency, link a real n8n workflow, trigger a run, confirm it appears in the portal and logs a Stripe event.
Generated
June 17, 2026
Model
claude-sonnet-4-6
Disclaimer: Ideas on this site are AI-generated and may contain inaccuracies. Revenue estimates, market demand figures, and financial projections are illustrative assumptions only — not financial advice. Do your own research before making any business or investment decisions. Technology availability, pricing, and market conditions change rapidly; always verify details independently.