n8n has no built-in SAP node: n8n’s integrations documentation lists none. SAP community nodes connect in different ways: most talk to SAP’s OData services (V2 and V4) directly, one goes through a separate server that holds the SAP connections, one needs a vendor’s connector installed inside SAP, and others read SAP HANA databases or use SAP AI Core models. This guide compares them, using the description and README each author publishes on npm and our own download data.
SAP community nodes
Our SAP hub lists 12 packages that pass our quality rule, with 635 npm downloads a week between them. The most downloaded, with the description each author gives on npm (weekly npm downloads as of 28 October 2026):
| Package | Weekly downloads | Latest version | Author’s description |
|---|---|---|---|
| n8n-nodes-sap-odata-guard | 434 | 0.4.0-beta.4 (24 October 2026) | Logali SAP OData Guard: OData reads and writes with automatic metadata discovery and optional credential policies |
| n8n-nodes-sap-odata | 63 | 1.0.0 (2 October 2026) | SAP OData integration (V2 and V4) with trigger support |
| n8n-nodes-guniweb-sap | 33 | 0.3.1 (15 October 2026) | SAP S/4HANA and ECC through the GuniWeb SAP MCP Server: OData, function imports, batch and IDoc, as workflow steps |
| n8n-nodes-sap-hana-2 | 32 | 1.0.3 (13 February 2026) | Read data from SAP HANA databases and HDI containers |
| n8n-nodes-sap | 21 | 0.1.9 (22 September 2026) | Connect SAP systems through the NeKu AI OData connector |
| n8n-nodes-sap-ai-core | 14 | 1.0.1 (10 August 2025) | SAP AI Core LLM and embeddings |
Versions and dates come from the npm registry. Weekly downloads: npm, last 7 days, adjusted for npm outage days.
n8n-nodes-sap-odata-guard
The most downloaded SAP package, from Logali Group. Its README calls the current version a candidate for controlled, non-production evaluation, and the version on npm is a beta. It discovers the SAP services you can see and supports Get, Get Many, Create, Update and Delete on OData V2 and V4; actions, batches and triggers aren’t implemented. Its focus is control over what a workflow may touch: leave Service Policies JSON empty and the node loads entities and fields from the service’s live metadata, with SAP’s own user permissions deciding access, or fill it in and the credential is limited to exactly what the policy lists. It signs in with basic auth or OAuth2 client credentials, fetches a CSRF token before every change, and only retries reads, never writes.
n8n-nodes-sap-odata
Its README marks 1.0.0 as the first stable release, with new features published as betas. It covers create, read, update and delete, function imports and V4 actions and functions, and discovers OData services from the SAP Gateway catalog on premise or S/4HANA. A trigger node receives SAP events by webhook, with HMAC authentication, rate limiting and an IP allowlist. Authentication is basic auth for on-premise SAP or OAuth2 client credentials for SAP Cloud and BTP.
n8n-nodes-guniweb-sap
Works with SAP S/4HANA and SAP ECC through the GuniWeb SAP MCP Server, which you run yourself, for example as a container next to n8n. The server holds the SAP connections and credentials, and n8n only gets an access token, which can be read-only. The node runs OData queries, reads and writes (V2 and V4), function imports and actions, $batch requests, and sends or tracks IDocs over HTTP and XML. Its README explains why it’s a regular node rather than the MCP Client in an AI agent: the workflow decides exactly which operation runs, with no language model involved unless you attach the node to an agent as a tool.
Other packages
- n8n-nodes-sap-hana-2: reads tables from SAP HANA databases and SAP HANA Cloud HDI containers, with WHERE filters, columns, sorting and limits. Its README says it is for self-hosted n8n only.
- n8n-nodes-sap: sends data to SAP through the NeKu.AI OData wrapper. Its README says the NeKu.AI Connector must be installed and set up in your SAP system first, on request from the vendor.
- n8n-nodes-sap-ai-core: text generation and chat with LLMs deployed in SAP AI Core on SAP BTP, with OAuth2. Its README also says it is for self-hosted n8n only.
Check each node page here for the latest release and, where it has one, its GitHub repository for open issues before you build on a package.
How to choose
- OData reads and writes with SAP events triggering workflows: n8n-nodes-sap-odata, the one with a stable release and a trigger.
- Strict limits on which services and fields a credential can use: n8n-nodes-sap-odata-guard, keeping in mind that its README calls it a non-production candidate.
- SAP credentials kept out of n8n, batches or IDocs: n8n-nodes-guniweb-sap with its MCP server.
- Read data straight from SAP HANA: n8n-nodes-sap-hana-2.
- Models deployed in SAP AI Core: n8n-nodes-sap-ai-core.
To install a package on a self-hosted instance, an owner or admin enters its npm name in Settings > Community Nodes; full steps are in How to Install n8n Community Nodes. On n8n Cloud only verified community nodes can be installed, see Verified vs Unverified n8n Community Nodes. Similar guides: Bitrix24 and Twenty CRM.
FAQ
Does n8n have an SAP node?
Not a built-in one. SAP support comes from community nodes, most of them for SAP OData services.
How does n8n connect to SAP S/4HANA?
Mostly through OData: n8n-nodes-sap-odata and n8n-nodes-sap-odata-guard call OData V2 and V4 services with basic auth (on premise) or OAuth2 client credentials (SAP Cloud and BTP). n8n-nodes-guniweb-sap goes through its own server instead.
Can n8n send IDocs to SAP?
n8n-nodes-guniweb-sap sends and tracks IDocs over HTTP and XML through the GuniWeb SAP MCP Server, which must run with write access enabled.
What is the most used SAP community node?
n8n-nodes-sap-odata-guard, with 434 weekly npm downloads on 28 October 2026.
