FAQ.md

FAQ

Is this actually running, or just a concept?

It's live. The live demo links to a small public test target whose uptime counter only keeps climbing if AutomatorBot is successfully pinging it on schedule — you can verify that yourself by opening it more than once.

Why isn't the source code here?

The bot handles other people's data — their monitored URLs, access keys, and database records — so the implementation (scheduler internals, database schema, dashboard templates, and credentials handling) is kept private rather than published alongside this documentation. This repo exists to explain the what and why, not to hand out a copy of the how.

What happens if a ping fails?

It's recorded honestly. The monitor's "last result" reflects whatever actually happened — a timeout, a non-2xx response, whatever — rather than being silently retried and hidden. You'll see it in /stats and on the dashboard.

Can other people see my monitored URLs?

No. Every monitor is tied to your Telegram account, and the web dashboard requires your personal access key (from /mykey) to view anything at all. Regenerating that key immediately revokes dashboard access for anyone who had the old one.

Does this work for any kind of URL?

It works for anything that responds to a plain HTTP(S) request — most commonly, free-tier web services (like Render) that spin down after inactivity. It's not a full uptime-monitoring/alerting product; it's specifically built around the "keep it warm" use case.

Is the ping interval configurable per URL?

Currently the interval is set bot-wide rather than per URL, tuned to comfortably beat the sleep timers of the hosting platforms this is built around.

How do I get access to the bot itself?

Message the maintainer on Telegram — this repository is documentation only and doesn't include a way to self-host AutomatorBot.