Email template variables

Pour :Administrateur

View of the 'email template variables' page

Variables are personalization tags that you insert in the content of an email and that are replaced when sending by the real data of the recipient or context.

This page lists all available variables in Unisoft, by usage context.

⚠

Variables are not universal

Not all variables are available in all contexts. A variable that works in a payment email does not necessarily work in a message campaign, and vice versa.

The list below is strict: if a variable is not listed for a given context, it will not be replaced — it will appear as-is in the email received by the recipient.

General syntax

All Unisoft variables follow the same syntax: double opening and closing braces around the variable name.

Form	Syntax
Simple variable	{{variable_name}}

Sensitivity:

• Case sensitive: {{prenom}} works, {{Prenom}} does not work.
• No spaces around the name: {{ prenom }} does not work (use {{prenom}} strictly).
• No conditional variables: no {{#if}}, no {{else}}. The Unisoft templating engine is deliberately minimal.
• No loops: no {{#each items}}...{{/each}}. No dynamic lists.

Context 1 — Message campaigns

Applies to emails sent via the Message Campaigns module (/app/messages/campagnes), whether the content is entered directly or via an email template.

Variable	Will be replaced by	Example
{{nom}}	Last name of the contact, with initial capital	COHEN → Cohen
{{prenom}}	First name of the contact, with initial capital	david → David
{{prenomHE}}	Hebrew first name of the contact, as-is without transformation	דוד
{{mailing_unsubscribe}}	Personalized unsubscribe URL for this recipient	https://api.unisoft.world/mailing/unsubscribe/<org>/<send>

About {{mailing_unsubscribe}}

This variable is automatically injected at the bottom of the email if you do not place it yourself in the content. Concretely:

• If you don't put {{mailing_unsubscribe}} in your email → Unisoft adds a centered Unsubscribe link at the very bottom of the body, just before the </body> tag.
• If you put {{mailing_unsubscribe}} somewhere in your email → Unisoft replaces your tag with the URL, and does not add a block at the bottom.

This is useful if you want to control the position and style of the unsubscribe link.

Example usage in an HTML template:

<p style="font-size: 11px; color: #888; text-align: center;">
  If you no longer wish to receive our communications:
  <a href="{{mailing_unsubscribe}}">click here to unsubscribe</a>
</p>

See Email unsubscribe for the detail of the mechanism.

Context 2 — Form emails

Applies to automatic emails triggered upon submission or validation of a Unisoft form (submitEmailTemplate and valideEmailTemplate fields in the configuration of a form).

Variable	Will be replaced by	Available?
{{nom}}	Last name of the person who submitted the form	✅
{{prenom}}	First name of the person who submitted the form	✅
{{prenomHE}}	Hebrew first name	✅
{{__org_name}}	Name of your Unisoft organization (initial double underscore)	✅
{{montant}}	Amount paid	❌ NOT AVAILABLE
{{devise}}	Payment currency	❌ NOT AVAILABLE

⛔

Warning: no amount / currency variables in form emails

A frequent error is to use {{montant}} or {{devise}} in a form email thinking that the amount paid will be inserted. This is not the case.

If you write "Thank you for paying {{montant}} {{devise}}" in the validation email of a donation form, the recipient will literally receive: "Thank you for paying {{montant}} {{devise}}" with the tags not replaced.

To insert the amount paid in an email, it's the Payment email context (below) that applies — and the templating engine is different.

ℹ

Form email configuration

The Forms modules still mainly exist in legacy interface (not new_ui). Email configuration (submitEmailTemplate, valideEmailTemplate) is done in the form editor — its interface is not documented here. For payment emails linked to a form, it's rather the Payment context that applies.

Context 3 — Payment and tax receipt emails

Applies to automatic emails sent upon a validated payment (confirmation to the donor, sending of the tax receipt).

Variable	Will be replaced by	Available?
{{nom}}	Donor's last name	✅
{{prenom}}	Donor's first name	✅
{{__org_name}}	Name of your Unisoft organization	✅
{{montant}}	Amount paid (number without currency)	✅
{{devise}}	Symbol or code of the currency (€, $, ₪, £)	✅

This is the only context where {{montant}} and {{devise}} work.

Typical example in a tax receipt template:

Dear {{prenom}},

We acknowledge receipt of your donation of {{montant}} {{devise}}
for the benefit of {{__org_name}}.

Please find attached your tax receipt.

Kind regards,
The {{__org_name}} team

ℹ

Payment templates: not a new_ui module

Payment and tax receipt email templates are managed in the configuration of the Payments module (or in EJS files on the Unisoft server side for organizations that have not customized). This management is outside the scope of the Email templates module (which mainly serves campaigns).

Context 4 — System notifications

System notifications (received payment alert sent to the admin, technical error alert, etc.) do not use variables: their content is static, generated by the Unisoft backend.

You cannot customize these notifications via an email template.

Summary table

Overview — which variable works in which context:

Variable	Message campaign	Form email	Payment email	System notif
{{nom}}	✅	✅	✅	❌
{{prenom}}	✅	✅	✅	❌
{{prenomHE}}	✅	✅	❌	❌
{{__org_name}}	❌	✅	✅	❌
{{montant}}	❌	❌	✅	❌
{{devise}}	❌	❌	✅	❌
{{mailing_unsubscribe}}	✅	❌	❌	❌

Behavior of empty variables

When a variable is used but the corresponding data is empty or missing on the contact, Unisoft replaces it by an empty string (not by a default text, not by an error).

Example: a contact without a first name will receive:

Dear Cohen,

instead of:

Dear David Cohen,

⚠

Audit your base before a bulk send

Before sending a campaign with a lot of personalization, check the quality of the contact details of your base:

• How many contacts have a first name entered?
• How many have a Hebrew first name entered (for {{prenomHE}})?

For variables where you have many gaps, either you complete the data upstream, or you avoid these variables for this campaign (use a generic message like "Dear congregant").

Frequent pitfalls

• Incorrect case: {{Prenom}} or {{PRENOM}} are not recognized. Always lowercase.
• Approximately spelled variable: {{prenoms}}, {{first_name}}, {{name}} do not work. Respect the exact syntax above.
• Variable from another context: using {{montant}} in a message campaign → the recipient will literally see {{montant}}.
• Spaces in braces: {{ prenom }} does not work, use {{prenom}}.
• Formatting attempt: {{prenom.toUpperCase()}} does not work, the variables are raw.

Unsupported cases

For information, here is what no Unisoft templating engine knows how to do:

• ❌ Conditional variables ({{#if prenom}}...{{/if}})
• ❌ Loops on a list ({{#each contacts}})
• ❌ Number formatting ({{montant | format: 'currency'}})
• ❌ Calculations ({{montant * 0.66}})
• ❌ Nested variables ({{contact.adresse.ville}})
• ❌ Custom variables defined by the admin (the available variables are fixed by the Unisoft code)

If you need these advanced features, it's generally a signal that the use case should be handled elsewhere than with a simple template (for example: by segmentation into multiple targeted campaigns).

Going further

• Email templates — the management of reusable templates
• Create a message campaign — where to insert variables in a campaign
• Email unsubscribe — detail on {{mailing_unsubscribe}}