Unsupported Features Reference
Nodes and features not supported on indie.money, with alternatives.
Written By pvdyck
Last updated About 5 hours ago
Unsupported Features Reference
Some n8n nodes and features don't work on indie.money due to Cloudflare Worker constraints. This list explains why and provides alternatives.
Database Nodes
Not Supported: Postgres, MySQL, Redis, MongoDB, Microsoft SQL, SQLite
Reason: Database client npm packages depend on Node.js TCP socket APIs unavailable in Workers.
Alternatives:
- Use HTTP-based APIs or services
- Consider D1 (Cloudflare's SQLite) for serverless database needs
See: Known Limitations
LangChain Vector Stores & Embeddings
Not Supported: Pinecone, Qdrant, Supabase, In-Memory, Redis vector stores, Weaviate, Chroma, embedding nodes
Reason: These require external infrastructure or persistent connections not available in Workers.
Alternatives:
- Use Memory Buffer Window for conversation context
- Call external embedding APIs via HTTP Request node
LangChain External Memory
Not Supported: Motorhead, Postgres, Redis, Xata, Zep, MongoDB-backed memory
Reason: Requires TCP/database connections.
Alternative: Memory Buffer Window for in-conversation context.
Streaming Responses
Not Supported: Real-time streaming from LLMs or external APIs
Reason: Server-Sent Events (SSE) streaming is limited in Workers.
Workaround: Poll for results or use batch responses.
File System Access
Not Supported: Reading/writing local files
Reason: Workers run in a sandboxed environment without file system access.
Alternative: Use R2 for object storage or external services.
TCP Connections
Not Supported: Direct TCP sockets via Node.js net module
Reason: Node.js net and tls modules are not available in Workers. While Workers have cloudflare:sockets, the n8n node ecosystem depends on Node.js-specific APIs.
Alternatives: Use HTTP-based APIs or proxy services.
Long-Running Operations
Limitation: 30-second CPU time limit and 5-minute wall-clock timeout
Reason: The execution engine enforces a 30-second CPU time limit (network I/O wait does not count) and a 5-minute total wall-clock timeout (including I/O wait). Most workflows are bounded by API response times (I/O), not CPU.
Workaround: Split CPU-intensive operations into multiple workflow executions using triggers.