CommunityHire an ExpertSign Up
App Users BasicsUser Email Notifications
App Users Basics

User Email Notifications

Edit notification templates for transactional messages.

User email notifications refer to the transactional messages that are sent in a response to an action users take on an application. In order to ensure these messages are relevant to your app users, Softr allows you to edit email notification templates.

Softr currently supports the below scenarios:

Invite email via password

This email provides a temporary password for users added to the app by an app builder. The email can be sent at any time by the app builder and may be resent if necessary.

Learn how to add users manually.

This email provides a special magic link for users added to the app by an app builder. The email can be sent at any time by the app builder and may be resent if necessary.

Learn how to import users manually.

Verification email

An email sent to allow users to obtain a code to sign in to this app. This email will be automatically triggered when a user requests a login code via the sign-in page.

A Sign in with Email Code block must be used to enable this option.

Forgot password email

An email sent to allow users to reset their password when they have forgotten it. This email will be automatically triggered when a user requests a password reset via the sign-in page.

Make sure you have added Forgot Password Form and Reset Password Form blocks to your app.

Editing notification templates

To edit notification templates, click on the Notifications tab in the Users Menu of Softr Studio. Here you’ll be able to see each of the above notification templates. Click into a template to begin editing.

From here, you can change the subject line, adjust the content of the email, and leverage the power of variables.

Notion image

Variables

Variables are dynamic inputs to your message. They are defined by user and application level data points. For example, the variable @user_name is a user level attribute and will populate as the notification recipient’s name when the email is delivered.

Required variables

Each template has a unique list of required variables. Required variables are critical pieces of information required in each scenario. For example @login_code is required for the Verification email notification. Without it app users would not be able to sign in.

Optional variables

Optional variables can be added to any email template. Leverage optional variables to personalize your messages, making them more relevant for your users. You have the option to add and remove optional variables.

List of variables

Invite email via password

Variable NameRequired
@user_emailYes
@passwordYes
@application_hyperlinkYes
@application_nameNo
@application_domainNo
@application_ownerNo
@user_nameNo
Variable NameRequired
@magic_linkYes
@application_hyperlinkNo
@application_nameNo
@application_domainNo
@application_ownerNo
@user_emailNo
@user_nameNo

Forgot password email

Variable NameRequired
@reset_password_linkYes
@application_hyperlinkNo
@application_nameNo
@application_domainNo
@application_ownerNo
@user_emailNo
@user_nameNo

Sign in with code

Variable NameRequired
@login_codeYes
@application_hyperlinkNo
@application_nameNo
@application_domainNo
@application_ownerNo
@user_emailNo
@user_nameNo

Sender details

You can customize the sender details for your email notifications. To edit Sender Details, click on the Notifications tab in the Users Menu of Softr Studio. Here, you can provide a sender name and email address. The email address does not need to have an actual Inbox, however you should ensure any replies sent to it are forwarded or handled appropriately so you can verify it. Alias emails will still work.

Once you have entered the name and email you want to send from, you will get an email from our service provider, Postmark, asking you to verify the email to enable sending from it. Be sure to click the verification button/link in the Postmark email. Come back to Softr to check that it has been verified. You can always click the Refresh button to re-check.

Notion image

DKIM Authentication

Ensuring that transactional emails from Softr apps reach their intended recipients is crucial for maintaining user engagement and satisfaction. Unfortunately, these emails can sometimes be blocked or end up in spam folders, leading to frustration and additional support overhead. Verifying the Sender Details (like in the step above) is a good first step, but by implementing DKIM (DomainKeys Identified Mail) verification, we can significantly improve email deliverability. This guide will walk you through the process of setting up DKIM for your domain to ensure consistent, reliable email delivery.

Setup

After setting your custom sender details, the DKIM setup option will become available. Clicking on the Verify button will open a popup modal showing you the DKIM records that need to be added to your DNS.

Notion image

  1. Requesting a DKIM record

    • Open the DKIM setup modal. Softr will generate and return a DKIM record for your domain.
  2. Adding the DKIM record to your DNS provider

    • Add the provided DKIM record to your DNS provider. This step is crucial for enabling DKIM for your domain. Below are general instructions for adding DKIM records to various DNS providers:
      • GoDaddy:
        1. Log in to your GoDaddy account.
        2. Go to the DNS management page for your domain.
        3. Click “Add” and select “TXT” as the record type.
        4. In the “Name” field, enter the host name provided in your DKIM record.
        5. In the “Value” field, enter the value provided in your DKIM record.
        6. Save the changes.
      • Cloudflare:
        1. Log in to your Cloudflare account.
        2. Select your domain.
        3. Go to the “DNS” tab.
        4. Click “Add record” and select “TXT” as the record type.
        5. Enter the host name and value provided in your DKIM record.
        6. Save the changes.
      • AWS Route 53:
        1. Log in to the AWS Management Console.
        2. Open the Route 53 console.
        3. Select the hosted zone for your domain.
        4. Click “Create record set.”
        5. Select “TXT - Text” as the record type.
        6. Enter the host name and value provided in your DKIM record.
        7. Save the changes.
      • Google Domains:
        1. Log in to your Google Domains account.
        2. Select your domain.
        3. Click on the “DNS” tab.
        4. In the “Custom resource records” section, click “Add.”
        5. Select “TXT” as the record type.
        6. Enter the host name and value provided in your DKIM record.
        7. Save the changes.
      • Namecheap:
        1. Log in to your Namecheap account.
        2. Select “Domain List” from the left sidebar and click “Manage” next to your domain.
        3. Navigate to the “Advanced DNS” tab.
        4. Click “Add New Record” and select “TXT Record” as the type.
        5. Enter the host name and value provided in your DKIM record.
        6. Save the changes.
  3. Verifying the DKIM record

    • Click the “Verify” button to check the status. Note that DNS changes can take up to 24 hours to come into effect.
    • Once verified, Softr will automatically start signing emails with DKIM for your domain.

Benefits of DKIM

  • Improved deliverability: DKIM ensures that your emails are less likely to be marked as spam or blocked.

  • Enhanced security: DKIM helps verify that your emails are indeed from your domain, reducing the risk of phishing attacks.

  • Consistency: Automating DKIM setup through Postmark’s API saves time and ensures reliable email delivery.

Use these docs with your AI tools

An AI agent can read this documentation directly. You do not need an account or an API key. Everything here is public and read-only.

Query these docs via MCP

Recommended

Add this server to Claude, Claude Code, Cursor, Mistral, or any tool that supports MCP. Your agent can then search Softr Documentation documentation and read it in full, instead of answering from memory.

https://docs.softr.io/mcp
  • searchFind the passages that answer a question.
  • fetchRead one page in full, as Markdown.
  • list_pagesSee every page in this documentation.

Query these docs over HTTP

The same tools also work as plain web requests. Use this for scripts, or for any tool that does not support MCP. There is one endpoint per tool. Arguments go in the query string, and the answer comes back as JSON.

https://docs.softr.io/api/docs/search?query=custom+domain

Read the OpenAPI description. It is built from the same definitions as the tools, so it always matches what the endpoints do.

Read these docs as Markdown

Add .md to any page URL to get its Markdown source. You can also send the headerAccept: text/markdown to the page URL itself.

To read the whole documentation in one file, open llms-full.txt. For a short index of every page, open llms.txt.