Unsupported Features Reference

Unsupported Features Reference

Some n8n nodes and features don't work on indie.money due to platform constraints. This list explains why and provides alternatives.

Database Nodes

Not Supported: Postgres, MySQL, Redis, MongoDB, Microsoft SQL, SQLite

Reason: Database clients require direct socket connections unavailable on the platform.

Alternatives:

• Use HTTP-based APIs or services
• Consider serverless database alternatives

See: Known Limitations

LangChain Vector Stores & Embeddings

Supported: Supabase, Pinecone, Qdrant vector stores; OpenAI, Ollama, Google Gemini, and Azure OpenAI embeddings

Not Supported: In-Memory, Weaviate, Chroma, Milvus, Zep vector stores; Cohere, HuggingFace, Mistral embeddings

Reason: Unsupported nodes require connection protocols or infrastructure not available on the platform.

Alternatives:

• Use Supabase, Pinecone, or Qdrant for vector storage
• Use Embeddings OpenAI or Embeddings Ollama for text embeddings
• Call other 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 on the platform.

Workaround: Poll for results or use batch responses.

File System Access

Not Supported: Reading/writing local files

Reason: The platform runs in a sandboxed environment without file system access.

Alternative: Use external object storage services (e.g., S3-compatible APIs via HTTP Request).

TCP Connections

Not Supported: Direct socket connections

Reason: Direct socket connections are not available on the platform.

Alternatives: Use HTTP-based APIs or proxy services.

Form Trigger and Send and Wait

Not Supported: Form Trigger.

Send and Wait: Approval responses are supported on communication nodes for owner-funded Agents. Free Text and Custom Form responses, GitHub "Dispatch and Wait," and Send and Wait inside sub-workflows are not supported.

See Known Limitations for supported nodes and response-window details.

Long-Running Operations

Limitation: the workflow's compute limit and 5-minute run limit

Reason: The execution engine enforces the workflow's compute limit (network I/O wait does not count) and a 5-minute run limit (including I/O wait). Most workflows are bounded by API response times (I/O), not CPU.

Workaround: Split CPU-intensive operations into multiple agent executions using triggers.

Integration Nodes with Incompatible Authentication

Not Supported: PostHog, ERPNext

Reason: These nodes use authentication patterns that are incompatible with indie.money's Secure Vault credential proxy:

Alternatives:

• Use the HTTP Request node with manual authentication for these services

Analytics & Metadata Nodes

Not Supported: Track Time Saved (n8n-nodes-base.timeSaved), Execution Data (n8n-nodes-base.executionData)

Reason: These nodes feed n8n's internal insights and execution-search dashboards, which don't exist on indie.money. Track Time Saved is permanently unsupported — the concept is not applicable to a managed runtime. Execution Data is blocked at activation with no replacement. Neither is a temporary gap.

Alternative: None for time-tracking. To persist your own custom metadata, use a Data Table.

Unsupported n8n Triggers

Not Supported:

• Workflow Trigger (n8n-nodes-base.workflowTrigger) — Deprecated by n8n. Fired on workflow lifecycle events (activated, updated) that don't apply to indie.money's managed runtime.

Alternatives:

• Use Execute Workflow Trigger for sub-workflow calls
• Use Schedule Trigger or Webhook for event-driven workflows
• Use Stop and Error + IF nodes for in-agent error handling

Summary

Related

• What nodes are supported?
• Known Limitations
• Technical Architecture