Notifications & Subscriptions
Stay informed about what matters. MeetLoyd's notification subscriptions let you choose exactly what events you want to know about across your AI workforce.
The RACI "Informed" Pattern
In traditional RACI matrices, the "I" (Informed) role means keeping stakeholders in the loop without requiring their direct involvement. MeetLoyd brings this pattern to AI operations:
- Subscribe to resources you care about (tasks, agents, workflows, etc.)
- Choose events that matter to you (success, failure, changes)
- Pick channels for delivery (in-app, email, Slack, and more)
Available Resource Types
| Resource | What You'll Be Notified About |
|---|---|
| Tasks | Task starts, completions, failures, timeouts |
| Workflows | Workflow completions, step failures |
| Agents | Agent status changes, activity summaries |
| Teams | Team-wide events, weekly digests |
| Projects | Project updates, milestone achievements |
| Approvals | When your approval is needed |
| Incidents | Security incidents, escalations |
| Reports | New agent reports ready |
Notification Channels
| Channel | Description |
|---|---|
| In-App | Badge on the notification bell, viewable in dropdown |
| Email to your registered address | |
| Slack | Message in your connected Slack workspace |
| Teams | Message in Microsoft Teams |
| Webhook | POST to a custom URL |
| SMS | Text message via Twilio |
| WhatsApp message via Twilio or Meta Cloud API | |
| Telegram | Telegram message via Bot API |
| Signal | Signal message via signal-cli |
| Google Chat | Google Chat via webhooks |
| Keybase | Keybase Chat for secure team messaging |
Event Types
Execution Events
| Event | When It Fires |
|---|---|
at_start | Execution begins |
on_success | Execution completes successfully |
on_failure | Execution fails with error |
on_stuck | Execution times out |
on_cancel | Execution is cancelled |
Lifecycle Events
| Event | When It Fires |
|---|---|
on_create | Resource is created |
on_update | Resource is modified |
on_delete | Resource is removed |
on_change | Any state change |
Special Events
| Event | When It Fires |
|---|---|
on_approval_needed | Approval request awaiting your action |
on_escalation | Issue escalated to higher priority |
daily_digest | Daily summary (scheduled) |
weekly_digest | Weekly summary (scheduled) |
Agent Subscriptions
Agents can also subscribe to notifications, enabling autonomous awareness. Team lead agents can subscribe to team member failures, supervisor agents can monitor project milestones, and watchdog agents can track compliance violations. This enables agent-to-agent awareness without direct coupling.
Subscribing to Notifications
You can subscribe from anywhere in the dashboard. Look for the notification bell icon in resource detail views.
Subscribing to a Task
- Open the task detail view
- Click Subscribe to notifications
- Select which events you want (at start, on success, on failure, on stuck, on cancel)
- Choose your notification channels
- Click Subscribe
Subscribing to an Agent
- Navigate to the agent view in Openspace
- Find the notification subscription section in the header
- Select events (on change, daily digest)
- Choose channels and subscribe
Setting Up Channels
Most channels work automatically once you've connected integrations:
- Slack: Connect via Integrations > Slack
- Teams: Connect via Integrations > Microsoft 365
- Email: Uses your account email by default
Subscription Settings
Digest Mode
Instead of immediate notifications, you can receive periodic summaries:
| Mode | Description |
|---|---|
| Immediate | Get notified right away (default) |
| Hourly | Hourly digest of all events |
| Daily | Daily summary at your preferred time |
| Weekly | Weekly roundup |
Quiet Hours
Pause non-critical notifications during specific times (e.g., 10 PM to 8 AM) to prevent late-night alerts.
Managing Subscriptions
Each resource shows its current subscribers in the detail view. You can modify your subscription events or channels, or unsubscribe at any time.
Best Practices
- Start selective -- subscribe to critical events first (failures, stuck tasks); you can always add more later
- Use digests for routine updates -- agent activity summaries work well as daily digests
- Match channel to urgency -- failures go to Email + Slack; successes go to in-app only; digests go to email
- Set quiet hours -- prevent alert fatigue by pausing non-critical notifications overnight
- Clean up unused subscriptions -- periodically review and remove subscriptions you no longer need
Next: Learn about the Activity Stream for real-time visibility into your AI workforce.