The testing and publishing process in Mailbindr provides a safe way to deploy your email templates or update your existing emails in your live instance.
The environment feature replicates a standard development workflow. This is ideal for teams who want to preview their emails in a test environment before deploying into production (or live).
There are 3 different environments available:
This is the environment to create and edit your template. Test emails here can only be sent to users in your organization.
Optional: publish your template in a test environment (or stage) to fully test your workflows involving emails before publishing to your live environment. In this environment you can send emails to anyone.
The version that is visible to your users in your live environment.
You can publish a version from Draft to your Testing or Live environment. The Testing environment step is optional and depends on your internal development workflow. The illustration below shows you can move a version either through Testing first and then Live or directly to Live:
The same workflow applies for moving a version from Testing to Live.
Everytime you publish your changes from Draft to the Testing or Live environment the version number increases. The higher the version number, the newer the template is.
Publishing is the equivalent of a "save" action. You start with V1; once you publish your changes of V1, it becomes V2. And so on.
While you can only edit the version in Draft, you can view the versions published in the Testing and Live environments.
If you want to send emails in Testing or Live you have to specify the environment in your API request (more information about API request in the Getting Started page. If you don't provide an environment in your request the Draft version will be used.
Mailbindr prevents the sending of emails from the Draft environment to the public by mistake. Only versions in the Testing and Live environments can be sent to email addresses outside of your organisation.