allv Routines
Configure AI monitoring routines that watch Gmail, Slack, GitHub, Calendar, and workflow activity on a schedule, then send proactive briefings only when something important changed. Repeated successful monitoring patterns can also surface as learned routine suggestions and workflow drafts.
Routines are for proactive monitoring and scheduled check-ins. If you want a retrospective daily or weekly report on completed work, use Digests.
Morning Briefing
08:30 dailySarah needs a reply before 10:00, standup moved to 09:30, and the release note workflow recovered but still needs final approval before publish.
Why Routines Matter
Run scheduled check-ins across Gmail, Slack, GitHub, Calendar, and workflow activity before something slips through the cracks.
Suppress duplicate briefings when nothing meaningful changed so proactive monitoring stays useful instead of becoming another noisy channel.
Repeated successful monitoring patterns can surface as routine suggestions and workflow drafts instead of staying trapped in one-off operator habits.
Monitoring Use Cases
Watch key inbox threads, meetings, and workflow status before the day gets reactive, then deliver one proactive briefing.
Track CRM movement, important replies, and team mentions so the next outreach step happens while momentum is still there.
Check GitHub, Slack, and support activity on a schedule and alert only when the signal crosses the threshold that matters.
Signal Sources
Scan unread or filtered inbox slices that match the configured monitoring query.
Track upcoming events, schedule changes, and tomorrow-prep context for the selected owner.
Apply mention policy, keyword rules, and escalation logic before a briefing is delivered.
Include repository issue and pull-request movement that changes what the owner should see next.
Bring workflow failures, recoveries, and pending approvals into the next proactive brief.
Reuse saved priorities, mission context, and workspace preferences when deciding what matters.
Delivery
Deliver the proactive result back into the workspace where the owner already reviews work.
Send the briefing directly to the owner when the summary should arrive outside the app.
Post the final monitoring briefing into the right team channel when coordination should happen there.
Preview or dispatch the monitoring routine manually before enabling the ongoing schedule.
Configuration
Configure the owner, delivery channel, source policies, and quiet-mode behavior. Monitoring runs can be previewed before activation, suppressed when nothing changed, and routed back into the same approval-aware workflow layer that powers the rest of allv.
Routine Settings
HeartbeatRoutine Mining
Routine mining watches for repeated successful work and surfaces candidate routines from what operators already do.
A learned routine can open as a workflow draft instead of forcing the team to rebuild the automation from scratch.
Routine suggestions stay reviewable before they become active workflows, so the team keeps control over what gets operationalized.
Routines FAQ
It is a scheduled workflow that checks selected sources, decides whether anything meaningful changed, and sends a proactive briefing only when the result is worth seeing.
A routine is proactive and monitoring-focused. A digest is retrospective and summarizes completed work after the reporting window closes.
Quiet mode suppresses repetitive briefings when the underlying signal fingerprint has not changed enough to justify another alert.
Routines can monitor Gmail, Calendar, Slack, GitHub, workflow runs, and workspace memory so the briefing reflects the real signal mix behind the work.
Yes. Operators can run a preview, adjust the cadence or source rules, and then enable the ongoing schedule once the result looks right.
Related features
Use retrospective reports when you want a summary of completed work after the reporting window closes.
Turn a useful monitoring pattern into a reusable workflow with branching, approvals, and recovery.
Bring Gmail, Slack, GitHub, and other sources into routines through one workspace connection layer.
Turn recurring monitoring into a routine your team can rely on every day.
Routines give founders and operators AI monitoring, scheduled check-ins, quiet mode, and proactive briefings tied back to real workflow state.