Current limitation does not offer all custom fields, e.g. a number fields to be considered as an event trigger, when creating automations.
Automation example:
When “number field” is updated by agent, then send custom mail to requester.
Closed
Custom fields to be considered as an event in automation rules
Why are number fields excluded from automation triggers when they can be just as important as status or text fields? Wouldn’t allowing triggers for all custom fields make automations more flexible and reduce manual work for agents? Has anyone found a reliable workaround for this limitation?
Join the Community
Already have an account? Login
Welcome back to Freshworks Community
No account yet? Create an account
Social Login
Login for Freshworks Employees Login with LinkedInor sign up below
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.