Docs
n8n compatibility
Which instances PulserNode can connect to, and exactly which parts of n8n it relies on.
1. Supported versions
Self-hosted n8n 2.x, reachable from the internet over HTTPS, with the public API enabled and an API key created in n8n's own settings.
| Line | Version | Status |
|---|---|---|
| Current | 2.31.1 | Probe, create, update, activate, webhook execution, and execution collection verified |
| Previous | 2.30.5 | Supported, full contract run pending |
| Oldest | 2.29.11 | Supported, full contract run pending |
When you connect, PulserNode probes your instance and reports which capabilities it found, rather than failing later on a call your version does not support.
2. Endpoints PulserNode calls
| Purpose | Endpoint | Notes |
|---|---|---|
| Reachability and capability probe | GET /api/v1/workflows?limit=1 | Also confirms workflow listing |
| Execution capability | GET /api/v1/executions?limit=1 | May be off when execution saving is disabled |
| Credential capability | GET /api/v1/credentials/schema/httpBasicAuth | Presence check only |
| Node catalog | GET /types/nodes.json | The nodes your instance has installed |
| Workflow create, update, activate | /api/v1/workflows[/:id][/activate] | Used for builds, snapshots, and rollback |
| Execution collection | GET /api/v1/executions | Payloads are redacted before leaving the API |
3. What PulserNode never uses
- Editor-private endpoints.
- Your editor login or its credentials.
- A proxy in front of the editor, or a broker for editor sessions.
4. Network requirements
Your instance must be reachable over HTTPS from PulserNode's servers. Addresses on private networks and localhost are refused in production, whatever the connection says. If your n8n sits behind a firewall, allow inbound HTTPS to its public address.
Upgrading n8n is always your decision. PulserNode documents compatibility; it never upgrades an instance.