If you try to embed n8n inside Glide’s Web Embed component and it doesn’t load, this isn’t a Glide issue. It’s caused by how the n8n.io domain (or your self-hosted n8n instance) has been configured.
Many websites, including n8n, add security headers that disallow embedding in iframes. This is a common web security practice and not something Glide can override.
Why iframe embedding may be blocked
Website operators often block embedding for reasons such as:
Clickjacking Protection
Prevents attackers from overlaying malicious controls or disguising the interface to trick users into unintended actions.Content and Brand Integrity
Ensures the website’s branding, layout, and overall experience remain consistent and aren’t altered by external sites.Security and Privacy
Reduces risks like cross-site scripting attacks or unintended sharing of user data.Revenue and Traffic Control
Keeps advertising, tracking, and analytics under the operator’s control.Legal and Policy Reasons
Some organizations have legal or policy requirements that limit where and how their content can be displayed.
What this means for Glide users
Because of these restrictions, n8n cannot be embedded in Glide’s Web Embed component. This is determined by the n8n server configuration, not Glide.
If you’re running your own self-hosted n8n instance, you may be able to adjust the security headers to allow embedding—but please be cautious, as this can introduce security risks.