Proactive Heartbeats

Heartbeats are scheduled checks that let an agent look for changes, summarize what matters, and alert the team when something needs attention.

Where To Use Heartbeats

Heartbeats are useful when you want a recurring check without asking an agent manually every time.

Good examples:

• monitor campaign health
• review incoming leads
• check whether a workflow needs attention
• watch for stale contacts or tasks
• summarize activity in a channel
• inspect a connected tool on a schedule

What You Configure

A heartbeat should define:

• what the agent should check
• how often it should run
• what counts as important
• where the result should go
• who should review alerts
• what the agent may do without approval

Heartbeats vs Workflows

Use Heartbeats for recurring observation and summaries.

Use Workflows for trigger/action automation.

Use both when a heartbeat should identify a condition and a workflow should handle the follow-up.

Recommended Rollout Pattern

1. start with one low-risk check
2. send results to an internal channel
3. review the first few outputs manually
4. tune the prompt and schedule
5. add actions only after the summaries are reliable

Example Heartbeat Prompt

Check new leads from the last 24 hours. Summarize any records missing phone, email, source, or service interest. Do not contact customers. Post the summary to the operations channel.

Troubleshooting

If a heartbeat does not run, check:

• the schedule is enabled
• the agent still exists
• the target channel exists
• required integrations are connected
• the workspace has the needed plan access

If there are too many alerts, narrow what counts as important and reduce the schedule frequency.