Creating a Template
A template holds the content Fyno sends for a notification. You can create one template with content for every channel you need, and each channel is edited separately inside the same template.
A template can consist of two types of content:
- Static Content: This portion of the template remains consistent for all recipients and contains the core message or design of your notification.
- Dynamic Content: This part of the template includes placeholders that are dynamically populated with user-specific information. These placeholders can be mapped to data from your data payload, allowing you to personalize the notification content for each recipient. Examples of dynamic content include customer names, SIP amounts, due dates, and other relevant information. Learn more in Dynamic Content.
Supported channels
A channel needs a template before Fyno can send on it. Templates support the following channels.
Create a template
Name the template
Enter a Name. Use something your team will recognize, such as order_shipped or sip-payment-reminder.
Add it to a group (optional)
Choose a group from Add To Group (Optional) to keep related templates together.

The template editor
The editor has four areas. The example below shows an SMS channel, but the layout is the same for every channel.

Header bar
Left panel
- Channels lists every channel in the template. Click a channel to edit it, or click Add to add another channel.
- Search finds placeholders, Handlebars helpers, variables, and components by name.
- Placeholders, Handlebars, System Variables, and Components hold everything you can insert as dynamic content.
Content editor
The channel-specific form where you write the message. Its toolbar includes:
- Reset, which reverts unsaved changes in this channel.
- Clear (eraser icon), which empties the channel’s fields.
- Run Test, which sends a test message to a real recipient.
Preview
A live device preview on the right that shows how the message will appear to the recipient, with sample values filled in for any placeholders.
Add dynamic content
Dynamic content is written using double curly braces, for example {{customer_name}}. At send time, Fyno replaces each one with the matching value. The left panel gives you four sources of dynamic content.
Placeholders
Placeholders are replaced with values from the data payload you send when you trigger a notification.
In the JSON tab, sample values look like this:
Want short or trackable links? Click Configure on the Shorten and track URLs with Fyno Shorty banner inside the placeholder editor. See Fyno Shorty for details.
Placeholder keys can contain letters, numbers, periods (.), underscores (_), and hyphens (-). A key cannot be made up of numbers only.
Handlebars
Handlebars helpers transform values at send time, such as formatting dates, doing arithmetic, changing text case, or showing content only when a condition is true. The editor groups 48 helpers into categories.

See Handlebars for every helper with examples.
System Variables
System Variables are values Fyno already knows, so you do not need to send them in your payload.

To use a user profile property, follow this format:
Components
Components are reusable building blocks, such as a PDF attachment or a shared header, that you create once and use across templates. Click + next to Components to add one, then select it to insert it.

Learn more in Components and Dynamic Content.
Test a template
Send a real message before you attach a template to a notification event, so you can catch problems early.
Click Run Test
Open the channel you want to test and click Run Test at the top of the content editor.
Choose a recipient
Enter the recipient’s destination, such as a mobile number or email address, or enter the distinct_id of a user profile.
If you use a distinct_id, use a test user profile so real customers never receive test messages.
Choose a provider
Select one of the providers already configured for this channel in your integrations.
Send
Click Test. Fyno shows whether the send succeeded or failed, along with a link to the Sent Logs entry.
Save and go live
Every template has Test and Live versions, so you can work on changes without affecting what your users receive.
The version dropdown next to the template name shows which version you are viewing, for example v2 (Test) or v1 (Live).
When a template goes live, every notification event, workflow, and campaign that uses it starts sending the new Live version immediately. Test before you go live.
View change logs
Click the history icon in the header bar to see every change made to the template. Each entry shows:
- Who made the change.
- Which version was changed.
- The date and time of the change.
Request approval to go live
If your workspace has Approval enabled in security settings (a maker-checker workflow), clicking Go Live raises an approval request instead of publishing straight away.
As the requester
As the approver
Add a message and decide when it goes live
In Write a Message, add a short reason for the request. Select Go live on approval to publish automatically once the request is approved. Leave it unselected if you want to publish manually after approval.

Once approved, the version goes live automatically if the requester selected Go Live on approval. Otherwise, the requester clicks Go Live to publish it. See Approval Request for more.




