Known Limitations

Known Limitations

Transparency matters. Here is what works, what does not, and what to expect.

Node-Specific Limitations

These nodes are supported but have specific constraints:

Code & Function Nodes

• Synchronous JavaScript only — no async/await, no Promises, no fetch()
• No network access — cannot make HTTP calls from code
• No server-side modules — standard library not available
• 2-minute CPU limit per code execution
• $getWorkflowStaticData is in-memory only — works within a single Code node but not persisted between executions and not shared across nodes. Cross-execution persistence is intentionally unsupported: n8n stores static data as global mutable state in the workflow DB record, which is an antipattern that breaks under load balancing, causes race conditions with concurrent executions, and does not scale. Use $('NodeName') to pass data between nodes. For cross-execution state, use an external store (database, key-value service, API)

Wait Node

• Maximum 15 minutes — longer waits (hours, days) are rejected when publishing; use seconds or minutes only
• Webhook and form resume not supported — workflows using resume: webhook or resume: form are rejected when publishing; use Time Interval or Specific Time instead
• In-memory only, no persistence across restarts

Webhook Node

• Multiple webhook triggers supported — each gets its own URL
• Supported methods: GET, POST, PUT, PATCH, DELETE, HEAD
• Auth options: Basic Auth, Header Auth

HTTP Request Node

• Bearer and Basic Auth only via Secure Vault — OAuth2, Digest, and custom auth not supported. Use dedicated integration nodes for OAuth services
• In-memory binary support — base64-encoded, ~50MB limit per file. No streaming by ID
• 10-second default timeout per request
• Pagination expressions support $response.body.*, $response.headers.*, $pageCount, and arithmetic (e.g., $pageCount + 1). No ternary operators or method calls

Merge Node

• combineBySql mode NOT supported — use other merge modes (append, combineByFields, combineByPosition, combineAll)

Item Lists Node

• Sort by Code NOT functional — use simple sort or the Sort node instead
• Other operations work: concatenate, limit, summarize, split out items

Remove Duplicates Node

• In-execution dedup only — the following operations require persistent database storage and are not supported:
  • Remove Items Seen in Previous Executions
  • Remove Items Up To Stored Incremental Key
  • Remove Items Up To Stored Date
  • Clear Deduplication History
• Use the in-execution dedup mode (removes duplicates within the current run)

Discord Node

• V2 only — V1 not supported
• In-memory binary — file attachments supported via base64 (~50MB limit)

Telegram Node

• In-memory binary support — direct file/binary uploads via base64 (~50MB limit)
• Can send images/videos via URL or binary

OpenAI Node

• Text and chat completions only
• Not supported: image generation (DALL-E), audio (TTS), assistants API, file operations

Output Parser Structured

• $ref in JSON schemas not supported — may produce incorrect types
• Use inline schema definitions instead of references

Memory Buffer Window

• 1-hour TTL — conversation memory auto-expires after 1 hour of inactivity
• Memory is scoped per workflow instance and session

Agent Node

• V2 and V3 supported — V1 (SQL Agent, Conversational, ReAct, Plan and Execute) requires database access and is not available

Summarization Chain

• JSON input only — binary input mode (nodeInputBinary) is not supported. Use JSON input or connect a Document Loader

Default Data Loader

• JSON data type only — binary document loading (PDF, DOCX, etc.) is not supported. Use JSON data type to load text from previous nodes

Credential Limitations

Not Available

These credential features from n8n are not available on indie.money:

• SSL certificate bypass — The platform enforces SSL validation for all connections. Services with self-signed certificates (some self-hosted instances) cannot skip SSL checks. Affected services: ERPNext, Gotify, Mattermost, WordPress, Zammad
• Custom OAuth scopes — OAuth permissions are configured at the platform level with all common scopes included by default. You cannot customize scopes per connection. LinkedIn includes organization posting scopes automatically. Microsoft Teams includes channel message reading. Discord, Linear, and Webflow use API Key authentication which has full access
• Connection testing — The "Test Connection" button from n8n is not yet available. If your credentials are invalid, you will see an error when the agent first tries to use them

Service-Specific Credential Limitations

Production-Only OAuth Services

These OAuth services connect to their production environment only. Sandbox/test environments are not configurable through OAuth:

• QuickBooks (Production only)
• Salesforce (Production only)

Self-Hosted Services

Most services with self-hosted options show an environment selector (Cloud / Self-Hosted) that reveals a URL field for your instance. If you do not see this option for a service you self-host, contact support.

Platform Limits

• 30-second CPU time per workflow execution (network I/O does not count toward this limit)
• 5-minute wall-clock timeout — total time including network I/O wait
• 50 MB file size limit — files downloaded or uploaded by nodes must be under 50 MB each. See File Handling & Size Limits for details
• 1 MB payload limit — keep JSON data under 1 MB per node for reliable execution

Nodes Not Yet Available

• Database nodes (Postgres, MySQL, Redis, MongoDB) — on the roadmap
• Email nodes (Send Email, IMAP) — requires secure proxy infrastructure
• Scheduled triggers (Cron, Interval) — planned for automated recurring workflows
• Vector stores and embeddings — require external infrastructure
• Document loaders (binary mode) — JSON mode is available, but binary document loading (PDF, DOCX, EPUB) requires file system access

Expression Engine

• Most standard n8n expressions work fine
• No const/let — use var instead
• No template literals — use string concatenation
• Arrow functions are transformed to ES5 automatically

What We Are Working On

Check the roadmap to see what is planned and vote on what you need most. High-demand features get built first.

Found Something Else?

Use the messaging widget in the bottom corner to report issues. Include what you tried, what happened, and what you expected.

Related

• File Handling & Size Limits
• What nodes are supported?
• Code Node
• HTTP Request Node
• Code Node Sandbox Reference