Imagine a client asks you to add the appointment time to a reminder email. You change one sentence, send a test, and get a thumbs-up. But the new template expects a time that the existing reschedule flow doesn't send. The preview looks right. The reminder for a rescheduled appointment is the one that breaks.
I would treat that as a release, even if nobody deployed the app that day.
On November 16, Novu announced a new production publish preview. It compares development and production workflows, flags changes that could break existing triggers, and lets an admin or owner choose which changed resources to publish. Novu's environment documentation makes a useful boundary clear: you publish a workflow, not an individual step inside it. A small edit to an email is a reason to review the rest of that workflow, too.
This article was prepared with AI assistance. The appointment reminder is a hypothetical freelance project.
1. Write down who still calls the workflow
Start with the event that causes the message, not the text of the message. For this example, a new booking and a reschedule both send a reminder. List the fields each path actually supplies, using invented test data or a redacted sample. Don't assume the two callers agree just because they use the same workflow name.
I'd run two tests in development: a new booking with the appointment time, and a reschedule using the old payload shape. If that second case doesn't include a time, decide what the customer should see before making the field required. A reminder with a link to the booking details might be acceptable. Guessing a time is not.
2. Separate the requested change from everything else
The client approved a clearer appointment email. That doesn't also approve a new SMS step, a different send condition, or a different notification preference. Compare the selected workflow with production and explain any extra difference in plain language. If the workflow contains an unrelated change you cannot separate with the publish control, hold it until the package matches what was approved.
An AI assistant can help turn the comparison into a checklist. Give it the sanitized change and the expected behavior for each caller. Ask it to flag fields it cannot account for. The person who owns the release still needs to read the comparison and approve what will go live.
3. Give the client a receipt they can use
Novu's workflow docs describe a workflow as the logic that controls what is sent and through which steps. A production confirmation is evidence that the new configuration is live. It isn't evidence that a specific message reached the correct person.
For an authorized controlled check, use an agreed test booking and a test recipient. I'd record the triggering event, which message arrived, what time it displayed, and where the booking link landed. If you only verified the development environment, say that. The receipt should not contain customer data or a promise that every message will deliver.
My handoff would be short: what changed, what stayed the same, which test arrived, and who should investigate if reminders stop. One good receipt is easier to use than a screenshot of a green Publish button.

Top comments (0)