Notification and Alerting Integration
What you'll learn: How to configure ArgoCD Notifications to send alerts about application sync events to external communication channels like Slack and webhooks.
Why Notifications Matter
When ArgoCD syncs your applications, you want your team to know what's happening—especially when deployments fail or succeed. ArgoCD Notifications acts like a messenger service that watches your application events and sends updates to wherever your team communicates.
Think of it like a doorbell camera: when something happens at your front door (sync event), it alerts you on your phone (Slack, email, etc.) so you don't have to constantly watch the door.
How ArgoCD Notifications Work
ArgoCD Notifications uses triggers and templates to decide when and what to send. You configure:
- Notification services (Slack, webhooks, email endpoints)
- Triggers (sync succeeded, failed, health degraded)
- Templates (message format and content)
- Subscriptions (which apps notify which channels)
Configuration happens in a ConfigMap called argocd-notifications-cm:
apiVersion: v1
kind: ConfigMap
metadata:
name: argocd-notifications-cm
data:
service.slack: |
token: $slack-token
trigger.on-sync-succeeded: |
- when: app.status.operationState.phase in ['Succeeded']
send: [app-sync-succeeded]
template.app-sync-succeeded: |
message: Application {{.app.metadata.name}} synced successfully!
Then subscribe applications using annotations:
metadata:
annotations:
notifications.argoproj.io/subscribe.on-sync-succeeded.slack: my-channel
Key Takeaway: ArgoCD Notifications integrates with external channels to proactively alert teams about sync events, enabling faster response to deployment issues and keeping everyone informed without constantly monitoring the ArgoCD UI.