Avanai's open-source SAP OData node for n8n was downloaded 304 times between October 20 and November 18, 2026, and the people who install it are the buyers Avanai sells to: engineers connecting SAP to automation. But the npm package's homepage and repository fields point to a personal GitHub account, the GitHub README never links to avanai.io or mentions paid help, and some of its install and clone instructions send people to that personal account instead of the avanaihq organisation. Nothing on the path from npm or GitHub tells an SAP team that a certified n8n Elite partner built the node and can take it to production.
First action
Publish a patch release with homepage set to https://avanai.io/n8n-sap/ and repository and bugs set to the avanaihq repository.
How to measure it
Node-sourced working sessions
- Now
- –
- Target
- 3 a month
- By
- 90 days
Steps
Fix package metadata
Set homepage, repository and bugs in package.json to avanai.io/n8n-sap and avanaihq; publish 1.0.1 so npm shows the new links.
Director Engineering, n8n & SAP 1 hour
Fix the README links
Replace every install and clone line that points to the personal account with the avanaihq repository.
Director Engineering, n8n & SAP 1 hour
Add a production section
Five lines under the install docs: maintained by Avanai, what production help looks like, one tagged link.
Director Engineering, n8n & SAP 2 hours
Create the booking path
A contact form on /n8n-sap/ with "SAP + n8n" pre-selected and a source field filled from the UTM tag.
Marketing Lead 1 day
Mirror it in the docs
Point "Contact Avanai for enterprise support" in the node docs to the same tagged path.
Marketing Lead 1 hour
Point the old repository home
Add a notice and link at the top of the personal repository so old links lead to avanaihq.
Director Engineering, n8n & SAP 1 hour
Track monthly
Downloads, stars, issues and sessions by source in one sheet.
Marketing Lead monthly
Why it works
Treat the node as Avanai's best-qualified lead source. Point the npm homepage to avanai.io/n8n-sap and the repository and bug links to avanaihq, fix the install and clone lines in the README, and add a short "Running this in production?" section: who maintains the node, what Avanai does for SAP and n8n teams (production setups, RFC access, governance, support under SLA), and one link to a dedicated booking path. Put UTM tags on every link so the team can see which working sessions started from npm, GitHub or the docs.
Engineers read the npm and GitHub pages before they install; that is where they decide who stands behind a package. A clear maintainer and support line turns anonymous downloads into identifiable conversations at almost no cost, and pointing everything at one repository concentrates stars, issues and contributors where Avanai can see them.
Ready to use
CopyREADME section: Running this in production?
## Running this in production? This node is built and maintained by Avanai, a certified n8n Elite partner (https://avanai.io/n8n-sap/?utm_source=github&utm_medium=readme). We help SAP teams take n8n from a test workflow to governed production: ECC and S/4HANA connectivity, RFC/BAPI access, monitoring and support under SLA. Book a 30-minute working session: https://avanai.io/n8n-sap/?utm_source=github&utm_medium=readme#contact Bugs and feature requests: GitHub Issues (public, free).
Risks and how to handle them
The open-source community reads it as a sales pitch
Keep it to five factual lines below the install docs and keep issues answered in public.
Old links to the personal repository break
Keep the personal repository up with a pointer instead of deleting it.
Evidence
- Open sourcenpm downloads API: 304 downloads of n8n-nodes-sap-odata between October 20 and November 18, 2026.Source
- Open sourcenpm registry: n8n-nodes-sap-odata 1.0.0, first published March 12, 2026, last modified October 16, 2026, 8 versions; the package homepage and repository fields point to a personal GitHub account, not to avanaihq or avanai.io.Source
- Open sourceGitHub repository avanaihq/n8n-nodes-sap-odata: 13 stars, 2 forks, MIT licence, 40 commits; the README has no link to avanai.io and no commercial support offer (help goes to GitHub Issues), and some install and clone instructions point to a personal GitHub account instead of the avanaihq organisation.Source
- n8n partner directoryAvanai's listing: certified n8n Elite partner, Premium listing, "Accepting new clients", 0 reviews; locations Germany, Boston, Zürich and London; services workflow building, process and workflow design, server installation and management, and migration; budgets $1,000 to $100,000+; languages English, German and Hindi; training through Avanai Academy.Source