Create lookup tables in Zaps

Available on plans:

Free

Pro

Team

Enterprise

 

With a lookup table, you can automatically match data from one app with the corresponding data needed by another app. You can then use the value returned by the lookup table to set a custom value for dropdown menu fields

Example

If your trigger app sends the customer's email 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.

 

This article explains how to create a lookup table using either Zapier Tables or a Formatter step. Each app offers different features, so you can select what works best for your use case:

Use Zapier Tables if:

  • You need to match the same value to multiple pieces of data, for different apps.
  • You want to share access with teammates to maintain the lookup table.

Use Formatter if:

  • The data you want to check comes as line items. Formatter can repeat the process for each line item in your data.
  • You want to set a backup value in case the data received is not available in the lookup table.
Formatter Zapier Tables

Use a Formatter lookup table step

1. Add a Formatter step

In the Zap editor:

  • In the Zap outline, click the Action step or the plus sign + to add a new action. A dialog box will open.
  • In the search box, search for and select Formatter. The right sidebar will open to the Setup tab.
  • Click the Action event dropdown menu and select Utilities.
  • Click Continue.

2. Set up your transform

  • Click the Transform dropdown menu and select Lookup Table.
  • In the Lookup Key field, select a field from the trigger or a previous action step. The Zap will use this value to search the lookup table for the correct row.
  • In the Lookup Table fields:
    • Key: In the left column, enter the text for each key. This should match the data the Zap could receive from the trigger. This column is case-sensitive. 
    • Value: Enter the corresponding value for each key in this column. This is what the Zap will pass on to other steps, if it finds a matching key.
    • Click + Add value set to create more key and value pairs.
  • (optional) In the Fallback Value field, enter a value to be used if there is no matching key.
Example

If your sales team inputs the customer name in a spreadsheet, but you need the customer ID to find them in your CRM app, you can add the customer's name to the Key column (for example, "Jane Doe"), and the corresponding ID to the Value column (for example, "12345"). You can then add a line for each customer so that the Zap can pass the correct value to other steps.

3. Test your step

  • Click Test step. If the transformation is successful, the step will return the value associated with the key, or the fallback value (if you set one).
Note

If the field you use as the lookup key is blank at the time the Zap runs, the lookup table will not return any matches. In that case, the Zap run will send no value, as the fallback value is only used when there are existing values but no matches.

Once you’ve set your lookup table step, you can add other actions to use the result in your Zap.

Was this article helpful?
4 out of 14 found this helpful