Skip to main content

Email

Overview​

The Email service in Blocks OS enables administrators to manage and customize all email communications used across your applications. It provides tools to configure mail servers, create and edit email templates. With flexible configuration options, a visual template editor, and built-in testing features, the Email service ensures teams can design branded, reliable, and secure email workflows that integrate seamlessly with their applications.

To set a configuration read this Guide.

Add a Template​

  1. Go to Core Services → Email. The Templates tab will open by default.
  2. Click the Add Template button. This opens the About the Template page.
  3. Fill in the required details:
    a. Template Name
    b. Email Configuration (select from dropdown; the default configuration will always be available)
    c. Language
    d. Subject
  4. Click Save and Continue. This will open the Template Editor page.
  5. Use the playground editor to design your email:
    a. Drag and drop components from the Content sidebar.
    b. Adjust styles (color, size, alignment, etc.) from the Settings bar.
    c. Switch to Segment View to structure your layout easily.
  6. Click Preview to see how the email will appear to recipients.
  7. Click Save to store your template. Once saved, you’ll see buttons to Send Test Email or Edit Template Details.
  8. Click Send Test Email to send a sample email to the address linked with your Blocks OS account.
  9. Click Yes to confirm.

Email

note

Emails need to be triggered from the code when a new template is created.

View and Manage Templates​

  1. Go to Core Services → Email. The Templates tab displays a table of all email templates.
  2. The table includes:
    a. Predefined templates for frequent use
    b. Custom templates created by users
  3. Use the search field to find templates by name.
  4. Filter templates using:
    a. Configuration dropdown (select preferred configuration)
    b. Language dropdown
  5. To edit a template, click on the desired row. This opens the Edit Template page, where you can update template details or send a test email.

Clone a Template​

To clone an existing email template:

  1. Click the three-dot menu beside the desired email template.
  2. Select Clone Template .
  3. Click Yes to confirm.
note

To migrate from one environment to another environment, please follow Environment Migration

Sending emails in multiple languages​

Every email template has a Language (set in the About the Template step). At send time, Blocks picks the template by matching two things together — the template name and the language. That means a single template name has a separate version for each language: one row per language, all sharing the same name.

To send the same email in more than one language, no coding is required to author the content:

  1. Create the template once for your first language. Follow Add a Template and set the Language.
  2. Add a version for each additional language — reusing the same Template Name. The quickest way is to clone the template, then change the Language and translate the subject and body. Because the name stays the same and only the language differs, these become sibling versions of one logical template.
  3. Use the Language filter in View and Manage Templates to confirm you have a version for every language you intend to send in.

When the email is triggered, Blocks looks up the template whose name matches and whose language matches the language on the send request, and delivers that version.

No automatic fallback

The match on name + language must be exact. Blocks does not auto-detect the recipient's preferred language, and there is no fallback to a default language. If a template for the requested name and language does not exist, the send fails and no email goes out — so make sure every language you send in has its own version under the same name.

Triggering the send

Authoring the per-language templates is fully no-code. The trigger — and the language passed with it — comes from either a Workflow Send Email node (no-code) or a code/API call. In a Workflow you can drive the language from workflow data (for example, the recipient's language), keeping the whole flow no-code.