Next.js
Serve your Umiplex Help Page under your own Next.js domain using rewrites.
Next.js can proxy requests to your Help Page using rewrites()
in next.config, without redirecting the visitor away from your domain.
1. Add a rewrite
In next.config.ts (or next.config.js):
const nextConfig = {
async rewrites() {
return [
{
source: "/help",
destination: "https://app.umiplex.com/chat/page/<agentId>",
},
{
source: "/help/:path*",
destination: "https://app.umiplex.com/chat/page/<agentId>/:path*",
},
]
},
}
export default nextConfigReplace <agentId> with your agent's ID (found in your agent's Playground URL),
and /help with whichever path you want to host the page at.
The second rewrite entry (/help/:path*) matters — the Help Page has nested
routes (e.g. a specific conversation), and without it only the top-level page
would proxy correctly.
2. Deploy
Rewrites take effect on your next deploy — no further configuration needed.
Visiting https://www.yoursite.com/help on your own domain will now render your
agent's Help Page, fetched transparently from Umiplex.
Verify
- Visit your rewritten path (e.g.
/help) on your own domain. - Confirm the URL bar still shows your domain, not
app.umiplex.com. - Send a test message and confirm you get a reply — this confirms the proxy is forwarding all sub-paths, not just the initial page load.