Page History

Inbound email actions allow defining the actions an instance takes when receiving an email. They allow to process inbound email as either an automatic reply or as a record in the system. The processing takes into account the type of incoming mail and other attributes.

They are similar to business-rules in the usage of scripts and conditions that perform actions on the target table. Inbound email actions check the email for some watermark that associates it with a task and checks for other conditions. If the conditions are met, then the inbound email action performs the preconfigured pre-configured activities. They may be of two types:

Record action: setting a value for a field in the target table.
Email reply: sending an a reply email back to the source that triggered the action.

Note
For inbound email processing, the default email account must be configured preliminary. Email accounts configuring is described in the referenced article.

Inbound email actions are most commonly used for processing emails (for example, create a new Incident when received an incoming email containing "Incident" in the subject line).

How to create an inbound email action

Navigate to System Notification → Inbound Email Actions;
Click New, fill in the form and then click Save.

Note
Role required: admin

Inbound Email Actions form fields

Field	Description
Name	The displayed name of the action.
Type	The message type required to run the action. Available choice options: Reply - letters of this type usually have distinctive features, such as watermarks with an for example:In- Subject line beginning with a recognized prefix (optionally); Reply-To email header , or whose subject line begins with a recognized prefix included in message; Forward - forward letters, in line with the reply letters, usually can be distinguished by watermarks, or subject lines, or any other features; New - new letters are the newly created letters, neither reply nor forward; All - these category summarizes all the letters (new and reply and forward letters).
Action type	The action type. Available choice options: Reply Email; Record Action. When the "Reply Email" option is chosen, then the action behavior is to send an email in reply when triggered. When the "Record Action" option is chosen, then the script is running (it should be specified in the Script field).
Active	Select this checkbox to activate the action.
Dsn	Select this checkbox on to trigger the action in response to the Delivery Status Notification letters.
Invitation	Select this checkbox on to trigger the action in response to the Invitation letters.
Order	Enter the number to define the order of action processing. Actions are processed in ascending order (lower numbers are processed first).
Stop Processing	Select this checkbox to terminate other inbound actions after the current action runs.
Reply email	Compose the email message to send to the source that was the trigger of the inbound action
From	Reference to the user, on behalf of which the script is executed, or the reply letter is sent.
Filter conditions	Specify the condition that must be met to trigger the inbound action. Use the Condition Builder to build a filter that fits your needs. You can create complex AND and OR filters, more than one condition in one filter. Once the condition is met and the action is triggered, the email will be processed and/or an event may be created. So the record of the table specified in the Table field is not accessible.
Script	Enter the script that the inbound email action runs. You can use all methods of server-side API classes here,
Table	Choose Select the target table heretable where the action adds or updates records.
Description	Enter the detailed description of what this email action does (this is optional).

Table of Contents

absoluteUrl	true
class	fixedPosition

Page tree

Versions Compared

Old Version 28

New Version 29

Key

How to create an inbound email action

Inbound Email Actions form fields