Skip to content


Argo CD Notifications continuously monitors Argo CD applications and provides a flexible way to notify users about important changes in the application state. Using flexible mechanism of triggers and templates you can configure when the notification should be sent as well as notification content. Argo CD Notifications includes the set of useful built-in triggers and templates. So you can just enable them instead of reinventing new ones.

Getting Started

  • Install Argo CD Notifications
kubectl apply -n argocd -f
  • Configure integration with your Slack in argocd-notifications-secret secret:
kubectl apply -n argocd -f - << EOF
apiVersion: v1
kind: Secret
  name: argocd-notifications-secret
  notifiers.yaml: |
      token: <my-token>
type: Opaque
  • Enable built-in trigger in the argocd-notifications-cm config map:
kubectl apply -n argocd -f - << EOF
apiVersion: v1
kind: ConfigMap
  name: argocd-notifications-cm
  config.yaml: |
      - name: on-sync-succeeded
        enabled: true
  • Subscribe to notifications by adding the annotation to the Argo CD application or project:
kubectl patch app <my-app> -n argocd -p '{"metadata": {"annotations": {"":"slack:<my-channel>"}}}' --type merge

Try syncing and application and get the notification once sync is completed.

Helm v3 Getting Started

argocd-notifications is now on Helm Hub as a Helm v3 chart, making it even easier to get started as installing and configuring happen together:

helm repo add argo
helm install argo/argocd-notifications --generate-name \
    --set triggers[0].name=on-sync-succeeded \
    --set triggers[0].enabled=true \
    --set secret.notifiers.slack.enabled=true \
    --set secret.notifiers.slack.token=<my-token>

For more information or to contribute, check out the argoproj/argo-helm repository.