Workflows & Alerts - Endpoint Agent Offline

Real-world scenario

Carlos Reyes · IT Admin at Bluewave Labs

Carlos wants an in-app alert to [email protected] when any engineering laptop agent goes offline, with hostname and platform filled in automatically.

Before you begin

Automation Workflows access
At least one enrolled agent
Active workflow with AGENT_OFFLINE trigger

Overview

When an agent misses heartbeats for roughly 2 minutes, a background health sweep marks it offline and emits an AGENT_OFFLINE event. Active automation workflows with matching triggers run their actions (email, in-app alert, Slack, tickets, and more).

Endpoint Agent Offline trigger

In the workflow canvas, the trigger is labeled Endpoint Agent Offline. It matches any agent in your org that transitions to offline. There is no per-device filter on the trigger by default; use a condition node if you need to narrow by hostname or platform.

Workflow did not fire again

If the agent was already offline, the next cron sweep does not re-emit the event. Bring the agent back online (start service, fix network), let it heartbeat, then stop it again to test.

Template variables

These fields are available in In-App Alert and email template actions:

Variable	Example
{{deviceName}}	sophie-linux
{{hostname}}	sophie-linux
{{platform}}	linux, mac, windows
{{previousStatus}}	online or degraded
{{agentVersion}}	1.0.0
{{lastSeenAt}}	ISO timestamp of last heartbeat

Click a chip under Available fields in the In-App Alert sidebar to insert into the focused field. Variables are substituted when the action runs, not in the canvas preview node text.

In-App Alert tips

Example In-App Alert configuration

Title: Agent is offline {{hostname}}
Message: {{deviceName}} on {{platform}} was {{previousStatus}} and stopped responding.
Recipient: Custom value → your work email, or a role such as org owner

Test without waiting for cron

Use Live test on the workflow with sample payload fields filled in, or temporarily stop the agent service with workverge-agentctl stop and wait about 2 minutes.

Build a workflow

1
Create an automation workflow
Go to Automation Workflows, add a canvas workflow, and set the trigger to Endpoint Agent Offline (AGENT_OFFLINE).
2
Add an In-App Alert or email action
Use available fields chips to insert variables like {{hostname}}, {{platform}}, and {{previousStatus}} into title and message.
3
Activate the workflow
Set status to Active and save. The trigger record syncs to the database on save.
4
Wait for a real offline transition
Workflows fire when an agent newly goes offline (heartbeat stale about 2 minutes), not on every health sweep while already offline.

Gallery template

WorkVerge includes a gallery workflow Endpoint Agent Offline Alert that sends email to {{adminEmail}} when org owner is configured. Customize or duplicate it for in-app-only alerts.