Managing Notification Templates and Workflows as Code With the SuprSend CLI
A DEV Community post argues that notification assets such as templates, workflows and preferences should be treated as version-controlled configuration rather than edited through dashboards. Keeping them only in a UI can cause missing audit trails, environment drift between staging and production, and broad production access. The author describes using the SuprSend CLI to pull these assets as local JSON files, edit them in an IDE, and push them back after schema validation. Once stored as files, changes gain Git's commit history, diffs and easy reverts. The post also sketches a GitHub Actions job that syncs assets from staging to production when a pull request merges to main.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in