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

Inbound action type criteria

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

Inbound action type criteria

An instance uses a set of criteria to decide what action to take based on the type of message that is sent to the instance.

Figure 1. How an instance matches email to an inbound action type
Table 1. Inbound action type criteria
Inbound email action type Required matching criteria Name of default action (Incident table) Result of default action
Forward The email contains the following conditions:
  1. A subject starting with a recognized forward prefix (even if a watermark or an In-Reply-To header is present).
  2. From <user email> appears anywhere in the email body.
Create Incident (Forwarded) Create new record
Reply The email contains one of the following conditions and the table specified in the email matches the table of the inbound action:
  1. A valid watermark that matches an existing record.
  2. An In-Reply-To email header (when no watermark is present) that matches an existing record.
  3. A subject line starting with a recognized reply prefix (when neither a watermark nor an In-Reply-To header is present) and a valid record number that matches an existing record.
Update Incident (BP) Update existing record
New The email does not meet the conditions for either a reply or forward type inbound email action Create Incident Create new record

If more than one inbound action is available for a particular type, the instance uses the Table field to match the email to a particular table. If there is also more than one action for the inbound action's table, the instance uses the Order field to determine the order in which the actions run.