Skip to content

Uploading your emails to Emarsys

Setting up your your Emarsys API Key โ€‹

To upload your email campaigns from any Emailify Figma designs, you'll need to create a WSSE key in Emarsys, set the permissions for it, and then use the generated API key credentials to connect Emailify to your Emarsys account.

Creating your Emarsys WSSE key โ€‹

The first step is to create your WSSE key in Emarsys (please note that you'll need to be an account owner to have permission to do this) and then navigate to Management -> Security Settings -> API Credentials to create your WSSE key.

Setting your API key permissions โ€‹

After you've created your key and stored your username and key somewhere safe (to paste into the Emailify Figma plugin in the next step below), you will also need to enable the API endpoint permissions below for the API integration to work as expected:

  • campaign.create
  • campaign.update
  • contactlist.list

Uploading your HTML from Emailify โ€‹

In the Emailify export panel, select the Emarsys option from the dropdown list, then paste in a valid Emarsys API credentials (as per the previous step above); once Emarsys is authenticated in the plugin, you'll need to select the Contact List you'd like the campaign to be sent to later, along with the From Name and From Email address that the campaign will be sent from later, too.

When you're ready, click the Upload To Emarsys button to start exporting the emails you've selected from Figma to HTML, and have them automatically be uploaded to your Emarsys campaigns.

Updating Emarsys Templates uploaded from Emailify โ€‹

If you'd like to have your Emarsys templates automatically update instead of being created as new templates each time, you can optionally enable the Enable Updatable Templates toggle in the plugin's export settings (when the Emarsys option is selected).

This will automatically append a emarsysTemplateId value to the Figma frame's layer name that was uploaded, and then re-use that ID when the same frame is re-uploaded to Emarsys via the API upon the next export from the plugin.