Overview
Thedowned_machines webhook tells your system when one or more important machines appear to need attention. Most teams route this event directly into Slack so operators see machine issues where they already work.
Cyberdesk only monitors machines that you explicitly opt in. On a desktop’s detail page, enable Downed machine alerts to include that machine in the monitor.
Machines are not monitored by default. This avoids alerts for desktops that are intentionally offline or only used occasionally.
Send Machine Alerts To Slack
The fastest way to use machine alerts is with Cyberdesk’s existing Slack integration. You do not need to host your own webhook receiver unless you want custom routing logic outside Slack.Create a machine-alert Slack endpoint
Go to Dashboard -> Webhooks -> Endpoints, click + Add Endpoint, then open the destination dropdown in the top right. Choose Send downed machine alerts to Slack.
Connect your workspace and channel
Click Connect to Slack. Slack will ask you to choose the workspace and channel that should receive machine alerts. Approve the connection, and you’ll return to Cyberdesk.
Review the selected event
The connector subscribes to the
downed_machines event and includes a default Slack transformation that formats machine alerts into a structured Slack message.Default Slack transformation
Default Slack transformation
The machine-alert Slack connector includes a default Svix transformation similar to this. You only need to edit it if you want to customize the final Slack message:
When It Fires
Cyberdesk checks opted-in machines on a recurring schedule. A machine appears down when either:- Its Cyberdesk status is not
connected. - Its status is
connected, but Cyberdesk cannot complete a lightweight display dimensions probe after retries.
Enable Monitoring For A Machine
- Go to Dashboard -> Desktops.
- Enable alerts from the Alerts checkbox in the desktops table, or open a desktop and enable Downed machine alerts in the Machine Status card.
- In Dashboard -> Webhooks, make sure your Slack endpoint or webhook endpoint subscribes to
downed_machines.
Payload
Verify And Handle The Event
- TypeScript / Node
- Python
Recommended Alerting Pattern
Useevent_id for idempotency, then fan out to your alerting system. Because Cyberdesk only sends this event when a newly downed machine is found, your receiver usually does not need to dedupe repeated deliveries beyond Svix retry handling.
Svix may retry deliveries when your endpoint fails or times out. Always verify signatures and treat
event_id or the svix-id header as idempotency keys.