Skip to navigation

Fyno’s email templates let you create rich emails for both marketing and transactional communication. You can build an email in one of three editors: Stripo, Unlayer or HTML.

Choose an editor

When you add the Email channel to a template, Fyno asks you to choose an editor to create your email template.

EditorUse it to
Stripo Editor (Recommended)Build your email from scratch with multiple blocks, with AMP support and branding capabilities.
Unlayer EditorBuild your email from scratch with multiple blocks, or import JSON from Unlayer.
HTML EditorPaste or upload your HTML, if you already have your HTML template code.

Fyno recommends the Stripo editor because it is easy to use and supports AMP, giving your customers a rich and responsive email experience.

Fields common to every editor

Every editor has the same fields above the design area:

  • Subject: Enter the subject line of the email.

  • Attachment icon (paperclip, next to the subject): Add attachments to the email. See How to add attachments.
  • Run Test and Preview: Send a test email, or preview how the email looks.

You can add placeholders in the subject line to personalize it.

To use any user property in your templates, add it in this format: {{$user.$<user_property>}}. For example, to add Name as a placeholder from the User profile, add it as {{$user.$name}}.

Stripo Editor

Stripo is a drag-and-drop email builder integrated into Fyno. Build your email from scratch using ready-made structures and content blocks, including AMP blocks such as carousels, accordions and forms. You can also save blocks as modules to reuse them in other templates.

To send interactive AMP emails, see AMP Email Template.

Unlayer Editor

Unlayer is a drag-and-drop email builder integrated into Fyno. Build your email from scratch using content blocks, or import a JSON design from Unlayer. You can preview how the email looks on desktop and mobile.

HTML Editor

Use the HTML editor if you already have your HTML template code. Paste your code into the editor, or upload it as a .zip file using the upload icon in the toolbar.

Upload an HTML template as a .zip file

You can upload a custom email template as a .zip file. This lets you include your HTML file along with all the assets it needs, such as images.

Your .zip file must contain:

  • One HTML file. This is used as the email template.
  • All static assets referenced in the HTML, such as images and CSS files.

For example, if your HTML references my_image.jpg, make sure my_image.jpg is also inside the .zip file.

Important guidelines
  • Make sure all asset references in the HTML are correctly linked to files inside the .zip.
  • Keep the structure simple to avoid broken references.

The upload fails if:

  • The .zip file does not contain an HTML file.
  • The .zip file contains more than one HTML file.

If any image or asset is missing, you see a warning message and are asked to re-upload a corrected .zip file with all the required assets.

How to add dynamic content

You can add dynamic content to your templates using one of the four options below:

How to add reusable components

Components let you create elements you want to reuse in other emails, such as a header or footer, so you don’t have to recreate them in every email. Learn more in Components.

How to override email sender details

You can override the sender details configured in your email integration in two ways: using the Notification Event API, or in the email editor. See How to override email sender details.

How to add attachments

You can add static as well as dynamic attachments to emails. See How to add attachments in email.

How to add multiple ‘to’ emails

You can add any number of emails to to in the Notification Event API, as shown below.

Add Multiple To
curl -X POST 'https://api.fyno.io/v1/<WorkspaceID>/test/event' \
-H 'Authorization: Bearer <API_KEY>' \
-H 'Content-Type: application/json' \
-d '{
"event": "ReleaseNote",
"to": {
"email": ["xyz@fyno.io","abc@fyno.io"]
},
"data": {
"company": "Fyno"
}
}'

How to add CC and BCC recipients

You can add CC and BCC recipients to emails. See How to add CC and BCC recipients in email.

How to test an email template

Use this feature to test a template thoroughly before including it in any Notification Event. This ensures early detection and resolution of any potential issues, for a seamless user experience.

1

Click Run Test above the editor. The Test Email template pop-up opens.

2

From the dropdown, choose Email and enter the email address of the recipient, or choose distinct_id and enter it. Make sure to enter the distinct_id of a Test User profile.

3

In Email Integration, select an email integration that is already configured in Fyno.

4

Auto-fill empty placeholders (optional, AI assistance): If your template has placeholders with no sample values, Fyno can fill them using AI so you can test the email. Click Yes to let Fyno fill sample values for the empty placeholders. Once done, you see the message Sample values have been filled.

5

Click Run Test to send the email to the recipient with the selected integration. You see the success or failure message along with a link to the Sent Logs.

Save and go live

Click Save to save the template as a Test version. You can save different versions of the template this way. Use Go Live when you are ready to move your template to the Live version.

If your workspace has a maker-checker workflow enabled for template management, Go Live needs an additional approval step. Choose from your designated approvers, who review and authorize the template changes. See Approval flow for the steps.

1

Make sure the email channel’s state within the subscription topic is set to either On or Off.

2

Make sure the unsubscribe feature is activated for the email channel.

3

Make sure the Enable one-click unsubscribe checkbox is selected.

4

When an email is triggered with this subscription topic, the unsubscribe link is automatically added in the header.

5

When the user clicks the unsubscribe link, they see a pop-up as shown below.

6

Once the user clicks Unsubscribe, their email is added to the email opt-out list for that subscription topic. To view all the users who opted out of any channel, click the subscription topic.

Add the right subscription topic to your Notification Event

Unsubscribes are managed at the subscription topic level, so using the wrong subscription topic with a notification event can unsubscribe users from something they didn’t intend.

The header unsubscribe link is currently available only for the SES and Postmark integrations. Reach out to us if you want to enable it for any other email service provider.

1

In the email editor, add a block for Unsubscribe and highlight the word Unsubscribe.

2

Click the link icon in the toolbar to add a hyperlink to the word.

3

In the link settings on the right, choose Other from the dropdown. In the text box next to it, enter the unsubscribe URL, or enter {{$fyno.$unsubscribe.url}} if you want to shorten the URL using Fyno Shorty.

We suggest using the original URL rather than Fyno Shorty. The URL linked to the Unsubscribe text isn’t visible to users, so Fyno Shorty doesn’t add much here.

4

When the user clicks the unsubscribe link in the email, a pop-up asks them to confirm that they want to unsubscribe from this subscription topic.

5

Once the user clicks Confirm, they see a confirmation message.

6

If the user unsubscribed by mistake, they can click Resubscribe, and they see a success message.

Once a user unsubscribes, Fyno adds their email to the opt-out list of the subscription topic. When you send any email for the same topic, Fyno excludes the user from the payload sent to the service provider, so the user doesn’t receive it. In the Sent Logs, you see this response for unsubscribed users: SUBSCRIPTION “Subscription_topic - User opted-out from channel(channel-state)”.

How to view change logs

To view the history of all the modifications made to a template, use the change logs feature.

Click the history icon at the top right corner of the template page to view the change logs. It shows the following details:

  • Who updated it
  • Which version was updated
  • The date and time it was updated