Answers about monitoring, billing timing, plans, and security.

PingNodes is an operational monitoring and alerting layer for automation businesses. It watches your n8n workflows and connected infrastructure for problems, then routes alerts and reports so issues surface before a customer notices them.

PingNodes monitors n8n workflow execution failures, silent missed runs, VPS health, Docker container health, SSL certificate expiry, and backup freshness. These are read-only operational signals used for detection — PingNodes does not store your underlying workflow data or business records.

Yes. PingNodes connects to your n8n instances via API to observe execution outcomes. It detects failed or crashed workflow executions in real time and watches for scheduled workflows that missed their expected execution window.

Yes. PingNodes monitors CPU utilization, memory pressure, and storage disk capacity on your host servers, alerting when operational thresholds are breached.

Yes. PingNodes tracks Docker container states, unexpected stops, crash loops, and container restart patterns across your deployment.

Yes. PingNodes continuously tracks SSL/TLS certificate validity for your monitored domains and sends advance warnings well before certificate expiration.

Yes. PingNodes verifies backup file timestamps and storage freshness, notifying your team if automated backup schedules become stale or fail to run.

When a failure occurs, PingNodes calculates an incident fingerprint, applies cooldown rules to coalesce repeat errors, creates a single active incident record, and immediately dispatches an actionable alert card to your configured channels.

All four paid plans — Single, Starter, Growth, and Agency — include the same monitoring and alerting modules. n8n failure monitoring and silent-run monitoring work immediately; VPS health, Docker health, SSL expiry, and backup freshness become active once you connect the relevant integration. Plans differ in how many workspaces you can monitor, not in which modules are available.

No. Monitoring is read-only: PingNodes observes execution outcomes and health signals from your connected systems to detect problems. It does not edit, trigger, or modify your n8n workflows.

Monitoring is best-effort and depends on the availability of underlying infrastructure — Supabase, n8n, Cloudflare, Telegram, email, and push notification networks. PingNodes runs its own self-monitoring and a dead-man's-switch mechanism specifically to detect and alert on this kind of infrastructure problem.

Alerts are routed to your configured channels — including Telegram, Email, and Web Push. Each workspace has granular notification preferences to control which alert categories reach which channel, backed by automatic cooldown and deduplication to prevent alert storms.

Telegram and email alerts are available today, with per-workspace notification preferences to control routing. Browser Web Push exists in the product but is currently unavailable while its delivery infrastructure is under maintenance — do not plan your alerting around it yet.

Every workspace gets a 24-day introductory access window starting when workspace setup begins — about 10 days to complete setup, followed by 14 days of free live monitoring. Finishing setup early does not shorten or restart the window; it is always calculated from your setup start date.

Your paid subscription begins on whichever is later: the date you complete payment, or the date your 24-day introductory window ends. Paid access never starts before your free-access window is over.

Nothing changes immediately. Your workspace keeps running on free access, your payment shows as confirmed, and your subscription shows as scheduled to begin once the introductory window ends. Your billing page always shows access, payment, and subscription as three separate, current states, so this is never ambiguous.

Single (₹399/month), Starter (₹599/month), Growth (₹999/month), and Agency (₹1,999/month) are all available through self-service checkout. Enterprise is handled separately by contacting sales.

Single supports 1 workspace, Starter up to 3, Growth up to 10, and Agency up to 25. A workspace generally represents one business, client, project, or automation environment you want monitored.

Yes. During the current phase, moving to a higher plan is handled by contacting support rather than a self-service switch inside the dashboard.

Contact support before requesting a downgrade that would put you below your current active workspace count. Support will confirm exactly how the affected workspaces are handled before anything changes.

Yes. Deleted workspaces no longer count toward your plan's workspace limit, so deleting one frees a slot for a new workspace under the same plan.

No. Enterprise is Contact Sales only — there is no self-service checkout for the Enterprise plan.

Your billing page shows the payment as failed rather than confirmed, and your workspace keeps its current access state. Contact support if a failed payment affects your access or you are unsure what to do next.

Yes. During the current phase, cancellation is handled by contacting support from your registered account email rather than a self-service dashboard control. Cancelling stops future renewal; your paid access continues through the end of the billing period you already paid for.

Yes. PingNodes uses a workspace-scoped access model — your integrations, events, alerts, and monitoring history are kept separate from other customers' workspaces, even when several workspaces exist under one account.

Only what is needed to monitor the systems you connect — for example your n8n connection details and a Telegram chat target for alerts. Protected credentials such as API keys and tokens are stored in a secrets vault, never in plain application tables, and are never required in public setup materials.

Email support@pingnodes.com, or open the Support page for other ways to get help. Your billing page may separately show "Support" as a workspace access state — that refers to temporary courtesy access after a paid period ends, not our support team.