Trigger Fields (Custom)#

Sometimes, the data returned by a trigger is hard to use in a Zap because of how the keys are named. When a user goes to map fields in an action, the trigger data's keys are used to identify which field is which. If those keys are something unintelligible like UUIDs rather than human-readable data points like "name" or "email", the user may not be able to identify which fields to map in their action.

To remedy this, we have Custom Trigger Fields, an additional HTTP GET to a URL you provide in your trigger definition that tells us additional metadata about the data the trigger will return, such as human-readable labels to display when mapping fields. All you need to do to enable custom trigger fields is:

[
  {
    "type": "unicode", // unicode, int, or bool
    "key": "json_key", // the key in the trigger data
    "label": "Pretty Label", // the human-readable label to display
  },
  ...
]
↑ Was this documentation useful? Yes No
Get Help