Create your network path
Sign up, pick your nodeflex.io network path and generate an API key in the portal.
nodeflex.io connects cloud apps to the n8n workflows running inside your network. Your n8n reaches out to us, so there are no inbound ports, VPNs or public webhooks to manage.
Free plan available. No credit card required.
Keep your data and n8n instance where they are. nodeflex.io carries the request in and the result back out.
Sign up, pick your nodeflex.io network path and generate an API key in the portal.
Your n8n opens an outbound connection to hub.nodeflex.io and registers each private workflow by name.
Trigger the remote workflow from your public or private n8n instance, or call the hub directly from your own code with a simple HTTP POST. No need to know IP addresses or configure port ingress rules in your firewall.
Private workflows connect out to the hub, so your firewall never has to open up. Cloud callers only ever see a nodeflex.io endpoint, never your servers.
# Call a private workflow from any cloud app POST https://hub.nodeflex.io/api/workflow/acme/sync-orders x-api-key: <your-api-key> { "payload": { "orderId": 10482 }, "waitForResponse": true, "waitTimeout": 30 }
Route requests from SaaS apps, cloud functions or other n8n instances into your self-hosted n8n.
Hold the request open for a synchronous answer, or get a correlation ID and fetch the result later.
Create and manage API keys in the portal for each app that calls your workflows.
Small messages travel inline. Larger payloads can be offloaded to short-lived storage.
See request counts for the last day, week, month and billing period on your dashboard.
Log in to the portal with a verification code sent to your email. No password to manage.
The Free plan covers your first private workflows. Move up when you need more workflows, executions or larger messages.
No. Your n8n opens an always-connected outbound SignalR (WebSocket) connection to hub.nodeflex.io. Requests come in over that connection, so nothing in your network has to be publicly reachable.
The easiest way is the NodeFlex Execute Workflow node inside n8n: drop it into any workflow to run a private workflow on another instance. You can also trigger a remote workflow with an HTTP POST to the hub, so anything that can send an HTTPS request with an API key works too: SaaS webhooks, cloud functions or scripts.
Set waitForResponse to hold the request open until your workflow finishes, or skip it and poll for the result with the correlation ID you get back. Your private workflow can also send results back itself by triggering a remote workflow through another NodeFlex node. This way your private workflow can send more than one response back to the remote side.
On the Free and Professional plans, if no private workflow is connected for that path, the request fails right away with a clear error, so the caller can retry later. On Enterprise, each workflow trigger can be configured to queue requests for up to 30 minutes until your n8n reconnects.
Yes. Sign up for the Free plan with just your email, then upgrade from the portal whenever you need higher limits.
Set up your first private workflow in minutes, free.