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 a 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 catalog of useful triggers and templates. So you can just use them instead of reinventing new ones.

Getting Started

  • Install Argo CD Notifications
kubectl apply -n argocd -f
  • Install Triggers and Templates from the catalog
kubectl apply -n argocd -f
  • Add Email username and password token to argocd-notifications-secret secret
export EMAIL_USER=<your-username>
export PASSWORD=<your-password>
kubectl apply -n argocd -f - << EOF
apiVersion: v1
kind: Secret
  name: argocd-notifications-secret
  email-username: $EMAIL_USER
  email-password: $PASSWORD
type: Opaque
  • Register Email notification service
kubectl patch cm argocd-notifications-cm -n argocd --type merge -p '{"data": {"": "{ username: $email-username, password: $email-password, host:, port: 465, from: $email-username }" }}'
  • Subscribe to notifications by adding the annotation to the Argo CD application or project:
kubectl patch app <my-app> -n argocd -p '{"metadata": {"annotations": {"":"<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.

Kustomize Getting Started

argocd-notification manifests can also be installed using Kustomize. To install argocd-notifications, we recommended saving a tagged release of the install.yaml:

curl -o argocd-notifications-v1.0.2-install.yaml

The tagged release should then be included in a kustomization.yaml:

namespace: argocd
- argocd-notifications-v1.0.2-install.yaml

If you would like to also install Triggers and Templates from the Catalog, we recommend saving a tagged release of the catalog install.yaml:

curl -o argocd-notifications-catalog-v1.0.2-install.yaml

The tagged release should then be patched into the base argocd-notifications install manifest in your kustomization.yaml:

namespace: argocd
- argocd-notifications-v1.0.2-install.yaml
- argocd-notifications-catalog-v1.0.2-install.yaml