Service status
Get help when a connection stops working.
Check whether the PulserNode API control plane is reachable right now, then use the steps below for account-specific recovery. The check does not measure every PulserNode component or your n8n instance.
Live check
PulserNode API
Checking PulserNode control-plane reachability
This check confirms only that the PulserNode API liveness endpoint answered. It does not measure the worker, MCP server, billing, or your n8n instance. Check your instance on Connections.
Recover your workspace
If the workspace cannot load, check the connection to your own n8n instance first. A PulserNode workspace error may include a correlation ID; include it in your support email so we can trace the request.
Check the n8n connection
Open Connections and run the connection check. Confirm your n8n URL is reachable and the API key is current.
Retry the workspace
After correcting the connection, return to Workflows and retry. Keep any correlation ID shown by the error panel.
Contact support
Email hello@pulsernode.com with the affected route, approximate time, and correlation ID. Do not include API keys or workflow credentials.
For operational details about retries and recovery, see Operations documentation.