SAP and n8n
Everyone is talking about the workflow automation angle and the money. Few are talking about what actually makes this hard.
Connecting 1,000+ enterprise integrations with AI agents isn’t a plumbing problem. It’s a semantics problem. Every system speaks a different vocabulary. Finance calls it a “cost center”. HR calls it a “department”. The CRM calls it an “account segment”. These aren’t synonyms and no LLM will reliably reconcile them at runtime across mission-critical processes.
This is exactly why SAP’s value in this deal isn’t just distribution. It’s the semantic layer they’ve spent decades building: ontology-grounded business data, structured process models, governed vocabularies across ERP, HR, supply chain, and finance.
Without shared ontologies, agentic workflows are just very expensive if-statements waiting to fail at the seams. The real bottleneck in enterprise AI orchestration isn’t the model. It isn’t the workflow engine. It’s the absence of a shared conceptual model across systems. Knowledge graphs solve this. Ontologies solve this. They always have.
The plumbing is finally catching up and SAP knows it.
Personally, I totally love n8n and have used it for years for personal automations, data pipelines and whatnot. If you wanna talk about n8n and knowledge graphs, ping me.