SMTP Triggers: Special Variables

SMTP Triggers are used to automated the launch of a Scenario via Email.

You can create a customized message action from an email trigger by using the following variables in your saved Action messages for your scenario:

• {{email_from}} - This variable will be replaced by the email's 'From Address'.
• {{email_subject}} - This variable will be replaced by the email's 'Subject'.
• {{email_body}} - This variable will be replaced by the email's 'Message Body'.*

Much like Text Variables, these special variables insert content into your messages. In this case, we're inserting content pulled from the email sent to Omnilert as a triggering event.

For example, if I have an SMTP trigger that is triggered by an email from a weather service, I might want my Scenario's action to use the Subject and the Body from that weather alert email.

To do that, I create a Scenario Action and include the appropriate variables in with my content:

Thus, when my Omnilert SMTP trigger address receives an email, the subject and body are used in my outgoing alerts automatically.

Caution:

If using the above example to relay email content, the triggering email's body should never be completely empty (no text). If no other content is included in your action's message, totally blank message content may not send properly to some endpoints!

If there is a chance of a blank email triggering this scenario, be sure to type in some text content along with the "{{email_body}}" variable. (Any content will do!)

Plain Text Only

The email body of the triggering email should be in plain text format (Content-Type: text/plain).

Other content types, such as text/HTML or rich text formatted email content will not be passed through the {{email_body}} variable.

Most email system will send a plain-text content equivalent, but always test triggers to ensure that the content is passed as desired!