Use Allowed values to restrict what a field can return to a predefined list of choices. This helps standardize outputs, reduce cleanup, and prevent unexpected values from slipping into your output. If the extracted value doesn’t match your allowed list, you stay in control of what happens next.
When This Is Useful
Allowed choices are especially helpful when you need consistent, predictable data for automations and reporting. Common scenarios include:
Standardizing variations: e.g., “Paid”, “paid”, “PAID”, which would ensure that only “Paid” is accepted
Controlling categories: map outputs into a fixed set like Pending / Approved / Rejected
Preventing typos or noisy OCR: stop near-matches from creating new “random” values in your CRM/spreadsheet
Keeping integrations clean: avoid broken Zap steps or mismatched conditions due to unexpected values
Improving analytics: ensure dashboards and filters don’t split into duplicates (“US”, “U.S.”, “United States”)
Routing workflows: trigger different automations only when the value is one of the approved options
How to Set Up
Enter the mailbox you're working on
Click on the Fields tab
Click on the Edit Field button if applying the restriction to an existing field, otherwise click + New Field at the bottom:
Click on the Restrict to a list of choices toggle to enable the Choice field, then enter your list of choices:
Click Update. You should now see an icon next to the field denoting it has a list of allowed outputs:
Frequently Asked Questions
How many choices can I have in a field?
There is currently no limit to the number of choices in a field, but we would recommend keeping this figure under a few dozen as it will extend the processing time with more choices.
Is the restriction exact match?
Yes, the list of choices is case sensitive.



