Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

Create an inbound email action

Log in to subscribe to topics and get notified when content changes.

Create an inbound email action

You can create inbound email actions to define the actions that the system takes when an email is received.

Before you begin

Role required: admin


  1. Navigate to System Policy > Email > Inbound Actions.
  2. Click New.
  3. Fill in the fields as described in the table.
    Inbound email actions
    Note: You might need to configure the form to see all fields.
    Table 1. Inbound Email Actions form fields
    Field Description
    When to run
    Name Enter a descriptive name for this email action.
    Target table Select the table where the action will add or update records.
    Action type Select the type of action the instance takes. Select Record Action to modify a record in the instance or select Reply Email to have the instance send an email back to the source of the inbound email.
    Active Select this check box to prevent the system from running additional inbound email actions after this one runs. Clear the check box to disable the action.
    Stop processing Select this option to stop processing after this inbound email action runs.
    Type Select the message type required to run the action. The action runs only if the inbound email is of the selected type. Available types are:
    • New: An email that is not recognized as a reply or forward.
    • Reply: An email with a watermark with an In-Reply-To email header, or whose subject line begins with a recognized reply prefix.
    • Forward: An email whose subject line begins with a recognized forward prefix, even if the email also contains a watermark or In-Reply-To header.
    Note: By default, inbound emails of the Forward type always generate new incidents regardless of the presence of a watermark. If this behavior does not match your business logic, you can change the recognized reply and forward prefixes to treat forwards like replies.
    Required roles Specify required roles the sender must have to trigger the inbound action.
    Order Enter a number that specifies when this inbound action runs relative to other inbound actions that use the same target table. The instance processes the action with the lowest order number first.
    From Select the user required to run the action. If a user is selected, the action runs only when the email sender matches the user name. Leave this field blank to perform the action for all users.
    Condition Specify the condition that must evaluate to true to trigger the inbound action. Build a condition with the choice lists or enter a statement that determines when the inbound email action runs. For example:
    email.subject. startsWith ( "chg:" )
    Field actions Specify how information in the email is inserted into the record.

    For example, select [Created by] [From email] [Sender], so that when the request is inserted, you can see who it is for.

    This field appears if the action type is Record Action.
    Reply email Compose the email message to send to the source that triggered the inbound email action.
    Script Enter the script the action runs. Typically, this script uses the validators script include and email variables.

    A template is provided:

    (function runAction(/*GlideRecord*/ current, /*GlideRecord*/ event, /*EmailWrapper*/ email, /*ScopedEmailLogger*/ logger) {
    	// Implement email action here
    })(current, event, email, logger);
    These are the objects available:
    • current: access the record referred to by the inbound email. For example, current.assigned_to accesses the person assigned to the task.
    • event: access one of the parameters of the originating event. For example, event.parm1 accesses the first parameter of the event or event.parm2 for the second parameter. See Events for more information.
    • email: access the inbound current email record. For example, email.subject accesses the content in the subject line of the email. See Accessing email objects with variables for more information.
    • logger: add a message to the log file with the source set to email.<Sys ID of incoming email>. For example: logger.log ("Some information")
    Description Enter a detailed explanation of what this inbound email action does.
    Other fields
    Order Enter a number to define the order in which this email action should be processed. Actions with lower numbers are processed first. For more information. This field is not installed by the Ordered Email Processing plugin.