Public documentation

Learn the PingNodes product structure before you log in.

Use this public documentation index to understand setup, monitoring scope, alert delivery, reporting, workspace structure, and public safety boundaries without opening protected account pages.

Documentation index

These guides explain the customer-facing product shape. They do not expose internal architecture files, private workflow details, secrets, or customer data.

Getting started

The safest first pass for understanding PingNodes before you connect anything.

What PingNodes monitorsAvailable
Review the operational checks PingNodes can run today and which ones still need setup.
Open related page
How workspaces workAvailable
One workspace represents one business, client, project, or automation environment.
Open related page
Test and live lifecycleAvailable
Setup happens before live monitoring, and billing activation stays server-controlled.
Open related page
Connecting n8nSetup required
PingNodes needs the workspace-specific n8n connection before failure and missed-run monitoring can start.
Open related page
Connecting TelegramSetup required
Telegram delivery depends on your workspace integration and preferences configuration.
Open related page
Connecting a VPS agentSetup required
VPS and Docker signals depend on the registered host and first heartbeat.
Open related page

Monitoring

Operational visibility PingNodes is designed to provide without storing unnecessary customer payloads.

n8n failuresAvailable
Detect failed executions that need attention.
Open related page
Silent missed runsAvailable
Surface workflows that stop running even when no explicit failure event appears.
Open related page
VPS healthSetup required
Heartbeat and machine-health checks become visible after VPS monitoring is configured.
Open related page
Docker healthSetup required
Docker monitoring rides the VPS connection rather than creating a second installer flow.
Open related page
SSL expirySetup required
SSL checks depend on the domains you register for monitoring.
Open related page
Backup freshnessSetup required
Backup freshness is public-facing, but coverage still depends on configured sources and current PingNodes-side support.
Open related page

Alerts and reports

What PingNodes can send and what stays intentionally unavailable until its delivery path is ready.

Telegram alertsAvailable
Controlled alert delivery for urgent operational issues.
Open related page
Email alertsAvailable
Email delivery is available for configured workspaces and remains preference-aware.
Open related page
Notification preferencesAvailable
Workspace-level notification settings help control channel noise and delivery scope.
Open related page
Cooldown and deduplicationAvailable
PingNodes avoids repeating identical alerts every time the same issue surfaces.
Open related page
Daily digestAvailable
Operational summaries help you confirm what PingNodes observed during the day.
Open related page
Weekly reportAvailable
A broader reporting surface for recent operational activity and patterns.
Open related page

Account and workspace

Public-safe guidance for what customers manage after signup.

Workspace settingsAvailable
Use workspace-level settings to keep operational scope separated.
Open related page
Profile and passwordAvailable
Account management remains protected and is not handled on the public site.
Notification preferencesAvailable
Channel settings stay tied to the signed-in workspace context.
Open related page
Multi-workspace managementAvailable
Freelancers and agencies can plan around isolated customer workspaces instead of shared state.
Open related page

Safety

Guardrails that shape the public product promise.

Tenant isolationAvailable
Customer workspaces are positioned as separate operational scopes, not pooled records.
Open related page
Operational metadata onlyAvailable
PingNodes is positioned around monitoring metadata rather than customer payload storage.
Open related page
Secrets and credentialsAvailable
Public setup guidance should explain safe handling without ever exposing real secret values.
Open related page
Web Push unavailable statusUnavailable
Browser Web Push remains unavailable while its delivery infrastructure is under maintenance.
Open related page
Billing activation statusAvailable
PingNodes should not imply self-activated checkout or instant paid activation from the public site.
Open related page

Next step

Use setup help when you are ready to connect a real workspace.

Documentation explains the surface area. Setup help turns that into a practical, public-safe onboarding path.

Loading...Open setup help Contact support