Automation

Last updated on 14.07.2026

Automations handle recurring communications that would otherwise need to be remembered. Once set up, they run reliably in the background.

Example: Birthday greetings

A classic example: Komma checks daily which contacts have a birthday and automatically sends a personalised birthday email. No one needs to keep a list, and no one gets forgotten.

How automations are structured

An automation consists of three parts:

  1. Trigger – when should something happen? (e.g. ‘Contact has a birthday today’, ‘Person has signed up via a form’)
  2. Condition – who does it apply to? (e.g. only contacts with an email address and active newsletter consent)
  3. Action – what happens? (e.g. send a specific email template)

Typical use cases

  • Birthday and anniversary greetings
  • Welcome email following newsletter sign-up
  • Confirmations following a form submission, e.g. for event registrations

Good to know

  • Automations respect unsubscriptions: anyone who no longer wishes to receive emails will not receive any automated messages either.
  • The sending history of automated emails appears as usual in the mailings, so it remains traceable.
  • You can see which triggers are available to your organisation in the Campaigns → Automations section.