Trigger w/ requester email address conditionAnswered
How can I configure a trigger with a condition that looks specifically at the email address of the requester?
The "Requester" condition, which requires you to select from a list of extant users, is insufficient; I want to include emails that don't exist yet as ZD users. I also have a pretty long list to add; would really be great to add them in bulk, rather than one-by-one in separate conditions.
This "Email" field looked promising, but doesn't seem to work:
Related: is there a way to specify a given email address or phone number as a recipient for an SMS or email alert, as an "action" on a given trigger? Limiting those fields to named users, without the ability to specify the phone number or email address that's actually targeted, is really cumbersome and hard to troubleshoot. At the very least, the email address/phone number associated with that user should be exposed in the UI while you're creating the trigger. Exposing the name only seems kind of absurd to me.
Have a look at targets for email notifications to specified individuals.
Triggers and automations are only able to access individual agents, individual groups, or variables such as requestor, assignee.
Depending on what you are trying to achieve, you can create organisations based on domains, and then this can be used in triggers and automations.
As Andrew mentioned, rather than specifying a long list of individual users in a trigger, why not all all those users to an Organization, and then just use the Organization as your trigger criteria? You could also use User Tags, or create a custom User Field to hold that information as well, some thing to denote the users are in a particular category that this trigger will use as a criteria. About organizations and groups
And fwiw, you can import users in bulk (and specify an Organization, tags or custom fields values when you do that): Bulk importing users
Thanks for your response. User Tags should work!
Using Organizations won't work for two reasons:
1. In our environment, Organizations are used to refer to something specific, which I can't interfere with for a one-off trigger configuration like this one, and
2. More specifically, a trigger with an Organization criterion will only fire if the first Organization for that user matches. I could create an organization for this purpose and ensure that it is the first organization for each of the users I'm hoping to match, but would break other triggers we have configured on the environment-specific organizations mentioned above in the process.
The tags solution is ok though. Thanks again!
Glad I could help, Charlie!
Post is closed for comments.