Notification Types and Workflow Patterns
This document outlines the notification framework design and patterns for building agentic workflows around creative sync events and campaign health monitoring.Notification Architecture
Resource.Action Taxonomy
The notification system uses a clearresource.action
taxonomy that enables agents to understand both what changed and what action is needed:
Notification Structure
Notifications use a minimal, action-oriented structure:Workflow Patterns
1. Creative Sync Workflows
Pattern: Handle Sync Failures
Pattern: Monitor Approval Status
2. Campaign Health Workflows
Pattern: Detect Unhealthy Campaigns
Pattern: Missing Creatives Alert
3. Proactive Monitoring Workflows
Pattern: Sales Agent Health Monitoring
Integration Patterns
MCP Tool Integration
Enhanced tools automatically generate notifications:Health Data Integration
Campaign and creative tools include health metrics:Best Practices
For Agents
- Filter by Urgency: Process high-urgency notifications first
- Batch Similar Actions: Group related creative updates, format changes
- Monitor Patterns: Track recurring issues to identify systematic problems
- Acknowledge Completed Actions: Mark notifications as acknowledged after resolution
For Integration
- Use Structured Data: Always include relevant IDs (creativeId, campaignId, etc.)
- Provide Clear Actions: Specify exactly what the agent should do
- Include Context: Add rejection reasons, error details for debugging
- Set Appropriate Urgency: Reserve “high” for launch-blocking issues
Notification Filtering
Performance Considerations
- Deduplication: Similar notifications within 5-minute windows are deduplicated
- Retention: Notifications are automatically cleaned up after 30 days
- Batching: Related notifications (e.g., multiple creative sync failures) can be batched
- Indexing: Notifications are indexed by
customerId
,brandAgentId
, andtype
for fast filtering