Skip to main content
All CollectionsTools
Creating mail trigger callback actions
Creating mail trigger callback actions

You can create actions when using mail triggers in your application.

Betty Blocks avatar
Written by Betty Blocks
Updated over a year ago

Warning!

This is a legacy document. The features described below are only usable within the classic-generation environment.

Currently, Betty Blocks offers faster and more advanced options that are available in next-gen. Before you start working on some new features in your application, consider doing it using the next-gen version. Good luck!

To create a callback email function you need to create a model in your data model with an Email message property. This is the email object. Different actions can be triggered by this property.

Creating an action connected to the email message property

Create an action connected to the model created - this example uses only the Send mail event. You also need to create a 'storage' property for storing mail related information. This is also required for creating trigger callback actions. The Storage property is an additional property that refers to the email message property already created. 

You can have actions based on different triggers. The triggers selected also need to be enabled in the mail server.

Note: If you use the default Betty Blocks mail server, you can ask our support team to set up the triggers you need.

Select actions for triggers

Edit the email message property in the model created and select an action for each Mandrill trigger that can be selected.

Click on the model (A) in the list of models. In the model details, select Properties (B) to open the property details for the model. Click on the New (C) button to create a new property. Select the Email message (D) from the Type menu displayed. The fields associated with this type are displayed.

Note: Actions can only be triggered where the correct trigger is selected in the email components, in this example, Mandrill. If the open event action trigger is not enabled, the action is not triggered.

As shown below, the start mail action begins the process. Additional Bounce mail events are also included. Where the communication over the configured email system fails, a bounce mail event action (C) is triggered.

In the following log example details, an action (bounce mail) is triggered.

Where a user does not have access to the log details, a bounce notification email can be configured to a different mail address.


​

Did this answer your question?