Back to changelog

v2026.6.6-0dd9fc6
  • Automation
  • Developer Experience

Meet the automations engine

React to what happens in your space: triggers like content.published fire configurable actions — webhooks, notifications and more — with execution history and replay built in.

Publishing content is rarely the end of the story — caches need purging, teams need pinging, downstream systems need to know. The new automations engine makes those follow-ups part of the CMS:

  • Triggers — react to space events, including content.published and content.unpublished
  • Actions — compose what happens next, from webhooks to notifications, defined once and reused across automations
  • Observability — every execution is recorded with status and payload; failed runs can be inspected and replayed
  • Statistics — trends and summaries show what your automations are actually doing

It's the difference between a CMS that stores content and one that participates in your workflow.