
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-11-2022 07:21 AM
Following the doc (https://docs.servicenow.com/bundle/sandiego-servicenow-platform/page/administer/notification/concept/c_InboundEmailActions.html) we have added a new Inbound Action that I thought would apply to all incoming emails from an accepted domain. We set the order right before the generic "Create INC" inbound action for our instance so it won't apply to the robo-alert emails and such earlier in the Order, and on initial testing it worked like a charm. Unfortunately when tested with an off-company account it failed. We DO have the Domains the emails we expect to be coming from Allowed in System Properties > Email Properties > Inbound Email Configuration, but it still failed. INCs are being created but the new Action failes stating: "Reply Email not sent for 'INC Creation Confirmation ', empty user_id".
That's the point of the though. It's just a courtesy notice that the INC queue is not monitored between the hours of X and Y. Please call Z.
Is there a way to set this up so that emails not associated to sys_user.list will still trigger the Action and send the email? I attempted to set up a User with a 2nd email account and SN only allows 1 email to be assigned to a User from what I can find. What's the best way to accomplish our goal?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-11-2022 11:31 AM
I personally have never used that action type, and might suggest avoiding it altogether. It looks like there might be issues with how it operates anyways (doesn't look to be 100% related to what you're doing, but the workaround is to revert to an inbound action where a script field is present) : Reply inbound email action ignoring execution condition when the referenced record does not exist - ....
I would recommend entertaining a different approach, since the Reply Email function doesn't seem to offer a solution to what you're trying to solve.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-11-2022 11:13 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-11-2022 11:31 AM
I personally have never used that action type, and might suggest avoiding it altogether. It looks like there might be issues with how it operates anyways (doesn't look to be 100% related to what you're doing, but the workaround is to revert to an inbound action where a script field is present) : Reply inbound email action ignoring execution condition when the referenced record does not exist - ....
I would recommend entertaining a different approach, since the Reply Email function doesn't seem to offer a solution to what you're trying to solve.