Trouble mapping custom product page links into automated Gmail shipping updates

Hi ​@forclaz00,

I've run into this before, and I'd still recommend sticking with the Lookup Table. The Gmail error usually means the product name isn't matching exactly, it might be extra spaces or capitalization.

I'd avoid switching to Python unless you really need to. A Lookup Table is much easier to maintain since adding or updating products is just a table edit instead of requiring someone to modify the Zap and republish it. I'd also consider matching on a product ID or SKU instead of the product name if possible.

Hope this helps!

Hi ​@forclaz00 

For us to have more info, post screenshots showing how your Zap steps are outlined and configured in the CONFIGURE tab while in EDIT mode with the field mappings visible.

Hi ​@forclaz00 

First things first – let's check if the product name coming from your trigger actually matches what's in your Lookup Table.

The Lookup Table in Zapier is case-sensitive, so even a small difference like "Forclaz Jackets" vs "forclaz jackets" will cause it to fail and return nothing (which is why you're getting that empty field error in Gmail).

Here's what I'd suggest:

1. Check the match first – Compare the exact product name from your trigger with what you have in the Lookup Table. Look for:

   • Capitalization differences

   • Extra spaces (leading or trailing)

   • Any special characters

2. If they don't match, use Formatter by Zapier to standardize the data:

   • Add a Formatter step with "Text" action

   • Set Transform to "Lowercase" – this makes everything consistent

   • Add another Formatter step with "Trim Whitespace" – this removes any sneaky spaces

3. Update your Lookup Table to use the lowercase version of product names as keys

One more thing: Could you share screenshots of your Zap setup (especially the Lookup Table configuration and the data coming from your trigger)? That would help me see exactly where the mismatch is happening and give you more specific guidance.

Hope this helps! Let me know what you find. 

One thing worth adding to the case and whitespace advice above: a Lookup Table returns an empty value on a miss rather than throwing an error, so the Zap keeps running and only falls over later at Gmail. That is why this looks like a Gmail problem when the real failure happened a step earlier.