If I complicate this too much let me know.
We have one large single inbound action and dozens of "smaller" ones that are purpose built. Our one large action accepts email from 20-30 email addresses (could be more by now, I don't keep track but simply keep adding them in). Within the action we "split" the addresses into assignment groups (e.g. IT is in charge of techsupport@ourdomain.com, itsupport@ourdomain.com, ithelp@ourdomain.com) to create the Incidents.
We do have the odd case where an email needs to trigger multiple record creations. In these case we just populate our conditional logic appropriate. For example an email from our Server Room environmental warning system may create an Incident to investigate the immediate cause (high temperature) and a Request to investigate how to prevent it in the future (higher capacity AC units).
So our typical flow is one email generates one record (Incident, etc.) and what that record contains is custom to the email address (e.g. Category, Assignment Group). However there are a handful that actually create/update multiple records.
In short, yes, each of the email addresses creates it's own record through the single inbound action. The values in the record created are different for each email address that created it (like Assignment Group).
Because I sometimes type too much I will share some experience. Having one large condition will also be more to maintain, and the risk brought forward with something as simple as a typo could impact all of those addresses. I am not a fan of this level of risk, and would ideally like to see our one big inbound action split apart into department-level (or work-unit level) pieces. That way if we accidentally break one the impact is smaller, and when we do a change request we are getting the right approvals because it only impacts one area.
The challenge is breaking apart a perfectly functional one will create a large amount of work and we are already quite busy doing other development that will generate other more direct benefits. If I was developing from scratch I would instead use multiple inbound actions and not "stop processing" automatically, but rather only if I found and matched my logic. I think this would be easier to maintain in the future and remove the risk of one minor mistake taking down dozens of incoming email addresses.
