Email Routing Rules

The Email Routing Rule form is organized into sections to simplify configuration:
Destination table: Table where the resulting record will be created
Order: Order in which rules are processed. Execution will stop after first match.
Error event: If an error occurs during email receipt & processing, an event can be generated to trigger a notification or other activity in ServiceNow so that administrators are made aware of the issue. Event parameters:
record/current: Email GlideRecord
parm1: Postmaster rule name
parm2: Error generated
Email condition: Email conditions under which to trigger this rule
Email Content
Email subject to: Field on the destination table where the email subject should be placed
Email body to: Field on the destination table where the email body should be placed
AI Content
Summarize email body: Enable summarization of incoming email
Summary to: Field on the destination table where the email summary should be placed
Summary prompt: Instructions to send to AI for email summarization
Draft email reply: Enable drafting of an email reply to the incoming message
Draft to: Field on the destination table where the draft reply should be placed
Draft persona: Persona that should be emulated when drafting the email reply
Draft prompt: Instructions to send to AI for email reply drafting
Enriched Content
Template to apply: Optional record template to apply to the created record
Auto-map fields from email: When enabled, Postmaster will attempt to map fields in the body of the email to fields on the created record
Apply record script: When enabled, you may use server-script to manipulate the target record, adding or updating field values as-needed.
Apply cart/item script: (Catalog only) When enabled, you may use the CartJS API to manipulate the catalog cart prior to order submission
Last updated