With a lookup table, you can automatically match data from one app with the corresponding data needed by another app. This is useful if two apps treat the same object differently. Lookup tables can only be used in a Zap action, not in a trigger.
If your trigger app sends the customer's name but your action app needs a customer ID, you can create a lookup table to match the name to the correct ID, and use the result in an action step.
- Lookup Key: the data you want to search for within your lookup table.
- Lookup Table: this table consists of two columns. The left column is where the Zap will search for the value that appears in the Lookup Key. The right column is what the Zap will output if the lookup key matches the value.
- Fallback Value: if the lookup key does not match any values in the lookup table, you can use this field to return a backup value.
If the mapped field for the lookup key has no value, nothing will be sent by the lookup table. The fallback value is only used for existing values that do not match any table row.