What Pixtex borrows.
Summary
Pixtex draws n8n workflows the way n8n draws them. Doing that faithfully means using two things n8n publishes: the schema that describes every node, and the icons those nodes are drawn with. This page says exactly what is used, where it came from, and under what terms.
Pixtex is not affiliated with, endorsed by, or sponsored by n8n GmbH.
Node schema
Node shapes, port counts, port labels and icon references come from n8n’s own published package data — dist/types/nodes.json in n8n-nodes-base and @n8n/n8n-nodes-langchain, read at version 2.33.0. It covers 563 node types across 599 version variants.
This is factual interface data, not creative work: it is what lets a diagram show a Switch node’s four real outputs instead of guessing from whatever happens to be wired up.
n8n design-system glyphs
n8n draws its core nodes — If, Edit Fields, Wait, Schedule Trigger and 76 others — with generic glyphs it authors itself. Those files are referenced by name only, with no copy shipped in the node packages, so Pixtex vendors them: 80 SVGs copied verbatim from n8n at n8n@2.33.0.
They remain © n8n GmbH under the Sustainable Use License and are notcovered by Pixtex’s own licence.
Third-party brand logos
Icons for services like Slack, Gmail and Notion are trademarks of their respective owners. Pixtex does not redistribute them: they are fetched on demand from n8n’s repository at a pinned release tag, and used only to identify the corresponding service inside a diagram of a workflow that uses it.
A brand logo is never recoloured, cropped or restyled. Only n8n’s own generic glyphs are tinted, because n8n tints them too — the rule is enforced in code, not by convention.
Removal requests
If you own one of these marks and want it gone, email support@pixtex.dev. Icon serving is behind a single switch, so it can be disabled without a code change or redeploy — expect a reply within a few days, not weeks.
See also the terms and privacy policy.