Your Zap reaches the Google Sheets Lookup Spreadsheet Row action but stops with the error Required field "Lookup Value" (lookup_value) is missing. The spreadsheet is connected, the lookup column is selected and the previous steps appear to be working, yet Zapier cannot complete the search.
This usually happens because the field mapped into Lookup Value contains no data when the action runs. To fix it, inspect the failed run, check which field supplied the search value and correct the mapping or handle records where that value is genuinely missing.
Quick Fix: Check the Lookup Value First
Start by opening Zap History and selecting the failed run. Click the Google Sheets Lookup Spreadsheet Row action, then examine its Data In tab to see what information the action received.
Find the Lookup Value field. If it is empty or shows a missing value, open the preceding step and check its Data Out to see whether that step supplied the expected information.
If the preceding step contains the correct value but the Google Sheets action receives nothing, inspect the field mapping. If the value is already missing from the preceding step, investigate the source data instead.
For example, a Zap might search a customer spreadsheet using an email address. If the form submission contains an email but the lookup receives an empty field, Zapier may be referencing the wrong email property.
You do not need to reconnect Google Sheets or recreate the spreadsheet simply because this error appears. First determine where the required value disappeared.
Why the Lookup Value Is Missing
Zapier's Lookup Spreadsheet Row action searches a selected spreadsheet column for a particular value. Both the lookup column and the value being searched for must be configured correctly.
Suppose a Google Sheet contains customer records with columns for Customer Name, Email and Account Status. A Zap receives new form submissions and searches the Email column to determine whether the customer already exists.
The lookup works when an email address arrives. However, if one submission has no email address and that empty field is mapped into Lookup Value, the action can not perform the intended search.
Zapier documents this error for the Lookup Spreadsheet Row action and the Lookup Spreadsheet Rows action that outputs line items. The problem occurs when the required mapped search value is blank.
The important distinction is that the search has not simply failed to find a matching row. The action is missing the information needed to carry out the search.
Check Whether the Previous Step Actually Sent the Value
A field appearing in the Zap editor does not guarantee that it contains information in every live run. Some applications provide optional fields that are populated for certain records but absent from others.
In Zap History, open the failed run and select the step immediately before the Google Sheets lookup. Examine its Data Out and locate the field that should supply the search value.
If that field contains the expected information, compare it with the field selected in the Google Sheets action. Make sure both refer to the same source property.
If the previous step is also missing the value, trace the information further backward. For example, the original form submission might not contain an email address or an earlier action might not have returned the field you expected.
When diagnosing the problem, distinguish between these three situations.
| What you find | Likely explanation | What to do |
|---|---|---|
| Previous step has the value, but Lookup Value is empty | Incorrect or outdated mapping | Select the correct source field |
| Previous step is missing the value | Source record is incomplete | Correct the source data or handle missing inputs |
| The error started after fields were renamed or changed | Mapping may reference an old field | Refresh test data and remap the field |
This comparison helps identify the relevant failure point without changing unrelated settings.
Fix an Incorrect Lookup Value Mapping
Open the affected Zap in the editor and select its Google Sheets Lookup Spreadsheet Row action. In the Configure tab, verify that the correct Spreadsheet, Worksheet and Lookup Column are selected.
Next, examine Lookup Value. This field should contain the actual information you want Zapier to search for, either entered directly or mapped from an earlier step.
Remove an incorrect field mapping and select the appropriate field from the available data. For example, if the spreadsheet's Email column contains customer email addresses, the Lookup Value should receive the corresponding email from the source record.
Be careful when the preceding application offers multiple similarly named fields. Contact Email, Billing Email and Account Email may contain different information or have different requirements.
After selecting the correct source field, test the Google Sheets action with a record containing a valid lookup value. Inspect Data In again to confirm that the expected information is reaching the action.
If the correct value is present but the search cannot find a matching row, you are dealing with a different problem. That requires checking the spreadsheet data and search criteria rather than continuing to troubleshoot an empty field.
Why a Working Lookup Value Suddenly Becomes Blank
A previously successful Zap can develop this error when the structure of an earlier application's data changes. The Zap may still contain an existing field mapping but that field might no longer supply usable information.
For example, a contact form originally provides a field called Customer Email. Later, someone replaces that field with Email Address, leaving the Zap's existing mapping connected to outdated data.
Open the step supplying the information and load a fresh test record. Check which fields are currently available and whether their values match the information expected by the lookup.
Return to the Google Sheets action and replace any outdated mapping with the current field. Zapier may display a warning indicator when a mapped field no longer exists or contains no data.
Testing with a recent record is important because older sample data may not represent the current structure of the connected application.
If the mapping is correct but only some records fail, investigate whether the source field is optional. A field that exists in your test record may still be empty in legitimate live submissions.
Example: Blank Billing Email Causes Lookup Error
Consider a Zap that receives customer orders and searches a Google Sheet to find the corresponding customer account. The spreadsheet uses customer email addresses as unique identifiers.
The incoming order contains two different email fields: Customer Email and Billing Email. Customer Email is required but Billing Email is optional.
During setup, the Zap creator accidentally maps Billing Email into the Google Sheets Lookup Value field. The first few test orders contain both addresses, so the workflow appears to function normally.
Later, an order arrives without a billing email. The Google Sheets action receives an empty Lookup Value and stops.
The relevant data might look like this:
| Field | Incoming order | Lookup configuration |
|---|---|---|
| Customer Email | customer@example.com | Not selected |
| Billing Email | Empty | Selected as Lookup Value |
| Lookup Column | — |
In this example, the spreadsheet connection does not need to be repaired. The problem is that the lookup uses an optional field even though a more appropriate customer identifier is available.
The correction is to replace Billing Email with Customer Email in the Lookup Value mapping, provided that Customer Email is the identifier stored in the spreadsheet's Email column.
Test the revised configuration using an order without a billing email but with a valid customer email. The lookup should now receive the required search value.
This example illustrates why checking the actual input data is more reliable than repeatedly reconnecting Google Sheets or rerunning the same failed action.
Prevent Lookup Errors From Blank Inputs
Sometimes the mapping is correct and the blank input is expected. A customer may legitimately omit optional information or another application may create a record before all its details are available.
In that situation, choosing the same field again will not prevent future failures. The workflow needs an appropriate way to handle incomplete records.
Stop the Lookup When the Required Value Is Empty
If a valid email address or customer ID is essential to identify the correct spreadsheet record, prevent the lookup from running when that information is unavailable.
On an eligible Zapier paid plan, add a Filter by Zapier step immediately before the Google Sheets lookup. Select the same source field used for Lookup Value and configure the condition Exists.
When the field contains data, the filter allows the Zap to continue to the lookup. When the field is missing, the filter stops the workflow before the Google Sheets action runs.
For example, a workflow that searches customers by email should continue only when an email value exists. A submission without that information can stop safely rather than attempting an invalid search.
Test the filter with both populated and missing values. The first should pass through the filter, while the second should stop before the lookup.
Remember that the Exists condition checks whether a value is present. It does not independently prove that an email address is valid or that a matching record exists in Google Sheets.
Use a Fallback Only When Another Valid Search Value Exists
If the missing field has a legitimate replacement, Zapier's Formatter tool can provide a default value before the lookup runs.
On a supported paid plan, add a Formatter by Zapier action before Google Sheets. Select Text and choose the Default Value transform, then map the original field into its Input.
Configure an appropriate fallback value and test the Formatter action. Once its output contains the expected information, map that output into the Google Sheets Lookup Value field.
However, do not enter an arbitrary email address or customer ID merely to bypass the error. A placeholder could match the wrong record or produce misleading results in later automation steps.
A fallback makes sense when the replacement is a legitimate value that the workflow is designed to search for. If no valid identifier exists, stopping the lookup is generally safer.
Handle Incomplete Records Separately When Necessary
Some businesses need to retain incomplete submissions rather than stop processing them entirely. For example, a record without an email address might need to enter a manual review process.
On a plan supporting Paths by Zapier, you can create separate branches based on whether the required identifier exists. One branch performs the Google Sheets lookup, while another handles records that need additional information.
This arrangement keeps the lookup limited to records with valid search inputs while allowing incomplete records to follow an intentional process.
The important requirement is that the branch handling missing identifiers must not attempt the same search without supplying an appropriate value.
Why No-Match Settings Won’t Fix a Missing Lookup Value
The Google Sheets lookup action includes settings that control what happens when a search does not find a matching row. Depending on the selected action and configuration, you may also have an option to create a spreadsheet row when no match exists.
These settings address a different situation from a missing Lookup Value. They become relevant when Zapier has a search value but cannot find a corresponding spreadsheet record.
For example, a lookup might correctly receive customer@example.com while the spreadsheet contains no row with that email address. The action has usable input but the search does not produce the expected match.
By contrast, the missing Lookup Value error indicates that the required search input is absent. Changing the no-match behaviour does not correct the empty field that caused the failure.
Keep the distinction clear before enabling automatic row creation. A workflow that creates spreadsheet records should use reliable identifiers so that incomplete data does not produce duplicates or records associated with the wrong customer.
Test the Fix With Valid and Blank Inputs
After updating the field mapping or adding the necessary conditional handling, test the workflow against two different situations.
First, use a safe test record containing a valid identifier. Check that the earlier step supplies the value and that the Google Sheets action receives the same information in Lookup Value.
Confirm that the lookup returns the intended spreadsheet row when a matching record exists. If the action has subsequent steps, check that they receive the correct row information.
Next, test a record where the original problem occurred. If the source field was mapped incorrectly, verify that the corrected field now supplies the required information.
If missing values are legitimate and you added a filter, confirm that the incomplete record stops before reaching Google Sheets. If you configured a separate path, verify that it follows the intended branch.
If you added a fallback, check that the replacement value is appropriate and does not search for an unrelated record.
Be careful when testing actions connected to production spreadsheets. Zapier action tests can execute real operations, so use safe test records and review settings that may create or update rows.
A successful test with one complete record does not establish that the problem is fully resolved. The important result is that the workflow behaves correctly with both complete and incomplete data.
Final Check: Verify the Lookup Value
The missing Lookup Value error is resolved when the Google Sheets action receives an appropriate search value or the workflow deliberately prevents incomplete records from reaching that action.
If the error continues, return to Zap History and compare the failed action's Data In with the preceding step's Data Out. That comparison usually provides a better starting point than changing the spreadsheet or reconnecting the account.
For reliable operation, keep field mappings current, verify that required source information is consistently available and handle optional fields before the lookup attempts to use them.
The goal is not merely to eliminate an error message. It is to make sure each Google Sheets lookup searches for the correct record using information that actually exists when the Zap runs.
