[Bug]:

[jeremymoll]

Bug Description

Installing n8n-nodes-cloudflare community node npm package throws error when n8n-nodes-cloudflare-vectorize plugin already present.

This occurs in the opposite direction as well (installing n8n-nodes-cloudflare-vectorize when n8n-nodes-cloudflare already present.

Links:

n8n-nodes-cloudflare-vectorize
on npm
on Github

n8n-nodes-cloudflare
on npm
on Github

n8n Version

2.3.6

n8n-nodes-cloudflare Version

all

[ARHAEEM]

📋 Status Update

Thank you for reporting this conflict. This is a known limitation due to both packages registering a node with the same internal name (cloudflareVectorize).

Current Solution

We've added migration documentation in the README with guidance:

1. Uninstall the standalone n8n-nodes-cloudflare-vectorize package
2. Use the built-in Vectorize node from n8n-nodes-cloudflare instead

The built-in Vectorize node in this package now includes:

• ✅ Updated v2 API endpoints
• ✅ Proper NDJSON format support for upsert/insert
• ✅ Dimension validation (40-1536)
• ✅ Improved error handling

Why This Happens

n8n requires unique node names across all installed packages. Both packages use cloudflareVectorize as the node identifier, causing the conflict.

Options Considered

Option	Pros	Cons
Rename our node	Avoids conflict	Breaking change for existing users
Migration docs (current)	No breaking change	Requires manual user action
Coordinate with other maintainer	Best long-term	Requires external cooperation

Recommendation

If you need Cloudflare Vectorize functionality, we recommend using this package (n8n-nodes-cloudflare) as it's actively maintained and includes the full Cloudflare suite. The standalone Vectorize package appears to be less actively updated.

We're open to discussing other solutions. Feel free to share your thoughts!

[ARHAEEM]

Just updated the README to include the issue as an example of conflicts.

https://github.com/Automations-Project/n8n-nodes-cloudflare#%EF%B8%8F-installation-notes

[jeremymoll]

Thank you!