Add Mapping field format (ability to map values detected in email to values desired in payload)
Example:
* A key-value pair extracted from an email says "Yes, I'd like to receive all regular updates" (and this is one of 4-5 string constants, not a free-form field)
* We want to receive the canonical value "all-updates"
Desired functionality: let us create a mapping table from the 4-5 string constants to our canonical values. This particular limited form of the feature doesn't require any AI parsing of the sentence.
Comments: 3
Oldest
•
Newest
•
Most likes
•
Fewest likes
-
15 Jan
Sylvestre Dupont Admin PinnedHighlighted comment
You can now constrain a field to a predefined list of allowed values by setting the field format to "Text (single line)" and enabling "Restrict to a list of choices".
We'll leave this feature request open until we offer a way map values to those choices like in the original description. -
09 May, '25
Tom NgoI should have said this in the body of my suggestion and wish I could edit that:
This is one of the two key reasons we are unable to adopt Parseur. The team member who reported this said it's the "nail in the coffin" for our product choice. (We really like what we see, other than those two key reasons we are unable to adopt.) -
12 May, '25
Sylvestre Dupont AdminHi Tom,
Thanks for the feedback! I hear the need to add a new format, perhaps named "Choice", that lets you enter key-value mappings. We'll consider adding this feature in the future.
In the meantime, here are three workarounds:
- If using the AI engine, use instructions to ask the AI to do the mapping
- If using Post Processing, implement the key-value business logic there (requires a Pro or above plan)
- If none of the above solutions are an option, do the key/value mapping down the line of the processing workflow, either on Zapier, Make, Power Automate or on your side of the webhook.