Transactional Messages
Transactional messages are triggered directly via API calls from your product. These messages are delivered instantly to a specific user.
Typical use cases include:
- Account verification, password resets, two-factor authentication, etc
- Billing and subscription-related emails
- Product activity notifications: new comments, assigned tasks, etc
- Product usage alerts: approaching or exceeding plan limits, team member allocations, etc
Transactional emails are often sent via separate tools like Postmark or SendGrid. However, there’s a benefit of having them inside Userlist: you can use the same styling, apply sender profiles and subscription preferences, leverage user data via Liquid, and update the copy without going into code.
Setting up a transactional message
To set up a new transactional message, follow these steps:
- Head over to Transactional in the main navigation and click Add New Message. Type the message name and select the desired channel: email or in-app message.
- Compose the message in the same way as you would compose a workflow message or a broadcast. See this article for details.
- Go to the Instructions tab to see an example payload to trigger this message for a user. See our API documentation for more details on how to send the message via API.
- Go back to the Message tab and click Activate Message.
After the message is live, you’ll be able to find its performance report in the Performance tab.
Using Liquid in transactional messages
You can use Liquid in transactional messages to personalize the content. For example, you can include the user’s name, email address, or any other custom attributes you have set up in Userlist. You can also access any custom properties you passed to the API when triggering the message.
Hello {{user.first_name}},
you have requested a password reset. Click the link below to reset your password:
{{event.password_reset_url}}
If you didn’t request this, please ignore this email.
Best, The {{account.name}} Team