Deploy as an OEM integration

n8n's OEM deployment option lets you embed and surface n8n's interface inside your own product's UI. This allows your users to build workflows, configure connections, and run workflow automation without leaving your product. n8n branding is required as part of an OEM integration.

This is distinct from using n8n as a backend, where workflows execute behind the scenes and end users never see n8n. In that model, your product calls n8n using a webhook or the API to trigger workflows, and n8n behaves like any other self-hosted service in your infrastructure - your users never see any n8n UI. This is available on all paid plans under the standard license, with no separate agreement needed. OEM deployment is only necessary when you want your users to interact with the n8n editor directly.

What's covered

• Prerequisites: Guidance on CPU, memory, and database requirements for planning your deployment.
• Managing workflows: Patterns for managing workflows across multiple users or organizations within an embedded deployment.
• Token exchange: Authenticate users from your own identity provider through iframe SSO and call n8n APIs on their behalf.
• Workflow templates: Configure a custom workflow template library for your users.
• Credential overwrites: Set OAuth credentials globally so your users can authenticate without seeing or entering client secrets.

Support

Contact n8n support using the email provided when you signed your OEM agreement. The community forum is also available for general questions.