"Inbound Email" Flow Trigger - some limitations I found

[Tom Sienkiewicz]

Hey Everyone, I'm hoping to get some opinions on this from fellow Architects/Devs.

In general I think Flows are a great tool and I try to incorporate them more and more in the apps I design. I do have one issue with the Inbound Email flow trigger though.

It does not seem to be possible to provide any kind of script or even access a system property from the Inbound Email trigger. Meaning it is too "static", at least in my opinion.

Typically, I don't want the flow to process all of the emails, just some subset. Very often that subset means a specific set of mailboxes, which are then being used to redirect to ServiceNow. Depending on mailbox used, flow should behave in a different way.

And yes, I know that we can create a separate flow per mailbox but it is not optimal when you try to design an app that's easily scalable and does not require development to onboard a new team.

So, I can create a condition saying, the flow should react to emails if Recipients is one of MailboxA,MailboXB etc..

But when a new Mailbox pops up, there is still developemnt/new Flow version required to add it!

It would be much better if we could use a System Property or even reference a custom config table from the trigger.

Currently, I did not fidn any way to do so. 

So, I'm thinking about using the good ol' Inbound Action to perform this type of check and then run a Subflow from that action... But it bugs me because it feels like a workaround.

It would be amazing if servicenow allowed adding "javascript:new Include()...." or "javascript:gs.getProperty()" kind of inline scripting in the trigger!

Any ideas/suggestions related to the above? I'm curious what you think!