All Collections
Plugin Questions
Server Configuration
(Plugin) Version History and Template Recovery
(Plugin) Version History and Template Recovery

In this article, you will learn how to connect version history to see previous savings and template recovery function to your Stripo plugin.

Marina Krivenets avatar
Written by Marina Krivenets
Updated over a week ago

This option allows you to provide the ability to your customers to be able to view all previous changes in an open email template in the editor.

It also contains the function to restore any previous email template version from earlier versions. You can place the link (trigger) inside your application by clicking on which the mode of viewing the history of changes of an open email template can be activated.

You don't have to store all versions on your end, as Stripo does it using micro changes (patches). You have to store only the most recent (up-to-date) version on every email template.

If an AutoSave option is activated and configured, all changes made in the editor will automatically be saved to our DB as a patch.

As soon as they are saved, our server will send the request to your end-point set for the AutoSave option with the changed HTML and CSS in order to replace the previous version in your DB. As a result, every change made by a user in the editor will be saved in your DB for that particular email, and you have only the final, most up-to-date version of every template opened in the editor.

*Please note: the editor won't display a user name if it was not passed as one of the parameters with the Plugin initialization.

First of all, we need to enable the "Version History and Template Recovery" option on the Plugin details page.

*Please notice that it's available for paid packages only.

Then, you can place the button/LINK (the trigger) in your application by clicking on which the mode "Version history and Template Recovery" of an opened email template will be activated.

Once this option is activated, please add these config parameters to the Plugin initialization call (see the "Plugin configuration" section).

"userFullName": "YOUR_PLUGIN_USER_NAME",
"versionHistory": {
"changeHistoryLinkId": "YOUR_LINK_ELEMENT_ID",
"onInitialized": "function(lastChangeInfoText)" {
// Do any additional actions here when version history is initialized

If you do not use the AutoSave Option you can independently create the points displayed in the "Version history" section.

To do so, please add this function and call this method every time a template is saved on your end or when you want the corresponding entry to appear in the Version history:

    "POST": "/",
"Content-Type": "application/json",
"Accept": "application/json",
"Body": {
"html": "YOUR_HTML_CODE",
"css": "YOUR_CSS_CODE",
"width": "EMAIL_WIDTH",
"height": "EMAIL_HEIGHT"
"Response status": "200 OK"

This function will create visible endpoints in the Version history and update the data of the last changes. You can independently choose where it should be applied; we recommend that you use it whenever your user clicks on the "Save" button within your app and you should call the "getTemplate" function to take out modified HTML and CSS from the editor in order to save it within your DB.

Thank you for taking the time to read our articles. We hope you will find this information helpful.

If you have any additional questions, please email us at

We would be glad to talk with you.

Did this answer your question?