Appearance
Trust, Privacy & Security
Automation Watchdog is designed to provide monitoring confidence without requiring access to your internal environment, code, or business data.
Connectivity
Outbound-only model
Your workflows send API requests to Automation Watchdog. No inbound connectivity to your environment is required.
Data scope
Operational metadata only
Automation Watchdog monitors timing and workflow-supplied metadata, not your execution logs, process logic, or business records.
Access control
Organization-scoped tokens
API access is controlled with organization-scoped API tokens and user access is managed through organization membership and roles.
Transport
Encrypted communication
Communication takes place over HTTPS, allowing workflows and users to connect securely to the platform.
What Automation Watchdog sees
| Data type | Description | Stored? | Notes |
|---|---|---|---|
| Check-in timestamp | The time a workflow reports activity | Yes | Used to evaluate timing and history |
| Watch identifier | The watch id and watch name chosen by the client | Yes | Used for display, routing, and reporting |
| Watch description | The description provided by the client | Yes | Used for context in the app and alerts |
| Workflow metadata | Optional context such as queue or machine name | Yes | Controlled by the client |
| Execution logs | Internal process logs and stack traces | No | Not transmitted unless a client chooses to place details into their own metadata |
| Business data | Payload data, transactions, or business records | No | Not required for monitoring |
What Automation Watchdog does not require
- inbound firewall exceptions
- direct access to your orchestrator
- direct access to your robots or worker machines
- direct access to your source code or execution logs
How it connects
Automation Watchdog uses a simple outbound API model. If your automation runtime can make an HTTPS request to the API endpoint, it can report status to a watch.
text
https://api.automationwatchdog.comThe user-facing applications are also delivered over HTTPS:
https://app.automationwatchdog.comhttps://docs.automationwatchdog.com
Network requirements
| Initiator | Protocol | Destination | Port | Purpose |
|---|---|---|---|---|
| Workflow, bot, or service | HTTPS | api.automationwatchdog.com | 443 | Secure API requests for activation, check-ins, and deactivation |
| User | HTTPS | app.automationwatchdog.com | 443 | Web application access |
| User | HTTPS | docs.automationwatchdog.com | 443 | Documentation access |
Practical trust summary
Automation Watchdog is intentionally narrow in scope: it is there to receive monitoring signals and evaluate operational expectations. It is not a remote control plane for your environment.