how to restrict incident creation from calendar invites for DL

RudhraKAM
Tera Guru

As of now we are creating an Incidents via Inbound action , but when there is a calendar invite , still it is creating Incident , How to restrict that ?

 

I am not able to restrict subject , as it can be any 

 

RudhraKAM_0-1764942196011.png

 

4 REPLIES 4

lpruit2
Kilo Sage

Greetings @RudhraKAM. Can you share any additional details about the logic of your Inbound Action? Once an e-mail is received inbound to ServiceNow, what is your Inbound Action currently checking? 

Its just checking if any email is send to our DL , create an Incident , but when there is a calender invite too , its creating an Incident which we dont want , I tried all ChatGPT options  like adding conditions , checking header none of them works .

Greetings @RudhraKAM. I noticed that when an inbound Outlook calendar invite is received by ServiceNow that it creates an E-mail Attachment record (Related List at the bottom of the Email record) which contains the .ics file. 

 

lpruit2_0-1765508167602.png

 

In theory, you could configure either your Inbound Action or the Notification record itself to perform a query of the Email Attachments table [sys_email_attachment] which has a Reference field back to the Email record. You can check if there is a record on the Email Attachments table that references the current Email AND has a File Name (file_name) that CONTAINS ".ics". If true, then do NOT proceed further. If false, then proceed. I hope this makes sense and is helpful! Interested in what others have to share. I'm not sure what the performance impact would be with performing a GlideRecord query for every inbound Email notification. 

 

lpruit2_1-1765508372242.png

 

 

 

Akshay37
Giga Guru

HI @RudhraKAM ,

 

If it is a calendar invite it should have some difference than other emails in body or header such as, 

ATTENDEE;
ORGANIZER:MAILTO:
LOCATION:
DTSTART:
DTEND:

You can use these parameters to identify and put a condition to restrict the incident creation in inbound action.

 

Thanks,

Akshay