The fastest way to lose a polished client experience is to send them to a portal that says someone else's name at the top. Your client doesn't care that your hosting is "FlowEngine" any more than they care that their email is "Gmail". The work is yours, the relationship is yours, the logo at the top should be yours.
FlowEngine ships with white-label support out of the box. Drop in your agency's logo, set the agency name, and switch the email sender to your own SMTP. Two settings sections, about ten minutes of work, and your clients see something that looks like a product you built.
What white-label changes for your clients
Two things visible to every client who logs in:
- The portal logo and name. Replaces FlowEngine's mark in the client dashboard header. The agency name shows up in invitation emails and browser tab titles too.
- The email sender. Invite emails, password resets, and notifications come from your agency's domain via your SMTP, not from a FlowEngine address.
What it does not change today: the FlowEngine subdomain on the actual n8n instances themselves. That is a per-instance custom-domain setting, covered in the first-instance guide. White-label is the wrapper around the n8n instance, not the n8n URL itself.
Step 1: Set the company name and logo
Open Settings from the sidebar, then click Company in the inner navigation. Scroll to the Branding section.
Two fields:
- Company Name. Your agency's display name. This becomes the page title clients see in their browser tab and the "from" name in invitation emails. Type it in and click Save.
- Logo. Click the upload area or drop in a PNG, JPG, or SVG (max 2 MB). A wordmark works better than a square mark. The logo replaces the FlowEngine mark in the client dashboard header.
That is the whole branding setup. The change is live for every client immediately, no instance restart needed.
Step 2: Send client emails from your own domain
By default, invitation and reset emails go out from a FlowEngine address. For full white-label, plug in your own SMTP. Open Settings → Integrations:
Click Custom Email. Drop in the host, port, username, password, and sender address from your provider (Postmark, Mailgun, AWS SES, Google Workspace - whichever you already use for transactional mail). Save, send a test, and the next invitation a client gets says it is from [email protected] instead of FlowEngine.
This step is the one most agencies skip and it is also the one most likely to make a client think "this is not a real product." A welcome email from a FlowEngine address breaks the illusion in one second flat.
What the client sees
After the two steps above:
- Client gets an email from
[email protected]inviting them to your portal. - Click the link, log in, see a dashboard with your logo at the top and your agency name in the browser tab.
- Every email after that (execution failures, monthly summaries, password resets) keeps the agency branding.
The word "FlowEngine" does not appear anywhere they look unless you put it there yourself.
Why this earns its keep
Two reasons beyond aesthetics. Pricing. If your portal looks like a product you built, you can charge product-style monthly fees rather than hourly retainer. Clients pay for "the Acme automation platform" without needing to understand the underlying stack. Defensibility. When your portal is the thing the client opens daily, switching agencies means losing the portal too. That is a moat unrelated to the actual workflow logic.
FlowEngine bundles white-label into the agency tier and above. The free tier is for personal use without white-label. Check the pricing page for the current tier breakdown.
Try it
If you are already paying for hosting under your client's account but the portal still says "FlowEngine," this is a 10-minute fix. Sign in at flowengine.cloud, open Settings → Company, upload the logo, then jump to Settings → Integrations and wire up Custom Email. The rest follows from there.