Page History

Inbound email actions are most commonly used to process emails. For example, if an incoming email contains “Incident” in the subject line, the system creates an incident record.

Inbound email actions are similar to business rules in the usage of scripts and conditions that perform actions on the target table. Inbound email actions verify emails for defined conditions and marks features that associate an email with a task. If the conditions are met, the inbound email action performs the pre-configured activities. There are two types of them:

• Record Actionaction: runs a specified script.
• Reply Email: when triggered, sends email: sends a reply email.
  

Unlike Notification Rules, inbound email actions enable the user to interact with the records in the system.

For example, while processing an incident in the Information Neededneeded state, the system inserts the body of this email to the Additional Commentcomment field in the Activity Feed when the caller sends their response. To do so, an inbound email action is created. The condition for this action is that the caller's email contains a specific the presence of a certain text in its the subject , and the same task number it includes matches the one as in the incident record. That is, the inbound email action defines what happens in the system after receiving an email.

Image RemovedImage Added

Inbound action chain

Inbound actions include three major groups of parameters:

Email processing chain

The order in which an incoming email is processed is determined by the following parameters:

• A condition that an email should meet for the action to be executed.
• An action type to execute when an email is received.
• Parameters that control the processing flow.

The third group of parameters is required to organize multiple inbound email actions in a way that they check an incoming email to match the condition defined in each of them, in a certain order. The less is the value in the Order field of an inbound action, the earlier this inbound action checks if a received email matches its execution condition. As a result, each email goes through an ordered chain of condition checks, from the inbound action with the least Order value to the one with the biggest, with the following processing logic: One incoming email can trigger execution of none, one or several actions in a row, depending on the values of the Active, Order, and Stop processing when complete fields of the action.

The inbound email actions are processed starting from the action with the lowest Order, according to the following logic:

1. If the inbound email action is active (the Active checkbox is selected), the system starts checking the incoming email according to the action conditions.
   • If the action is not active, the system moves to the next one in Order.
2. The email is checked against the conditions of the action.
   • If the email does not match the conditions, the system skips the action and proceeds to check the next action from Step 1.
3. Depending on the value of the Action type field, a Script is executed, or a Reply email is sent.
4. The
If the Active checkbox is disabled (its value is set tofalse), this inbound action is skipped. The inbound actions with the Active checkbox enabled (its value is set totrue)are processed further.
5. If an email matches no condition of any inbound action, it passes all the way down the processing chain, and no action will be executed.
6. If the condition of an inbound action is matched, the execution of the action script of that inbound action starts. The further processing flow depends on the value of the Stop processing when complete checkbox of this inbound action:is checked
   • If the checkbox is

1. • selected, the

1. • rest of the

1. • actions down the chain are skipped, and the

1. • processing chain is terminated.
   • If the checkbox is not selected, the

1. • system proceeds to the next action and repeats Steps 1–4.
2. The email processing ends when the system completes all active actions or when an action is performed with the Stop processing when complete checkbox selected.

The email processing chain is shown in the diagram below:

Image Added

As a result, one inbound email can trigger execution of none, one or several action scripts in a row, depending on the values of the Active, Order and Stop processing when complete fields in each inbound action defined in the system.

Image Removed

Configure an inbound email action

1. Navigate to System Notification → Inbound Email Actions.
2. Click New and fill in the fields.
3. Click Save or Save and Exitexit to apply the changes.

Inbound Email Action form fields

(function runAction(/*SimpleRecord*/ event, /*SimpleRecord*/ email) {
const newTask = new SimpleRecord('task');
newTask.subject = email.subject;
newTask.description = email.body_text;
if (email.blind_carbon_copy) {
    newTask.attention_required = true;
}
cosnt insertedTaskID = newTask.insert();

Use case

You need to configure an inbound email action implementing the following logic:

• When the system receives an email with the subject containing the keyword “access”“access”, a new incident is created and assigned to the group responsible for security and access to the system and data.

Create an inbound email action as shown below:

(function runAction( /*SimpleRecord*/ event, /*SimpleRecord*/ email) {

    ss.importIncludeScript('EmailHelper');
    const helper = new EmailHelper();

    const letter = email.subject.match('aсcess'); // Keywords checking
    if (letter) {
        const incident = new SimpleRecord('itsm_incident');
        incident.subject = email.subject;
        /* If the sender's address is registered in the system,
        the Caller field will contain reference to an existing User record.
        If the address is unknown, the caller will be defined as Guest */
        incident.caller = helper.userIDbyEmail(helper.parseSender(email.from));

        incident.description = email.body_text;
        incident.state = '-2'; // Registered
        incident.contact_type = '20'; // Email
        incident.assignment_group = '162920380313692887'; // Security Group
        incident.impact = '2'; // Moderate
        incident.urgency = '2'; // Moderate
        const insertedIncidentId = incident.insert();

        if (insertedIncidentId != 0) {
            ss.debug(`Email ${email.sys_id} processing result: Incident with ID ${insertedIncidentId}`);

            const attach = new SimpleAttachment();
            attach.copy('sys_email', email.sys_id, 'itsm_incident', insertedIncidentId);
            return;
        }
        ss.error(`Inbound Action Failed!\nErrors:` + JSON.stringify(incident.getErrors(), null, 2));
    }
})(event, email);

Inbound email action logging

Every inbound email action triggering is logged in the Script Logtable. You can filter these logs using the criteria below:

• Source IS Inbound Action
• Essence Document CONTAINS 0229fa8a-bcbe-1f11.

Recommendations

The incoming mail parsing returns the address value for the From field of a record from the Email (sys_email) table in lower case. 

When searching for a user by the email by email in the Script column, do not use the IS operator because the value of email can be entered with uppercase letters. For example, J.Doe@mail.com.

user.get('email', 'j.doe@mail.com');

Also, do not use the LIKE operator when searching for a user by email because the search will find a user with a similar email, for example, 'raj.doe@mail.com'.

user.get('email', 'like', 'j.doe@mail.com')

The following example shows the script with the userIDbyEmail() method that search searches for a user by email value:

ss.importIncludeScript('EmailHelper');
class MyEmailHelper extends EmailHelper {
    userIDbyEmail(email) {
        const user = new SimpleRecord('user');
        user.addQuery('email', 'startswith', email);
        user.addQuery('email', 'endswith', email);
        user.selectAttributes('sys_id');
        user.setLimit(1);
        user.query();
        if (user.next()) {
            return user.sys_id;
        }
        return this.searchGuest();
    }
}